Error Expanding tables in Linked Server to Pervasive

Pleeeease help? I get an error when expanding the Tables object under linked servers in Enterprise Manager on a MSSQL2000 server.

I have a standard install of the Pervasive.SQL V8 data engine and DemoData db on my local PC. The SQL Server is also on my local PC.

I manage to create the Linked Server using the MSSQL Enterprise Manager. I used the following configuration:

Provider Name: Pervasive.SQL V8 OLE DB Provider
Product Name: Pervasive.SQL V8
Data source: DemoData
Provider string: <blank>
Location: workstation03
Catalog: <blank>

However when I try to expand the tables object under Linked Servers in the Enterprise manager I get the following error.

Error 7311: Could not obtain the schema rowset for the OLE DB provider 'UNKNOWN'. The provider supports the interface, but retuns a failure code when it is used. OLE DB error trace [OLE/DB Provider 'UNKNOWN' IDBSchemaRowset::GetRowset returned 0x80040155 ].

How would I fix this?

Thank you.moving to microsoft sql server forumsql

Error executing sp_change_users_login

Hello -
Hello, i'm trying to run
Exec sp_change_Users_login 'report'
From a few databases on my servers. When I try to execute,=20
i'm receiving the following error message:
=AB Server: Msg 15289, Level 16, State 1, Procedure=20
sp_change_users_login, Line 27
Terminating this procedure. Cannot have an open=20
transaction when this is
run.=BB
Here's the code i'm trying to execute:
=AB=20
if exists (select * from dbo.sysobjects where id =3D=20
object_id(N'[dbo].[OutputOrphanUsers]') and OBJECTPROPERTY
(id, N'IsUserTable') =3D 1)
drop table [dbo].[OutputOrphanUsers]
go
create table OutputOrphanUsers=20
(uname varchar(30),
usid varbinary(85))
go
insert OutputOrphanUsers EXEC=20
sp_change_users_login 'Report'=BB
I hope that you can help me, i cant found any workarround=20
to this situation.
Best regerdsI'm not sure there is a workaround... I tried hiding the query in openrowset
and that didn't work either... ie
insert OutputOrphanUsers select a.* FROM
OPENROWSET('SQLOLEDB','servername';'logi
n';'password',
'exec sp_change_users_login report') AS a
Actually what you could do is get the source... in master sp_helptest
sp_change_users_login and change the code that requires no transaction (but
only if the parameter is report. Then re-add it as a different name. The
common naming convention would be sp__change_users_login (2 underscores
after sp).
That will work.
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:153ed01c4157e$e99d76d0$a101280a@.phx
.gbl...
Hello -
Hello, i'm trying to run
Exec sp_change_Users_login 'report'
From a few databases on my servers. When I try to execute,
i'm receiving the following error message:
Server: Msg 15289, Level 16, State 1, Procedure
sp_change_users_login, Line 27
Terminating this procedure. Cannot have an open
transaction when this is
run.
Here's the code i'm trying to execute:
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[OutputOrphanUsers]') and OBJECTPROPERTY
(id, N'IsUserTable') = 1)
drop table [dbo].[OutputOrphanUsers]
go
create table OutputOrphanUsers
(uname varchar(30),
usid varbinary(85))
go
insert OutputOrphanUsers EXEC
sp_change_users_login 'Report'
I hope that you can help me, i cant found any workarround
to this situation.
Best regerds

Error executing Backup

Hello,
I've configure "HP Omniback" to perform backups on=20
databases servers under the account "omni_acc", when i=20
configured this account i assign this account the "System=20
Administrators" Server Role because i can=B4t did backups if=20
the account wasn=B4t assign to this role.
Now i want to give to the omni_acc account other=20
previleges since we have the "db_backupoperator" database=20
role but... i cant do the backups if the user is only=20
assign to this role. Can anybody explain to me this=20
situation?
Is not supposed that a user assign to=20
the "db_backupoperator" database role perform backups and=20
restores to databases?
How can i give permissions to a user to make backups and=20
restores of databases?
Best regards
For RESTORE you cannot use db_backup operator if the database doesn't exist, as ... the database doesn't
exist! In this case, dbcreator server role should do.
Your problem is very likely that HP wrote their software so it requires this permissions. The place to start
is the documentation for the software. If there is no, ask the vendor of the software (HP).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message news:1919d01c44c8f$47eb8c30$a501280a@.phx.gbl...
Hello,
I've configure "HP Omniback" to perform backups on
databases servers under the account "omni_acc", when i
configured this account i assign this account the "System
Administrators" Server Role because i cant did backups if
the account wasnt assign to this role.
Now i want to give to the omni_acc account other
previleges since we have the "db_backupoperator" database
role but... i cant do the backups if the user is only
assign to this role. Can anybody explain to me this
situation?
Is not supposed that a user assign to
the "db_backupoperator" database role perform backups and
restores to databases?
How can i give permissions to a user to make backups and
restores of databases?
Best regards

