Hi,
From my research, it appears that it is not possible to have a linked server
created in SQL Server 2005 x64 use a 32-bit DSN (i.e. created with a 32 bit
driver). The answer is that I need to create a 64-bit DSN in order to
create a linked server in SQL Server 2005 x64. The problem is that many
vendors (i.e. Sybase) do not have a 64-bit driver.
Looks like our migration is SQL Server 2005 x64 will have to wait unless we
can get this to work with perhaps a third party vendore such as Data Direct.
Any one using Data Direct to connect to Sybase from SQL Server 2005 x64?
Thanks,
Rocco M.
(posted in microsoft.public.sqlserver.odbc,
microsoft.public.sqlserver.clients and microsoft.public.sqlserver.connect)Hi,
I've just ran into the same problem linking to Oracle 8i.
MSDAORA, OraOLEDB.Oracle and ODBC drivers do not work.
64 bit drivers have not been released yet... Any workaround except returning
to sqlserver 32bit?
Davide
"Rocco M" <rocco.mastrangelo@.hp.com> ha scritto nel messaggio
news:AHYeg.1209$cY3.584@.news.cpqcorp.net...
> Hi,
> From my research, it appears that it is not possible to have a linked
> server created in SQL Server 2005 x64 use a 32-bit DSN (i.e. created with
> a 32 bit driver). The answer is that I need to create a 64-bit DSN in
> order to create a linked server in SQL Server 2005 x64. The problem is
> that many vendors (i.e. Sybase) do not have a 64-bit driver.
> Looks like our migration is SQL Server 2005 x64 will have to wait unless
> we can get this to work with perhaps a third party vendore such as Data
> Direct. Any one using Data Direct to connect to Sybase from SQL Server
> 2005 x64?
> Thanks,
> Rocco M.
> (posted in microsoft.public.sqlserver.odbc,
> microsoft.public.sqlserver.clients and microsoft.public.sqlserver.connect)
>
Showing posts with label linked. Show all posts
Showing posts with label linked. Show all posts
Saturday, February 25, 2012
64 bit windows 2003 sp2 SQL SERVER 2005 Linked server
The server is IBM XS 466.
The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
(64bit),I want to create a linked server for Oracle,I have installed ORACLE
Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
2005,i can't find 'MSDAORA',it caust i can't create linked server for
oracle.msbut I can find some drivers about oracle in ODBC,but must run
'c:\windows\system32\odbcad32.exe'
This proble puzzle me for some days
Standing on Shoulders of Giants
* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
My first guess is that the 64 version of SQL Server can only load 64-bit
drivers. This means the old OleDb driver and ODBC driver are not
compatible.
Either reinstall SQL server as 32-bit binaries or find a 64-bit
compatible driver for Oracle.
Jesse
|||* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
You can find the 64-bit OleDB Driver here:
http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
That should get things in working order.
Jesse
|||I haved installed 64bit Driver for Oracle,but the proble is the same,it has
other approach?
Standing on Shoulders of Giants
"Jesse Houwing" wrote:
> * fds2003 wrote, On 4-7-2007 12:32:
> You can find the 64-bit OleDB Driver here:
> http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
> That should get things in working order.
> Jesse
>
The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
(64bit),I want to create a linked server for Oracle,I have installed ORACLE
Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
2005,i can't find 'MSDAORA',it caust i can't create linked server for
oracle.msbut I can find some drivers about oracle in ODBC,but must run
'c:\windows\system32\odbcad32.exe'
This proble puzzle me for some days
Standing on Shoulders of Giants
* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
My first guess is that the 64 version of SQL Server can only load 64-bit
drivers. This means the old OleDb driver and ODBC driver are not
compatible.
Either reinstall SQL server as 32-bit binaries or find a 64-bit
compatible driver for Oracle.
Jesse
|||* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
You can find the 64-bit OleDB Driver here:
http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
That should get things in working order.
Jesse
|||I haved installed 64bit Driver for Oracle,but the proble is the same,it has
other approach?
Standing on Shoulders of Giants
"Jesse Houwing" wrote:
> * fds2003 wrote, On 4-7-2007 12:32:
> You can find the 64-bit OleDB Driver here:
> http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
> That should get things in working order.
> Jesse
>
64 bit windows 2003 sp2 SQL SERVER 2005 Linked server
The server is IBM XS 466.
The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
(64bit),I want to create a linked server for Oracle,I have installed ORACLE
Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
2005,i can't find 'MSDAORA',it caust i can't create linked server for
oracle.msbut I can find some drivers about oracle in ODBC,but must run
'c:\windows\system32\odbcad32.exe'
This proble puzzle me for some days
--
Standing on Shoulders of Giants* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACL
E
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
My first guess is that the 64 version of SQL Server can only load 64-bit
drivers. This means the old OleDb driver and ODBC driver are not
compatible.
Either reinstall SQL server as 32-bit binaries or find a 64-bit
compatible driver for Oracle.
Jesse|||* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACL
E
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
You can find the 64-bit OleDB Driver here:
[url]http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html[/u
rl]
That should get things in working order.
Jesse|||I haved installed 64bit Driver for Oracle,but the proble is the same,it has
other approach?
--
Standing on Shoulders of Giants
"Jesse Houwing" wrote:
> * fds2003 wrote, On 4-7-2007 12:32:
> You can find the 64-bit OleDB Driver here:
> [url]http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html[
/url]
> That should get things in working order.
> Jesse
>
The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
(64bit),I want to create a linked server for Oracle,I have installed ORACLE
Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
2005,i can't find 'MSDAORA',it caust i can't create linked server for
oracle.msbut I can find some drivers about oracle in ODBC,but must run
'c:\windows\system32\odbcad32.exe'
This proble puzzle me for some days
--
Standing on Shoulders of Giants* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACL
E
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
My first guess is that the 64 version of SQL Server can only load 64-bit
drivers. This means the old OleDb driver and ODBC driver are not
compatible.
Either reinstall SQL server as 32-bit binaries or find a 64-bit
compatible driver for Oracle.
Jesse|||* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACL
E
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
You can find the 64-bit OleDB Driver here:
[url]http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html[/u
rl]
That should get things in working order.
Jesse|||I haved installed 64bit Driver for Oracle,but the proble is the same,it has
other approach?
--
Standing on Shoulders of Giants
"Jesse Houwing" wrote:
> * fds2003 wrote, On 4-7-2007 12:32:
> You can find the 64-bit OleDB Driver here:
> [url]http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html[
/url]
> That should get things in working order.
> Jesse
>
64 bit windows 2003 sp2 SQL SERVER 2005 Linked server
The server is IBM XS 466.
The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
(64bit),I want to create a linked server for Oracle,I have installed ORACLE
Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
2005,i can't find 'MSDAORA',it caust i can't create linked server for
oracle.msbut I can find some drivers about oracle in ODBC,but must run
'c:\windows\system32\odbcad32.exe'
This proble puzzle me for some days
--
Standing on Shoulders of Giants* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
My first guess is that the 64 version of SQL Server can only load 64-bit
drivers. This means the old OleDb driver and ODBC driver are not
compatible.
Either reinstall SQL server as 32-bit binaries or find a 64-bit
compatible driver for Oracle.
Jesse|||* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
You can find the 64-bit OleDB Driver here:
http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
That should get things in working order.
Jesse|||I haved installed 64bit Driver for Oracle,but the proble is the same,it has
other approach?
--
Standing on Shoulders of Giants
"Jesse Houwing" wrote:
> * fds2003 wrote, On 4-7-2007 12:32:
> > The server is IBM XS 466.
> > The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> > (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> > Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> > 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> > oracle.msbut I can find some drivers about oracle in ODBC,but must run
> > 'c:\windows\system32\odbcad32.exe'
> > This proble puzzle me for some days
> You can find the 64-bit OleDB Driver here:
> http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
> That should get things in working order.
> Jesse
>
The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
(64bit),I want to create a linked server for Oracle,I have installed ORACLE
Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
2005,i can't find 'MSDAORA',it caust i can't create linked server for
oracle.msbut I can find some drivers about oracle in ODBC,but must run
'c:\windows\system32\odbcad32.exe'
This proble puzzle me for some days
--
Standing on Shoulders of Giants* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
My first guess is that the 64 version of SQL Server can only load 64-bit
drivers. This means the old OleDb driver and ODBC driver are not
compatible.
Either reinstall SQL server as 32-bit binaries or find a 64-bit
compatible driver for Oracle.
Jesse|||* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
You can find the 64-bit OleDB Driver here:
http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
That should get things in working order.
Jesse|||I haved installed 64bit Driver for Oracle,but the proble is the same,it has
other approach?
--
Standing on Shoulders of Giants
"Jesse Houwing" wrote:
> * fds2003 wrote, On 4-7-2007 12:32:
> > The server is IBM XS 466.
> > The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> > (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> > Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> > 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> > oracle.msbut I can find some drivers about oracle in ODBC,but must run
> > 'c:\windows\system32\odbcad32.exe'
> > This proble puzzle me for some days
> You can find the 64-bit OleDB Driver here:
> http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
> That should get things in working order.
> Jesse
>
Friday, February 24, 2012
64 bit linked server
I am trying to set up a linked server on a 64 bit Itanium SQL Server 2000
server to access a 32 bit SQL Server 2000 server. When I run a query in
query analyzer accessing the linked server I get the error:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: The stored procedure required to comp
lete
this operation could not be found on the server (they were supplied with the
ODBC setup disk for the SQL Server driver). Please contact your system
administrator.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowse
t
returned 0x80004005: ].
If I run a trace on the 32 bit server I see the error:
Error: 2812, Severity: 16, State: 62
Also, the trace on the 32 bit server shows a system stored procedure that
isn't on the 32 bit machine. It is
exec [Database1]..sp_tables_info_rowset_64 N'SERVICE', N'dbo', NULL
Is there a way to link from a 64 bit server to a 32 bit server?That sounds like a bug in IA64 version of sql2k. I suggest you contact PSS
for this.
Meanwhile, have you tried to create a linked server to sql2k x86 using
MSDASQL provider.
-oj
"billd101" <billd101@.newsgroup.nospam> wrote in message
news:uF4GrzGnGHA.4604@.TK2MSFTNGP02.phx.gbl...
>I am trying to set up a linked server on a 64 bit Itanium SQL Server 2000
>server to access a 32 bit SQL Server 2000 server. When I run a query in
>query analyzer accessing the linked server I get the error:
> Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'SQLOLEDB' reported an error.
> [OLE/DB provider returned message: Unspecified error]
> [OLE/DB provider returned message: The stored procedure required to
> complete this operation could not be found on the server (they were
> supplied with the ODBC setup disk for the SQL Server driver). Please
> contact your system administrator.]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRow
set
> returned 0x80004005: ].
>
> If I run a trace on the 32 bit server I see the error:
> Error: 2812, Severity: 16, State: 62
> Also, the trace on the 32 bit server shows a system stored procedure that
> isn't on the 32 bit machine. It is
> exec [Database1]..sp_tables_info_rowset_64 N'SERVICE', N'dbo', NULL
>
> Is there a way to link from a 64 bit server to a 32 bit server?
>|||Hi,
Thanks for your reply.
From your description, I understand that:
You had two SQL Server 2000, one is 64 bit, the other is 32 bit. And you
tried to link the two servers,
however you got that error.
If I have misunderstood, please let me know.
From my research, this issue is mostly caused by the system stored
procedures were not upgraded to SQL Server 2000 SP3 or SQL Server 2000 SP4.
I recommend you manually run the Instcat.sql script that is included with
SQL Server 2000 SP3 or SP4 on the 32-bit SQL Server 2000 server.
Use Windows Authentication mode
To use Windows Authentication mode to upgrade the system stored procedures
on a 32-bit instance of SQL Server 2000, follow these steps: 1. Log on to
the computer by using a Windows account that is a member of the SQL Server
sysadmin fixed server role.
2. Click Run, type cmd.exe, and then click OK.
3. At the command prompt, type one of the following commands, and then
press ENTER:
For a default instance:
osql -E -S <LinkedServerName> -i <Location>\instcat.sql
For a named instance:
osql -E -S <LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
Note <LinkedServerName>, <InstanceName>, and <Location> represent the
linked server name, the instance name, and the full path of the folder that
contains the Instcat.sql script. By default, this folder is C:\Program
Files\Microsoft SQL Server\MSSQL\Install.
Use SQL Server Authentication mode
To use SQL Server Authentication mode to upgrade the system stored
procedures on a 32-bit instance of SQL Server 2000, follow these steps: 1.
Log on to the computer by using any Windows account.
2. Click Run, type cmd.exe, and then click OK.
3. At the command prompt, type the following command, and then press ENTER:
For a default instance:
osql -U <AdminLogin> -P <AdminPassword> -S <LinkedServerName> -i
<Location>\instcat.sql
For a named instance:
osql -U <AdminLogin> -P <AdminPassword> -S
<LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
Note <AdminLogin> and <AdminPassword> represent the user account that is a
member of the SQL Server sysadmin fixed server role.
Note After you run the Instcat.sql script, many messages are generated. The
last message indicates whether the script ran successfully.
You may refer to:
http://support.microsoft.com/?id=906954
This KB article is for the client SQL 2005 64bit, it also applies to the
issue you encountered, because the servers are both SQL 2000.
If this issue persists, I appreciate you send me the SQL error logs and
dump files for further research.
My email is changliw@.microsoft.com.
If you have any other concerns, please feel free to let me know. It's my
pleasure to be of assistance.
+++++++++++++++++++++++++++
Charles Wang
Microsoft Online Partner Support
+++++++++++++++++++++++++++
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others:
https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/defaul...rnational.aspx.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Running instcat solved the problem. Thanks for your help.
"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:8x$0MPnnGHA.4612@.TK2MSFTNGXA01.phx.gbl...
> Hi,
> Thanks for your reply.
> From your description, I understand that:
> You had two SQL Server 2000, one is 64 bit, the other is 32 bit. And you
> tried to link the two servers,
> however you got that error.
> If I have misunderstood, please let me know.
> From my research, this issue is mostly caused by the system stored
> procedures were not upgraded to SQL Server 2000 SP3 or SQL Server 2000
> SP4.
> I recommend you manually run the Instcat.sql script that is included with
> SQL Server 2000 SP3 or SP4 on the 32-bit SQL Server 2000 server.
> Use Windows Authentication mode
> To use Windows Authentication mode to upgrade the system stored procedures
> on a 32-bit instance of SQL Server 2000, follow these steps: 1. Log on to
> the computer by using a Windows account that is a member of the SQL Server
> sysadmin fixed server role.
> 2. Click Run, type cmd.exe, and then click OK.
> 3. At the command prompt, type one of the following commands, and then
> press ENTER:
> For a default instance:
> osql -E -S <LinkedServerName> -i <Location>\instcat.sql
> For a named instance:
> osql -E -S <LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
> Note <LinkedServerName>, <InstanceName>, and <Location> represent the
> linked server name, the instance name, and the full path of the folder
> that
> contains the Instcat.sql script. By default, this folder is C:\Program
> Files\Microsoft SQL Server\MSSQL\Install.
> Use SQL Server Authentication mode
> To use SQL Server Authentication mode to upgrade the system stored
> procedures on a 32-bit instance of SQL Server 2000, follow these steps: 1.
> Log on to the computer by using any Windows account.
> 2. Click Run, type cmd.exe, and then click OK.
> 3. At the command prompt, type the following command, and then press
> ENTER:
> For a default instance:
> osql -U <AdminLogin> -P <AdminPassword> -S <LinkedServerName> -i
> <Location>\instcat.sql
> For a named instance:
> osql -U <AdminLogin> -P <AdminPassword> -S
> <LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
> Note <AdminLogin> and <AdminPassword> represent the user account that is a
> member of the SQL Server sysadmin fixed server role.
> Note After you run the Instcat.sql script, many messages are generated.
> The
> last message indicates whether the script ran successfully.
> You may refer to:
> http://support.microsoft.com/?id=906954
> This KB article is for the client SQL 2005 64bit, it also applies to the
> issue you encountered, because the servers are both SQL 2000.
> If this issue persists, I appreciate you send me the SQL error logs and
> dump files for further research.
> My email is changliw@.microsoft.com.
> If you have any other concerns, please feel free to let me know. It's my
> pleasure to be of assistance.
> +++++++++++++++++++++++++++
> Charles Wang
> Microsoft Online Partner Support
> +++++++++++++++++++++++++++
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/te...erview/40010469
> Others:
> https://partner.microsoft.com/US/te...upportoverview/
> If you are outside the United States, please visit our International
> Support page:
> http://support.microsoft.com/defaul...rnational.aspx.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi ,
Appreciate your update and response. I am glad to hear that the problem has
been fixed.
If you have any other questions or concerns, please do not hesitate to
contact us.
It is always our pleasure to be of assistance.
Have a nice day!
+++++++++++++++++++++++++++
Charles Wang
Microsoft Online Partner Support
+++++++++++++++++++++++++++
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others:
https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/defaul...rnational.aspx.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Just out of curiosity, what does upgrading the system stored procedures do
exactly? I'm wondering how it will affect any existing systems on the 32bit
server.
server to access a 32 bit SQL Server 2000 server. When I run a query in
query analyzer accessing the linked server I get the error:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: The stored procedure required to comp
lete
this operation could not be found on the server (they were supplied with the
ODBC setup disk for the SQL Server driver). Please contact your system
administrator.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowse
t
returned 0x80004005: ].
If I run a trace on the 32 bit server I see the error:
Error: 2812, Severity: 16, State: 62
Also, the trace on the 32 bit server shows a system stored procedure that
isn't on the 32 bit machine. It is
exec [Database1]..sp_tables_info_rowset_64 N'SERVICE', N'dbo', NULL
Is there a way to link from a 64 bit server to a 32 bit server?That sounds like a bug in IA64 version of sql2k. I suggest you contact PSS
for this.
Meanwhile, have you tried to create a linked server to sql2k x86 using
MSDASQL provider.
-oj
"billd101" <billd101@.newsgroup.nospam> wrote in message
news:uF4GrzGnGHA.4604@.TK2MSFTNGP02.phx.gbl...
>I am trying to set up a linked server on a 64 bit Itanium SQL Server 2000
>server to access a 32 bit SQL Server 2000 server. When I run a query in
>query analyzer accessing the linked server I get the error:
> Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'SQLOLEDB' reported an error.
> [OLE/DB provider returned message: Unspecified error]
> [OLE/DB provider returned message: The stored procedure required to
> complete this operation could not be found on the server (they were
> supplied with the ODBC setup disk for the SQL Server driver). Please
> contact your system administrator.]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRow
set
> returned 0x80004005: ].
>
> If I run a trace on the 32 bit server I see the error:
> Error: 2812, Severity: 16, State: 62
> Also, the trace on the 32 bit server shows a system stored procedure that
> isn't on the 32 bit machine. It is
> exec [Database1]..sp_tables_info_rowset_64 N'SERVICE', N'dbo', NULL
>
> Is there a way to link from a 64 bit server to a 32 bit server?
>|||Hi,
Thanks for your reply.
From your description, I understand that:
You had two SQL Server 2000, one is 64 bit, the other is 32 bit. And you
tried to link the two servers,
however you got that error.
If I have misunderstood, please let me know.
From my research, this issue is mostly caused by the system stored
procedures were not upgraded to SQL Server 2000 SP3 or SQL Server 2000 SP4.
I recommend you manually run the Instcat.sql script that is included with
SQL Server 2000 SP3 or SP4 on the 32-bit SQL Server 2000 server.
Use Windows Authentication mode
To use Windows Authentication mode to upgrade the system stored procedures
on a 32-bit instance of SQL Server 2000, follow these steps: 1. Log on to
the computer by using a Windows account that is a member of the SQL Server
sysadmin fixed server role.
2. Click Run, type cmd.exe, and then click OK.
3. At the command prompt, type one of the following commands, and then
press ENTER:
For a default instance:
osql -E -S <LinkedServerName> -i <Location>\instcat.sql
For a named instance:
osql -E -S <LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
Note <LinkedServerName>, <InstanceName>, and <Location> represent the
linked server name, the instance name, and the full path of the folder that
contains the Instcat.sql script. By default, this folder is C:\Program
Files\Microsoft SQL Server\MSSQL\Install.
Use SQL Server Authentication mode
To use SQL Server Authentication mode to upgrade the system stored
procedures on a 32-bit instance of SQL Server 2000, follow these steps: 1.
Log on to the computer by using any Windows account.
2. Click Run, type cmd.exe, and then click OK.
3. At the command prompt, type the following command, and then press ENTER:
For a default instance:
osql -U <AdminLogin> -P <AdminPassword> -S <LinkedServerName> -i
<Location>\instcat.sql
For a named instance:
osql -U <AdminLogin> -P <AdminPassword> -S
<LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
Note <AdminLogin> and <AdminPassword> represent the user account that is a
member of the SQL Server sysadmin fixed server role.
Note After you run the Instcat.sql script, many messages are generated. The
last message indicates whether the script ran successfully.
You may refer to:
http://support.microsoft.com/?id=906954
This KB article is for the client SQL 2005 64bit, it also applies to the
issue you encountered, because the servers are both SQL 2000.
If this issue persists, I appreciate you send me the SQL error logs and
dump files for further research.
My email is changliw@.microsoft.com.
If you have any other concerns, please feel free to let me know. It's my
pleasure to be of assistance.
+++++++++++++++++++++++++++
Charles Wang
Microsoft Online Partner Support
+++++++++++++++++++++++++++
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others:
https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/defaul...rnational.aspx.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Running instcat solved the problem. Thanks for your help.
"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:8x$0MPnnGHA.4612@.TK2MSFTNGXA01.phx.gbl...
> Hi,
> Thanks for your reply.
> From your description, I understand that:
> You had two SQL Server 2000, one is 64 bit, the other is 32 bit. And you
> tried to link the two servers,
> however you got that error.
> If I have misunderstood, please let me know.
> From my research, this issue is mostly caused by the system stored
> procedures were not upgraded to SQL Server 2000 SP3 or SQL Server 2000
> SP4.
> I recommend you manually run the Instcat.sql script that is included with
> SQL Server 2000 SP3 or SP4 on the 32-bit SQL Server 2000 server.
> Use Windows Authentication mode
> To use Windows Authentication mode to upgrade the system stored procedures
> on a 32-bit instance of SQL Server 2000, follow these steps: 1. Log on to
> the computer by using a Windows account that is a member of the SQL Server
> sysadmin fixed server role.
> 2. Click Run, type cmd.exe, and then click OK.
> 3. At the command prompt, type one of the following commands, and then
> press ENTER:
> For a default instance:
> osql -E -S <LinkedServerName> -i <Location>\instcat.sql
> For a named instance:
> osql -E -S <LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
> Note <LinkedServerName>, <InstanceName>, and <Location> represent the
> linked server name, the instance name, and the full path of the folder
> that
> contains the Instcat.sql script. By default, this folder is C:\Program
> Files\Microsoft SQL Server\MSSQL\Install.
> Use SQL Server Authentication mode
> To use SQL Server Authentication mode to upgrade the system stored
> procedures on a 32-bit instance of SQL Server 2000, follow these steps: 1.
> Log on to the computer by using any Windows account.
> 2. Click Run, type cmd.exe, and then click OK.
> 3. At the command prompt, type the following command, and then press
> ENTER:
> For a default instance:
> osql -U <AdminLogin> -P <AdminPassword> -S <LinkedServerName> -i
> <Location>\instcat.sql
> For a named instance:
> osql -U <AdminLogin> -P <AdminPassword> -S
> <LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
> Note <AdminLogin> and <AdminPassword> represent the user account that is a
> member of the SQL Server sysadmin fixed server role.
> Note After you run the Instcat.sql script, many messages are generated.
> The
> last message indicates whether the script ran successfully.
> You may refer to:
> http://support.microsoft.com/?id=906954
> This KB article is for the client SQL 2005 64bit, it also applies to the
> issue you encountered, because the servers are both SQL 2000.
> If this issue persists, I appreciate you send me the SQL error logs and
> dump files for further research.
> My email is changliw@.microsoft.com.
> If you have any other concerns, please feel free to let me know. It's my
> pleasure to be of assistance.
> +++++++++++++++++++++++++++
> Charles Wang
> Microsoft Online Partner Support
> +++++++++++++++++++++++++++
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/te...erview/40010469
> Others:
> https://partner.microsoft.com/US/te...upportoverview/
> If you are outside the United States, please visit our International
> Support page:
> http://support.microsoft.com/defaul...rnational.aspx.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi ,
Appreciate your update and response. I am glad to hear that the problem has
been fixed.
If you have any other questions or concerns, please do not hesitate to
contact us.
It is always our pleasure to be of assistance.
Have a nice day!
+++++++++++++++++++++++++++
Charles Wang
Microsoft Online Partner Support
+++++++++++++++++++++++++++
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others:
https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/defaul...rnational.aspx.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Just out of curiosity, what does upgrading the system stored procedures do
exactly? I'm wondering how it will affect any existing systems on the 32bit
server.
64 bit linked server
I am trying to set up a linked server on a 64 bit Itanium SQL Server 2000
server to access a 32 bit SQL Server 2000 server. When I run a query in
query analyzer accessing the linked server I get the error:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: The stored procedure required to complete
this operation could not be found on the server (they were supplied with the
ODBC setup disk for the SQL Server driver). Please contact your system
administrator.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
returned 0x80004005: ].
If I run a trace on the 32 bit server I see the error:
Error: 2812, Severity: 16, State: 62
Also, the trace on the 32 bit server shows a system stored procedure that
isn't on the 32 bit machine. It is
exec [Database1]..sp_tables_info_rowset_64 N'SERVICE', N'dbo', NULL
Is there a way to link from a 64 bit server to a 32 bit server?That sounds like a bug in IA64 version of sql2k. I suggest you contact PSS
for this.
Meanwhile, have you tried to create a linked server to sql2k x86 using
MSDASQL provider.
--
-oj
"billd101" <billd101@.newsgroup.nospam> wrote in message
news:uF4GrzGnGHA.4604@.TK2MSFTNGP02.phx.gbl...
>I am trying to set up a linked server on a 64 bit Itanium SQL Server 2000
>server to access a 32 bit SQL Server 2000 server. When I run a query in
>query analyzer accessing the linked server I get the error:
> Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'SQLOLEDB' reported an error.
> [OLE/DB provider returned message: Unspecified error]
> [OLE/DB provider returned message: The stored procedure required to
> complete this operation could not be found on the server (they were
> supplied with the ODBC setup disk for the SQL Server driver). Please
> contact your system administrator.]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
> returned 0x80004005: ].
>
> If I run a trace on the 32 bit server I see the error:
> Error: 2812, Severity: 16, State: 62
> Also, the trace on the 32 bit server shows a system stored procedure that
> isn't on the 32 bit machine. It is
> exec [Database1]..sp_tables_info_rowset_64 N'SERVICE', N'dbo', NULL
>
> Is there a way to link from a 64 bit server to a 32 bit server?
>|||Hi,
Thanks for your reply.
From your description, I understand that:
You had two SQL Server 2000, one is 64 bit, the other is 32 bit. And you
tried to link the two servers,
however you got that error.
If I have misunderstood, please let me know.
From my research, this issue is mostly caused by the system stored
procedures were not upgraded to SQL Server 2000 SP3 or SQL Server 2000 SP4.
I recommend you manually run the Instcat.sql script that is included with
SQL Server 2000 SP3 or SP4 on the 32-bit SQL Server 2000 server.
Use Windows Authentication mode
To use Windows Authentication mode to upgrade the system stored procedures
on a 32-bit instance of SQL Server 2000, follow these steps: 1. Log on to
the computer by using a Windows account that is a member of the SQL Server
sysadmin fixed server role.
2. Click Run, type cmd.exe, and then click OK.
3. At the command prompt, type one of the following commands, and then
press ENTER:
For a default instance:
osql -E -S <LinkedServerName> -i <Location>\instcat.sql
For a named instance:
osql -E -S <LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
Note <LinkedServerName>, <InstanceName>, and <Location> represent the
linked server name, the instance name, and the full path of the folder that
contains the Instcat.sql script. By default, this folder is C:\Program
Files\Microsoft SQL Server\MSSQL\Install.
Use SQL Server Authentication mode
To use SQL Server Authentication mode to upgrade the system stored
procedures on a 32-bit instance of SQL Server 2000, follow these steps: 1.
Log on to the computer by using any Windows account.
2. Click Run, type cmd.exe, and then click OK.
3. At the command prompt, type the following command, and then press ENTER:
For a default instance:
osql -U <AdminLogin> -P <AdminPassword> -S <LinkedServerName> -i
<Location>\instcat.sql
For a named instance:
osql -U <AdminLogin> -P <AdminPassword> -S
<LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
Note <AdminLogin> and <AdminPassword> represent the user account that is a
member of the SQL Server sysadmin fixed server role.
Note After you run the Instcat.sql script, many messages are generated. The
last message indicates whether the script ran successfully.
You may refer to:
http://support.microsoft.com/?id=906954
This KB article is for the client SQL 2005 64bit, it also applies to the
issue you encountered, because the servers are both SQL 2000.
If this issue persists, I appreciate you send me the SQL error logs and
dump files for further research.
My email is changliw@.microsoft.com.
If you have any other concerns, please feel free to let me know. It's my
pleasure to be of assistance.
+++++++++++++++++++++++++++
Charles Wang
Microsoft Online Partner Support
+++++++++++++++++++++++++++
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others:
https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||Running instcat solved the problem. Thanks for your help.
"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:8x$0MPnnGHA.4612@.TK2MSFTNGXA01.phx.gbl...
> Hi,
> Thanks for your reply.
> From your description, I understand that:
> You had two SQL Server 2000, one is 64 bit, the other is 32 bit. And you
> tried to link the two servers,
> however you got that error.
> If I have misunderstood, please let me know.
> From my research, this issue is mostly caused by the system stored
> procedures were not upgraded to SQL Server 2000 SP3 or SQL Server 2000
> SP4.
> I recommend you manually run the Instcat.sql script that is included with
> SQL Server 2000 SP3 or SP4 on the 32-bit SQL Server 2000 server.
> Use Windows Authentication mode
> To use Windows Authentication mode to upgrade the system stored procedures
> on a 32-bit instance of SQL Server 2000, follow these steps: 1. Log on to
> the computer by using a Windows account that is a member of the SQL Server
> sysadmin fixed server role.
> 2. Click Run, type cmd.exe, and then click OK.
> 3. At the command prompt, type one of the following commands, and then
> press ENTER:
> For a default instance:
> osql -E -S <LinkedServerName> -i <Location>\instcat.sql
> For a named instance:
> osql -E -S <LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
> Note <LinkedServerName>, <InstanceName>, and <Location> represent the
> linked server name, the instance name, and the full path of the folder
> that
> contains the Instcat.sql script. By default, this folder is C:\Program
> Files\Microsoft SQL Server\MSSQL\Install.
> Use SQL Server Authentication mode
> To use SQL Server Authentication mode to upgrade the system stored
> procedures on a 32-bit instance of SQL Server 2000, follow these steps: 1.
> Log on to the computer by using any Windows account.
> 2. Click Run, type cmd.exe, and then click OK.
> 3. At the command prompt, type the following command, and then press
> ENTER:
> For a default instance:
> osql -U <AdminLogin> -P <AdminPassword> -S <LinkedServerName> -i
> <Location>\instcat.sql
> For a named instance:
> osql -U <AdminLogin> -P <AdminPassword> -S
> <LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
> Note <AdminLogin> and <AdminPassword> represent the user account that is a
> member of the SQL Server sysadmin fixed server role.
> Note After you run the Instcat.sql script, many messages are generated.
> The
> last message indicates whether the script ran successfully.
> You may refer to:
> http://support.microsoft.com/?id=906954
> This KB article is for the client SQL 2005 64bit, it also applies to the
> issue you encountered, because the servers are both SQL 2000.
> If this issue persists, I appreciate you send me the SQL error logs and
> dump files for further research.
> My email is changliw@.microsoft.com.
> If you have any other concerns, please feel free to let me know. It's my
> pleasure to be of assistance.
> +++++++++++++++++++++++++++
> Charles Wang
> Microsoft Online Partner Support
> +++++++++++++++++++++++++++
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
> Others:
> https://partner.microsoft.com/US/technicalsupport/supportoverview/
> If you are outside the United States, please visit our International
> Support page:
> http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi ,
Appreciate your update and response. I am glad to hear that the problem has
been fixed.
If you have any other questions or concerns, please do not hesitate to
contact us.
It is always our pleasure to be of assistance.
Have a nice day!
+++++++++++++++++++++++++++
Charles Wang
Microsoft Online Partner Support
+++++++++++++++++++++++++++
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others:
https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||Just out of curiosity, what does upgrading the system stored procedures do
exactly? I'm wondering how it will affect any existing systems on the 32bit
server.
server to access a 32 bit SQL Server 2000 server. When I run a query in
query analyzer accessing the linked server I get the error:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: The stored procedure required to complete
this operation could not be found on the server (they were supplied with the
ODBC setup disk for the SQL Server driver). Please contact your system
administrator.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
returned 0x80004005: ].
If I run a trace on the 32 bit server I see the error:
Error: 2812, Severity: 16, State: 62
Also, the trace on the 32 bit server shows a system stored procedure that
isn't on the 32 bit machine. It is
exec [Database1]..sp_tables_info_rowset_64 N'SERVICE', N'dbo', NULL
Is there a way to link from a 64 bit server to a 32 bit server?That sounds like a bug in IA64 version of sql2k. I suggest you contact PSS
for this.
Meanwhile, have you tried to create a linked server to sql2k x86 using
MSDASQL provider.
--
-oj
"billd101" <billd101@.newsgroup.nospam> wrote in message
news:uF4GrzGnGHA.4604@.TK2MSFTNGP02.phx.gbl...
>I am trying to set up a linked server on a 64 bit Itanium SQL Server 2000
>server to access a 32 bit SQL Server 2000 server. When I run a query in
>query analyzer accessing the linked server I get the error:
> Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'SQLOLEDB' reported an error.
> [OLE/DB provider returned message: Unspecified error]
> [OLE/DB provider returned message: The stored procedure required to
> complete this operation could not be found on the server (they were
> supplied with the ODBC setup disk for the SQL Server driver). Please
> contact your system administrator.]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
> returned 0x80004005: ].
>
> If I run a trace on the 32 bit server I see the error:
> Error: 2812, Severity: 16, State: 62
> Also, the trace on the 32 bit server shows a system stored procedure that
> isn't on the 32 bit machine. It is
> exec [Database1]..sp_tables_info_rowset_64 N'SERVICE', N'dbo', NULL
>
> Is there a way to link from a 64 bit server to a 32 bit server?
>|||Hi,
Thanks for your reply.
From your description, I understand that:
You had two SQL Server 2000, one is 64 bit, the other is 32 bit. And you
tried to link the two servers,
however you got that error.
If I have misunderstood, please let me know.
From my research, this issue is mostly caused by the system stored
procedures were not upgraded to SQL Server 2000 SP3 or SQL Server 2000 SP4.
I recommend you manually run the Instcat.sql script that is included with
SQL Server 2000 SP3 or SP4 on the 32-bit SQL Server 2000 server.
Use Windows Authentication mode
To use Windows Authentication mode to upgrade the system stored procedures
on a 32-bit instance of SQL Server 2000, follow these steps: 1. Log on to
the computer by using a Windows account that is a member of the SQL Server
sysadmin fixed server role.
2. Click Run, type cmd.exe, and then click OK.
3. At the command prompt, type one of the following commands, and then
press ENTER:
For a default instance:
osql -E -S <LinkedServerName> -i <Location>\instcat.sql
For a named instance:
osql -E -S <LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
Note <LinkedServerName>, <InstanceName>, and <Location> represent the
linked server name, the instance name, and the full path of the folder that
contains the Instcat.sql script. By default, this folder is C:\Program
Files\Microsoft SQL Server\MSSQL\Install.
Use SQL Server Authentication mode
To use SQL Server Authentication mode to upgrade the system stored
procedures on a 32-bit instance of SQL Server 2000, follow these steps: 1.
Log on to the computer by using any Windows account.
2. Click Run, type cmd.exe, and then click OK.
3. At the command prompt, type the following command, and then press ENTER:
For a default instance:
osql -U <AdminLogin> -P <AdminPassword> -S <LinkedServerName> -i
<Location>\instcat.sql
For a named instance:
osql -U <AdminLogin> -P <AdminPassword> -S
<LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
Note <AdminLogin> and <AdminPassword> represent the user account that is a
member of the SQL Server sysadmin fixed server role.
Note After you run the Instcat.sql script, many messages are generated. The
last message indicates whether the script ran successfully.
You may refer to:
http://support.microsoft.com/?id=906954
This KB article is for the client SQL 2005 64bit, it also applies to the
issue you encountered, because the servers are both SQL 2000.
If this issue persists, I appreciate you send me the SQL error logs and
dump files for further research.
My email is changliw@.microsoft.com.
If you have any other concerns, please feel free to let me know. It's my
pleasure to be of assistance.
+++++++++++++++++++++++++++
Charles Wang
Microsoft Online Partner Support
+++++++++++++++++++++++++++
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others:
https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||Running instcat solved the problem. Thanks for your help.
"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:8x$0MPnnGHA.4612@.TK2MSFTNGXA01.phx.gbl...
> Hi,
> Thanks for your reply.
> From your description, I understand that:
> You had two SQL Server 2000, one is 64 bit, the other is 32 bit. And you
> tried to link the two servers,
> however you got that error.
> If I have misunderstood, please let me know.
> From my research, this issue is mostly caused by the system stored
> procedures were not upgraded to SQL Server 2000 SP3 or SQL Server 2000
> SP4.
> I recommend you manually run the Instcat.sql script that is included with
> SQL Server 2000 SP3 or SP4 on the 32-bit SQL Server 2000 server.
> Use Windows Authentication mode
> To use Windows Authentication mode to upgrade the system stored procedures
> on a 32-bit instance of SQL Server 2000, follow these steps: 1. Log on to
> the computer by using a Windows account that is a member of the SQL Server
> sysadmin fixed server role.
> 2. Click Run, type cmd.exe, and then click OK.
> 3. At the command prompt, type one of the following commands, and then
> press ENTER:
> For a default instance:
> osql -E -S <LinkedServerName> -i <Location>\instcat.sql
> For a named instance:
> osql -E -S <LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
> Note <LinkedServerName>, <InstanceName>, and <Location> represent the
> linked server name, the instance name, and the full path of the folder
> that
> contains the Instcat.sql script. By default, this folder is C:\Program
> Files\Microsoft SQL Server\MSSQL\Install.
> Use SQL Server Authentication mode
> To use SQL Server Authentication mode to upgrade the system stored
> procedures on a 32-bit instance of SQL Server 2000, follow these steps: 1.
> Log on to the computer by using any Windows account.
> 2. Click Run, type cmd.exe, and then click OK.
> 3. At the command prompt, type the following command, and then press
> ENTER:
> For a default instance:
> osql -U <AdminLogin> -P <AdminPassword> -S <LinkedServerName> -i
> <Location>\instcat.sql
> For a named instance:
> osql -U <AdminLogin> -P <AdminPassword> -S
> <LinkedServerName>\<InstanceName> -i <Location>\instcat.sql
> Note <AdminLogin> and <AdminPassword> represent the user account that is a
> member of the SQL Server sysadmin fixed server role.
> Note After you run the Instcat.sql script, many messages are generated.
> The
> last message indicates whether the script ran successfully.
> You may refer to:
> http://support.microsoft.com/?id=906954
> This KB article is for the client SQL 2005 64bit, it also applies to the
> issue you encountered, because the servers are both SQL 2000.
> If this issue persists, I appreciate you send me the SQL error logs and
> dump files for further research.
> My email is changliw@.microsoft.com.
> If you have any other concerns, please feel free to let me know. It's my
> pleasure to be of assistance.
> +++++++++++++++++++++++++++
> Charles Wang
> Microsoft Online Partner Support
> +++++++++++++++++++++++++++
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
> Others:
> https://partner.microsoft.com/US/technicalsupport/supportoverview/
> If you are outside the United States, please visit our International
> Support page:
> http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi ,
Appreciate your update and response. I am glad to hear that the problem has
been fixed.
If you have any other questions or concerns, please do not hesitate to
contact us.
It is always our pleasure to be of assistance.
Have a nice day!
+++++++++++++++++++++++++++
Charles Wang
Microsoft Online Partner Support
+++++++++++++++++++++++++++
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others:
https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||Just out of curiosity, what does upgrading the system stored procedures do
exactly? I'm wondering how it will affect any existing systems on the 32bit
server.
64 bit Implementation, and Linked Server to Access DB
Can anyone suggest a method to connect to an Access DB from 64 bit
implementation of Yukon ?
Regardless of whether I use Linked Servers or Opendatasource I get the
following error:
"The OLE DB provider "MICROSOFT.JET.OLEDB.4.0" has not been
registered."
If there isn't a 64 bit driver available ..what alternative mechanisms
are available to load data from Access ?
TIAThere is unfortunately no 64-bit version of Jet. You'll need to use a
32-bit version to move your data.
Conor
"MJKulangara" <RutgersDBA@.gmail.com> wrote in message
news:1151430037.910336.142450@.x69g2000cwx.googlegroups.com...
> Can anyone suggest a method to connect to an Access DB from 64 bit
> implementation of Yukon ?
> Regardless of whether I use Linked Servers or Opendatasource I get the
> following error:
> "The OLE DB provider "MICROSOFT.JET.OLEDB.4.0" has not been
> registered."
> If there isn't a 64 bit driver available ..what alternative mechanisms
> are available to load data from Access ?
> TIA
>
implementation of Yukon ?
Regardless of whether I use Linked Servers or Opendatasource I get the
following error:
"The OLE DB provider "MICROSOFT.JET.OLEDB.4.0" has not been
registered."
If there isn't a 64 bit driver available ..what alternative mechanisms
are available to load data from Access ?
TIAThere is unfortunately no 64-bit version of Jet. You'll need to use a
32-bit version to move your data.
Conor
"MJKulangara" <RutgersDBA@.gmail.com> wrote in message
news:1151430037.910336.142450@.x69g2000cwx.googlegroups.com...
> Can anyone suggest a method to connect to an Access DB from 64 bit
> implementation of Yukon ?
> Regardless of whether I use Linked Servers or Opendatasource I get the
> following error:
> "The OLE DB provider "MICROSOFT.JET.OLEDB.4.0" has not been
> registered."
> If there isn't a 64 bit driver available ..what alternative mechanisms
> are available to load data from Access ?
> TIA
>
64 bit Implementation, and Linked Server to Access DB
Can anyone suggest a method to connect to an Access DB from 64 bit
implementation of Yukon ?
Regardless of whether I use Linked Servers or Opendatasource I get the
following error:
"The OLE DB provider "MICROSOFT.JET.OLEDB.4.0" has not been
registered."
If there isn't a 64 bit driver available ..what alternative mechanisms
are available to load data from Access ?
TIAThere is unfortunately no 64-bit version of Jet. You'll need to use a
32-bit version to move your data.
Conor
"MJKulangara" <RutgersDBA@.gmail.com> wrote in message
news:1151430037.910336.142450@.x69g2000cwx.googlegroups.com...
> Can anyone suggest a method to connect to an Access DB from 64 bit
> implementation of Yukon ?
> Regardless of whether I use Linked Servers or Opendatasource I get the
> following error:
> "The OLE DB provider "MICROSOFT.JET.OLEDB.4.0" has not been
> registered."
> If there isn't a 64 bit driver available ..what alternative mechanisms
> are available to load data from Access ?
> TIA
>|||There is unfortunately no 64-bit version of Jet. You'll need to use a
32-bit version to move your data.
Conor
"MJKulangara" <RutgersDBA@.gmail.com> wrote in message
news:1151430037.910336.142450@.x69g2000cwx.googlegroups.com...
> Can anyone suggest a method to connect to an Access DB from 64 bit
> implementation of Yukon ?
> Regardless of whether I use Linked Servers or Opendatasource I get the
> following error:
> "The OLE DB provider "MICROSOFT.JET.OLEDB.4.0" has not been
> registered."
> If there isn't a 64 bit driver available ..what alternative mechanisms
> are available to load data from Access ?
> TIA
>
implementation of Yukon ?
Regardless of whether I use Linked Servers or Opendatasource I get the
following error:
"The OLE DB provider "MICROSOFT.JET.OLEDB.4.0" has not been
registered."
If there isn't a 64 bit driver available ..what alternative mechanisms
are available to load data from Access ?
TIAThere is unfortunately no 64-bit version of Jet. You'll need to use a
32-bit version to move your data.
Conor
"MJKulangara" <RutgersDBA@.gmail.com> wrote in message
news:1151430037.910336.142450@.x69g2000cwx.googlegroups.com...
> Can anyone suggest a method to connect to an Access DB from 64 bit
> implementation of Yukon ?
> Regardless of whether I use Linked Servers or Opendatasource I get the
> following error:
> "The OLE DB provider "MICROSOFT.JET.OLEDB.4.0" has not been
> registered."
> If there isn't a 64 bit driver available ..what alternative mechanisms
> are available to load data from Access ?
> TIA
>|||There is unfortunately no 64-bit version of Jet. You'll need to use a
32-bit version to move your data.
Conor
"MJKulangara" <RutgersDBA@.gmail.com> wrote in message
news:1151430037.910336.142450@.x69g2000cwx.googlegroups.com...
> Can anyone suggest a method to connect to an Access DB from 64 bit
> implementation of Yukon ?
> Regardless of whether I use Linked Servers or Opendatasource I get the
> following error:
> "The OLE DB provider "MICROSOFT.JET.OLEDB.4.0" has not been
> registered."
> If there isn't a 64 bit driver available ..what alternative mechanisms
> are available to load data from Access ?
> TIA
>
Monday, February 13, 2012
400 Linked Server to SQL Server via IBMDA400
I am running V5R2 on client and am trying to link a 400 from SQL Server
2000.
Can this be done using IBMDA400?
I have gotten to a point with the IBM DB2 UDB that I can connect without
error. But now I can't see my tables.
This is what I am using for my provider string:
User ID=USERNAME;Password=PASSWORD;Initial Catalog=DATABASE_NAME;Data
Source=AS_400_SERVER_NAME
I have also checked the In Process checkbox that some have talked about
needing to be checked.
Any assistance is appreciated.
Thanks,
JasonHi,
I had the the same problem for a time, and I don't want to check all the NG
you have crossposted to, so I don't know if you already had an answer, but
here it is anyway :
Add "Catalog Library List=Lib1 Lib2 Lib3" in the connect string where "Lib1
Lib2 Lib3" is the list of your iseries library you want to browse the tables
and views. The list can be space separated or coma separated.
HTH
Christophe Niel
Remove 'nospam' to mail me.
"Jason Penner" <pennerjason@.hotmail.com> a crit dans le message de
news:%23SqrM%23A8DHA.2028@.TK2MSFTNGP10.phx.gbl...
> I am running V5R2 on client and am trying to link a 400 from SQL Server
> 2000.
> Can this be done using IBMDA400?
> I have gotten to a point with the IBM DB2 UDB that I can connect without
> error. But now I can't see my tables.
> This is what I am using for my provider string:
> User ID=USERNAME;Password=PASSWORD;Initial Catalog=DATABASE_NAME;Data
> Source=AS_400_SERVER_NAME
> I have also checked the In Process checkbox that some have talked about
> needing to be checked.
> Any assistance is appreciated.
> Thanks,
> Jason
>
2000.
Can this be done using IBMDA400?
I have gotten to a point with the IBM DB2 UDB that I can connect without
error. But now I can't see my tables.
This is what I am using for my provider string:
User ID=USERNAME;Password=PASSWORD;Initial Catalog=DATABASE_NAME;Data
Source=AS_400_SERVER_NAME
I have also checked the In Process checkbox that some have talked about
needing to be checked.
Any assistance is appreciated.
Thanks,
JasonHi,
I had the the same problem for a time, and I don't want to check all the NG
you have crossposted to, so I don't know if you already had an answer, but
here it is anyway :
Add "Catalog Library List=Lib1 Lib2 Lib3" in the connect string where "Lib1
Lib2 Lib3" is the list of your iseries library you want to browse the tables
and views. The list can be space separated or coma separated.
HTH
Christophe Niel
Remove 'nospam' to mail me.
"Jason Penner" <pennerjason@.hotmail.com> a crit dans le message de
news:%23SqrM%23A8DHA.2028@.TK2MSFTNGP10.phx.gbl...
> I am running V5R2 on client and am trying to link a 400 from SQL Server
> 2000.
> Can this be done using IBMDA400?
> I have gotten to a point with the IBM DB2 UDB that I can connect without
> error. But now I can't see my tables.
> This is what I am using for my provider string:
> User ID=USERNAME;Password=PASSWORD;Initial Catalog=DATABASE_NAME;Data
> Source=AS_400_SERVER_NAME
> I have also checked the In Process checkbox that some have talked about
> needing to be checked.
> Any assistance is appreciated.
> Thanks,
> Jason
>
Subscribe to:
Posts (Atom)