Error executing Backup

Hello,
I've configure "HP Omniback" to perform backups on=20
databases servers under the account "omni_acc", when i=20
configured this account i assign this account the "System=20
Administrators" Server Role because i can=B4t did backups if=20
the account wasn=B4t assign to this role.
Now i want to give to the omni_acc account other=20
previleges since we have the "db_backupoperator" database=20
role but... i cant do the backups if the user is only=20
assign to this role. Can anybody explain to me this=20
situation?
Is not supposed that a user assign to=20
the "db_backupoperator" database role perform backups and=20
restores to databases?
How can i give permissions to a user to make backups and=20
restores of databases?
Best regardsFor RESTORE you cannot use db_backup operator if the database doesn't exist,
as ... the database doesn't
exist! In this case, dbcreator server role should do.
Your problem is very likely that HP wrote their software so it requires this
permissions. The place to start
is the documentation for the software. If there is no, ask the vendor of the
software (HP).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message news:1919d01c
44c8f$47eb8c30$a501280a@.phx.gbl...
Hello,
I've configure "HP Omniback" to perform backups on
databases servers under the account "omni_acc", when i
configured this account i assign this account the "System
Administrators" Server Role because i cant did backups if
the account wasnt assign to this role.
Now i want to give to the omni_acc account other
previleges since we have the "db_backupoperator" database
role but... i cant do the backups if the user is only
assign to this role. Can anybody explain to me this
situation?
Is not supposed that a user assign to
the "db_backupoperator" database role perform backups and
restores to databases?
How can i give permissions to a user to make backups and
restores of databases?
Best regards

Error executing Backup

Hello,
I've configure "HP Omniback" to perform backups on databases servers under the account "omni_acc", when i configured this account i assign this account the "System Administrators" Server Role because i can=B4t did backups if the account wasn=B4t assign to this role.
Now i want to give to the omni_acc account other previleges since we have the "db_backupoperator" database role but... i cant do the backups if the user is only assign to this role. Can anybody explain to me this situation?
Is not supposed that a user assign to the "db_backupoperator" database role perform backups and restores to databases?
How can i give permissions to a user to make backups and restores of databases?
Best regardsFor RESTORE you cannot use db_backup operator if the database doesn't exist, as ... the database doesn't
exist! In this case, dbcreator server role should do.
Your problem is very likely that HP wrote their software so it requires this permissions. The place to start
is the documentation for the software. If there is no, ask the vendor of the software (HP).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message news:1919d01c44c8f$47eb8c30$a501280a@.phx.gbl...
Hello,
I've configure "HP Omniback" to perform backups on
databases servers under the account "omni_acc", when i
configured this account i assign this account the "System
Administrators" Server Role because i can´t did backups if
the account wasn´t assign to this role.
Now i want to give to the omni_acc account other
previleges since we have the "db_backupoperator" database
role but... i cant do the backups if the user is only
assign to this role. Can anybody explain to me this
situation?
Is not supposed that a user assign to
the "db_backupoperator" database role perform backups and
restores to databases?
How can i give permissions to a user to make backups and
restores of databases?
Best regards

Error during Full-text population

I'm using Full-text in various databases on my servers (SQL2005 on W2K3). On a few databases the Full-text population ends with the error:

'Error '0x80030050' occurred during full-text index population for table or indexed view '[database].[dbo].[table]' (table or indexed view ID '1714105147', database ID '9'), full-text key value 0x00015EE1. Failed to index the row.'

The next log-line lets me know the name of the dll that caused the problem:

The component 'offfilt.dll' reported error while indexing. Component path 'C:\WINDOWS\system32\offfilt.dll'.

There's one solution I read about, but that one is not the case here. That sollution states that this problem occurs when de datatype is not the same as the filetype (e.g. datatype is pdf, documenttype is doc).

What can be the problem here?

Thanks.

I'm getting the same error in a multitude of environments (XP Pro (development/test environment), Windows Server 2003). SQL Server 2005 SP1 has been applied. Also getting on XP Pro system with SP2 applied. However, the OFFFILT.DLL appears to be part of the OS and not SQL Server. The version on my XP Pro is 2003.5.28.0 and is dated 2004-08-04.

I think the problem is with Word (.doc) files as I don't appear to have any problems indexing PowerPoint (.ppt) files.

|||

It sounds like the Microsoft Office Indexing filter DLL is choking on an unrecognised file format. Might you have some very old Word documents in the table, or conversely if there are new Word 2007 documents in there might these be too new?

|||In my case (not the original poster) the files that it is choking on are valid Microsoft Word documents. The documents can be opened in Office 2003. We are avoiding Office 2007 for now. Not every document has a problem. So it is something (style, font, property, ?) in the document that is tripping it up.|||

Ok, it took some time, but here it is:

I had some word-documents with embedded object that were unkown to Word. So I deleted them from the documents. All messages with the error in the original post are gone now. There is however a 'known bug' in Full Text Catalogue (I got the information from Microsoft) which will be patched in SP3. If the Full Text Index is being used very frequent (I'm not sure if that is 500 times a second or 5000000 times...) it gets corrupted.

A few tips here:

Make sure the dll's concerning FTC are in place. You can use this query to see which dll's FTE is using:

select * from sys.fulltext_document_types

Make sure there are no unkown objects in your documents. The error produced, if so, contains a HEX-number which represents the id-column value of the table. You can transform it to a more usable number with this query:

select * from [table] where [id-column] in (cast([HEX-number] as int))

If all this is ok, it's getting more likely that you have the 'known-bug' issue at hand.

Error during Full-text population

I'm using Full-text in various databases on my servers (SQL2005 on W2K3). On a few databases the Full-text population ends with the error:

'Error '0x80030050' occurred during full-text index population for table or indexed view '[database].[dbo].[table]' (table or indexed view ID '1714105147', database ID '9'), full-text key value 0x00015EE1. Failed to index the row.'

The next log-line lets me know the name of the dll that caused the problem:

The component 'offfilt.dll' reported error while indexing. Component path 'C:\WINDOWS\system32\offfilt.dll'.

There's one solution I read about, but that one is not the case here. That sollution states that this problem occurs when de datatype is not the same as the filetype (e.g. datatype is pdf, documenttype is doc).

What can be the problem here?

Thanks.

I'm getting the same error in a multitude of environments (XP Pro (development/test environment), Windows Server 2003). SQL Server 2005 SP1 has been applied. Also getting on XP Pro system with SP2 applied. However, the OFFFILT.DLL appears to be part of the OS and not SQL Server. The version on my XP Pro is 2003.5.28.0 and is dated 2004-08-04.

I think the problem is with Word (.doc) files as I don't appear to have any problems indexing PowerPoint (.ppt) files.

|||

It sounds like the Microsoft Office Indexing filter DLL is choking on an unrecognised file format. Might you have some very old Word documents in the table, or conversely if there are new Word 2007 documents in there might these be too new?

|||In my case (not the original poster) the files that it is choking on are valid Microsoft Word documents. The documents can be opened in Office 2003. We are avoiding Office 2007 for now. Not every document has a problem. So it is something (style, font, property, ?) in the document that is tripping it up.|||

Ok, it took some time, but here it is:

I had some word-documents with embedded object that were unkown to Word. So I deleted them from the documents. All messages with the error in the original post are gone now. There is however a 'known bug' in Full Text Catalogue (I got the information from Microsoft) which will be patched in SP3. If the Full Text Index is being used very frequent (I'm not sure if that is 500 times a second or 5000000 times...) it gets corrupted.

A few tips here:

Make sure the dll's concerning FTC are in place. You can use this query to see which dll's FTE is using:

select * from sys.fulltext_document_types

Make sure there are no unkown objects in your documents. The error produced, if so, contains a HEX-number which represents the id-column value of the table. You can transform it to a more usable number with this query:

select * from [table] where [id-column] in (cast([HEX-number] as int))

If all this is ok, it's getting more likely that you have the 'known-bug' issue at hand.

Error during Full-text population

I'm using Full-text in various databases on my servers (SQL2005 on W2K3). On a few databases the Full-text population ends with the error:

'Error '0x80030050' occurred during full-text index population for table or indexed view '[database].[dbo].[table]' (table or indexed view ID '1714105147', database ID '9'), full-text key value 0x00015EE1. Failed to index the row.'

The next log-line lets me know the name of the dll that caused the problem:

The component 'offfilt.dll' reported error while indexing. Component path 'C:\WINDOWS\system32\offfilt.dll'.

There's one solution I read about, but that one is not the case here. That sollution states that this problem occurs when de datatype is not the same as the filetype (e.g. datatype is pdf, documenttype is doc).

What can be the problem here?

Thanks.

I'm getting the same error in a multitude of environments (XP Pro (development/test environment), Windows Server 2003). SQL Server 2005 SP1 has been applied. Also getting on XP Pro system with SP2 applied. However, the OFFFILT.DLL appears to be part of the OS and not SQL Server. The version on my XP Pro is 2003.5.28.0 and is dated 2004-08-04.

I think the problem is with Word (.doc) files as I don't appear to have any problems indexing PowerPoint (.ppt) files.

|||

It sounds like the Microsoft Office Indexing filter DLL is choking on an unrecognised file format. Might you have some very old Word documents in the table, or conversely if there are new Word 2007 documents in there might these be too new?

|||In my case (not the original poster) the files that it is choking on are valid Microsoft Word documents. The documents can be opened in Office 2003. We are avoiding Office 2007 for now. Not every document has a problem. So it is something (style, font, property, ?) in the document that is tripping it up.|||

Ok, it took some time, but here it is:

I had some word-documents with embedded object that were unkown to Word. So I deleted them from the documents. All messages with the error in the original post are gone now. There is however a 'known bug' in Full Text Catalogue (I got the information from Microsoft) which will be patched in SP3. If the Full Text Index is being used very frequent (I'm not sure if that is 500 times a second or 5000000 times...) it gets corrupted.

A few tips here:

Make sure the dll's concerning FTC are in place. You can use this query to see which dll's FTE is using:

select * from sys.fulltext_document_types

Make sure there are no unkown objects in your documents. The error produced, if so, contains a HEX-number which represents the id-column value of the table. You can transform it to a more usable number with this query:

select * from [table] where [id-column] in (cast([HEX-number] as int))

If all this is ok, it's getting more likely that you have the 'known-bug' issue at hand.

Error converting data type varchar to numeric.

Server: Msg 8114, Level 16, State 5
Error converting data type varchar to numeric.

Hello...
I new in MS SQL.
Given: 2 servers, same SQL statements, same input, same tables, same data types, same triggers.
Problem: One server works fine while the other returns the error above.

I have no idea of the problem why the other is working.IN addition to that, they also have the same MS SQL version.|||Perhaps you could post the relevant code, as well as the table structure? It would be quite impossible to help without these two crucial pieces of information.

Error connecting to the server

I am having a problem adding a new server or going into my previously registered servers.

I was using Sql express and now using the full version of SQL 2005.

When I try to coonect to a server, In the server type I choose Database Engine
Server name I typed in LOCALHOST\SQLEXPRESS, no names show in the
dropdown for server, leave use windows authentication selected. then hit the
advanced button and change the network library to shared memory, hit test
button and get this error:

"An error has occurred while establishing a connection to the server. when
connecting to sql server 2005, this failure may be caused by the fact that
under the default settings sql server does not allow remote connections.
(provider: shared memory provider, error: 36 - the shared memory dll used to
to connect to 2000 was not found)"

any input would be appreciated. thanks.

Are you connecting to the Remote server or a Local server?|||local server|||

<connectionStrings><add name="ConnectionString" connectionString="Data Source=.\SQLSERVER;AttachDbFilename=|DataDirectory|\Database.mdf;Integrated Security=True;User Instance=True"providerName="System.Data.SqlClient" /></connectionStrings>

SQLSERVER is the server Name of your SQL SERVER. Check the name of the server (by default its SQLSERVER)

OR (create a new connection string)

Create a new Page > Put a GridView on it > Click the right Top corner and select the "New data source" > Click "Database" in the step "Choose a Data Type > Click OK > Now when you click the Drop down, probably you will see your Data base name in it.

(you will see the database name with your connection strings when the connection strings in web.config are not valid)

1. If you see the Database name:

Click Next and select any Table from your Database> Click Next again Ok > Click Finish. Now when you open your Configuration File (i.e web.config) you will see a new Connection string with the server Name.

2. If you dont see the Database Name:

Click "New Connection" in the step "Choose your data Connection" > Choose "Microsoft SQL Server" type and click Continue > choose your SQL SERVER Name from the Drop down next to REFRESH button> Attach the DataBase to the server > Now you can create a Connection string to the server.

Happy coding!

|||

I cannot register a server in sql server Management Studio

and this is the error i get

New Server Registration

Testing the registered server failed. Verify the server name, login credentials, and database, and then click test again.

Additional Information

=>An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)(Microsoft Sql Server)

|||

Hi,

Please check if you have the correct Servername and Instance name of that specific server.

I suggest you create a .UDL file to test the connection with the following steps:

1. Create a normal Text file.
2. Rename it to .udl extension.
3. Double click on that file and a Data Link Properties dialog box will be show.
4. Select the provider and data source, specify username and password, and click the Test Connection button for test.

|||

When I Have Microsoft OLE DB Provider for OLAP Drivers, it returns these options in the data source name

dBASE Files|||

Hi,

Are you connecting to a OLAP service(like SQL Server analysis service)? If not, I would suggest you use OLE DB Provider for SQL Server or SQL Native Client instead.

You can choose them from the Provider tab in Data Link Properties dialog box.

Error Connecting to SQL 2000 from 2005 SSMS

I can connect to all but one of my SQL 2000 SP 4 servers with SQL 2005 SP2 SSMS on my workstation. I get the following error for the one:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

I can connect to this server with the SQL 2000 Enterprise Manager from the same workstation I'm running SQL 2005 SSMS. I've also verified that tcp and named pipes are set up on the 2000 server. Can also telnet to the box with the default port #.

I'd appreciate any help you could give..

Thanks,

Dan

check the sql server 2005 is enabled for remote connection. check for firewall

http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx

Madhu

Error connecting to remote connections...

That's what appears at my client site. I have virtually the exact same
configuration on a handful of servers using the SQL Reporting Services and
the RDLC which is working great. Except this one server has:
"An error has occurred when establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by teh fact that
under the default settings SQL Server does not allow remote connections.
Named Pipes provider, error: 40 - Could not open a connection to the SQL
Server).
I think the IT admin used SQL permissions when he installed. Could that be
the problem?
Thanks in Advance.
ChrisThis link might help,
http://vadivel.blogspot.com/2007/01/error-has-occurred-while-establishing.html.
daw
"Chris Marsh" wrote:
> That's what appears at my client site. I have virtually the exact same
> configuration on a handful of servers using the SQL Reporting Services and
> the RDLC which is working great. Except this one server has:
> "An error has occurred when establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by teh fact that
> under the default settings SQL Server does not allow remote connections.
> Named Pipes provider, error: 40 - Could not open a connection to the SQL
> Server).
> I think the IT admin used SQL permissions when he installed. Could that be
> the problem?
> Thanks in Advance.
> Chris
>
>|||Sorry, I should have specified this earlier but the SQL DB is SQL 2000 not
2005 which is what is strange. Again, works on multiple other configurations
but not this one.
"daw" <daw@.discussions.microsoft.com> wrote in message
news:D05FF90C-2A0D-43B9-83B4-D348859995E9@.microsoft.com...
> This link might help,
> http://vadivel.blogspot.com/2007/01/error-has-occurred-while-establishing.html.
> daw
> "Chris Marsh" wrote:
>> That's what appears at my client site. I have virtually the exact same
>> configuration on a handful of servers using the SQL Reporting Services
>> and
>> the RDLC which is working great. Except this one server has:
>> "An error has occurred when establishing a connection to the server. When
>> connecting to SQL Server 2005, this failure may be caused by teh fact
>> that
>> under the default settings SQL Server does not allow remote connections.
>> Named Pipes provider, error: 40 - Could not open a connection to the SQL
>> Server).
>> I think the IT admin used SQL permissions when he installed. Could that
>> be
>> the problem?
>> Thanks in Advance.
>> Chris
>>