Hi,
Can anyone confirm that the 64bit edition on SQL 2000 will only run on
Itanium 64 bit machines & not Xeon 64 bit processors?
Is there an Microsoft article on this?
Regards
SteveConfirmed.
(Don't know about MS article, haven't searched KB..)
On EM64T and 64 bit OS, you can run 32 bit SQL Server with sp4 in WOW, which is supported, but
probably not what you want.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<stevanflores@.gmail.com> wrote in message
news:1142414594.177552.235650@.z34g2000cwc.googlegroups.com...
> Hi,
> Can anyone confirm that the 64bit edition on SQL 2000 will only run on
> Itanium 64 bit machines & not Xeon 64 bit processors?
> Is there an Microsoft article on this?
> Regards
> Steve
>|||Hi
Yes , 64bit runs on Itanium , but I don't remember the specific article
about that
<stevanflores@.gmail.com> wrote in message
news:1142414594.177552.235650@.z34g2000cwc.googlegroups.com...
> Hi,
> Can anyone confirm that the 64bit edition on SQL 2000 will only run on
> Itanium 64 bit machines & not Xeon 64 bit processors?
> Is there an Microsoft article on this?
> Regards
> Steve
>|||Thank you both.
We have a 32 bit application that is supposed be getting installed onto
64bit Server 2003, seeing as that we are still going to be using 32bit
SQL 2000, do you think it would be better for us to use the 32bit
version of Windows 2003?
Regards,
Steve|||IAE64 supports fully 64 bit and partially 32. Before this there was x64
allowing both architectures. As far as I know benefits (64) are visible when
you have more than 4 Gb RAM or 16 processors.
--
current location: alicante (es)
"Stevan" wrote:
> Thank you both.
> We have a 32 bit application that is supposed be getting installed onto
> 64bit Server 2003, seeing as that we are still going to be using 32bit
> SQL 2000, do you think it would be better for us to use the 32bit
> version of Windows 2003?
> Regards,
> Steve
>|||You should really look into using SQL2005 since you can run the 64 bit
edition of 2005 on Win2003 X64. But if you stay with 2000 then the 32 bit
is the only choice and it will run just fine on X64.
--
Andrew J. Kelly SQL MVP
"Stevan" <stevanflores@.gmail.com> wrote in message
news:1142415651.698599.131360@.e56g2000cwe.googlegroups.com...
> Thank you both.
> We have a 32 bit application that is supposed be getting installed onto
> 64bit Server 2003, seeing as that we are still going to be using 32bit
> SQL 2000, do you think it would be better for us to use the 32bit
> version of Windows 2003?
> Regards,
> Steve
>|||You can certainly run SQL2000 SP4 on Windows 2003 x64. And there are some
benefits right away. For instance, SQL2000 gets to use 4GB by default.
Whether these benefits will bobble up to your app level is a different story.
The only way to determine whether using Windows 2003 x64 will provide better
performance for your app is for you to conduct some tests. For the workloads
I have tested, I get better performance on Windows 2003 x64 for some
workloads and no change in performance for the others >with Windows 2003 x86
vs x64 being the only variable<.
Linchi
"Stevan" wrote:
> Thank you both.
> We have a 32 bit application that is supposed be getting installed onto
> 64bit Server 2003, seeing as that we are still going to be using 32bit
> SQL 2000, do you think it would be better for us to use the 32bit
> version of Windows 2003?
> Regards,
> Steve
>|||stevanflores@.gmail.com wrote:
> Hi,
> Can anyone confirm that the 64bit edition on SQL 2000 will only run on
> Itanium 64 bit machines & not Xeon 64 bit processors?
> Is there an Microsoft article on this?
> Regards
> Steve
64-bit IA64 Itanium is your only 64-bit option for SQL Server 2000 and
it must run on equivalent Itanium hardware.
SQL Server 2005 supports three platforms: x86, x64 (AMD64 and Intel
EM64T), and Itanium
You can run SQL Server 2000 SP4 x86 and SQL Server 2005 x86 on Windows
Server 2003 x64 Edition.
David Gugick - SQL Server MVP
Quest Software
Showing posts with label itanium. Show all posts
Showing posts with label itanium. Show all posts
Tuesday, March 6, 2012
Saturday, February 25, 2012
64 bit TextFile ConnectionString unable to dynamically change?
Hello,
On a 64bit Itanium cluster, I'm having a problem dynamically setting the ConnectionString of a TextFile Source using the "EvaluateAsExpression" = True and setting the ConnectionString using an expression from a variable. I get the error message:
-1073647612,0x,The result of the expression "@.[User::vFullFilePath]" on property "ConnectionString" cannot be written to the property. The expression was evaluated, but cannot be set on the property.
This is not a problem at all on a 32bit machine. I can run the same package on 32bit and it runs fine.
The funny thing is, I'm able to dynamically change the ConnectionString of a Logfile that we're writing all of the errors to, which I believe is using a TextFile Destination connection under the covers somehow (I'm using the SSIS Logging, to a textfile).
Can anyone confirm if this is a problem in 64bit?
Thanks,
Andy
It just dawned on me that this may be due to the fact that I'm using "LocalHost" as a servername rather than my cluster name when I set up the UNC Path. I'll change that and see if it runs. I'm guessing that has to be the problem. Silly me.Friday, February 24, 2012
64 bit Server Aliases SQL 2005
Does anyone know how to create SQL Server aliases for Itanium servers?
Alternatively does anyone know how to use SMO to create a SQLAliasCollection for a specific server? I can't seem to find how to get that collection.
I've added aliases that work for 32 bit applications but they don't seem to be used for 64 bit applications.
Please check my blog for alias. http://blogs.msdn.com/sql_protocols/archive/2007/01/07/connection-alias.aspx
You need to use 64-bit cliconfg.exe or SQL Server Connection Manager to create the alias.
|||
Thanks. It turns out alias are working fine for 64 bit and we need to add the 32 bit. The problem turned out to be that I can't connect from an Itanium Back to the itanium using a different name. When we do, NT credentials are getting blocked. We can connect to other machines using aliases, just not back to the same machine. We're investigating how to get around that at the moment :)
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 Edition and 32bit Participate in VIRTUALSQL Cluster
Does anybody know if you can mix x64 and Itanium editions?
No, absolutely not.
Itanium and x64 are differenct processor architectures. Software that uses low level services has to be written for one or the other and cannot operate on both.
Granted, there is some software that may easily execute on both -but SQL Server is NOT able to execute on both.
|||Just to be clear I was asking if an x64 and an Itanium could participate in a cluster together.. not if the software would run of the respective machines?|||There would be no point in clusting an x64 and Itanium machine together as the needed software wouldn't be able to run on both nodes.
Because the installers would be different you woulnd't be able to install SQL on the cluster.
Machines which are in a cluster should be of the same hardware architechurer.
64 bit cluster cannot connect using dtutil
Hi,
I have a 64 bit Itanium SQL Cluster that I'm trying to set up. The database engine seems fine, but I'm trying to install some SSIS packages using dtUtil and I keep getting a connection error. The error is as follows
"Login timeout expired
An error has occured 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 seetings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2}. (Microsoft SQL Native Client)"
Also, in Management studio, I can make a connection to my SSIS Server, but when I go down to the MSDB folder to look at packages I get the same connection error.
I think I was able to deploy a package using the Deployment Manifest created by VS, but I'm not sure because I can't see the package in Mgt Studio.
It almost seems like it may be related to the cluster. I'm connected in to one of the Servers using Terminal Services. But I am trying to connect to the Cluster name in Mgt Studio.
Any thoughts/ideas/Solutions greatly appreciated.
Thanks.
Andy
Another note, I was able to get the dtUtil working by using the argument /DestS, which is the destination server, and specifying the cluster name. However, I still have the issue that I can't actually use Management Studio to view these packages, I still get the above error. I'm able to run my packages using SQL Server Agent, and when I go to create a job that calls an ssis package, I'm able to see the list of packages installed on the cluster?!?! Very weird.
My main issue is I can't use Management studio to Manage my packages. Help!
Andy
|||I found the problem. Because of the cluster, the MsDtsSrvr.ini.xml file had a "." for the servername (I found this from another post that was due to 2 instances on a machine. I had to change the "." to our cluster name and now it works fine.
|||Hi,
Question for you - in your case Ingration Service runs under cluster? In my case I installed IS on 2 nodes separately, runs as a service and when I changed MsDtsSrvr.ini.xml to PC/node name, restart service it did not work. But when I changed in ini names of folder itself it presents on IS management studio.
Thanks
64 bit cluster cannot connect using dtutil
Hi,
I have a 64 bit Itanium SQL Cluster that I'm trying to set up. The database engine seems fine, but I'm trying to install some SSIS packages using dtUtil and I keep getting a connection error. The error is as follows
"Login timeout expired
An error has occured 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 seetings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2}. (Microsoft SQL Native Client)"
Also, in Management studio, I can make a connection to my SSIS Server, but when I go down to the MSDB folder to look at packages I get the same connection error.
I think I was able to deploy a package using the Deployment Manifest created by VS, but I'm not sure because I can't see the package in Mgt Studio.
It almost seems like it may be related to the cluster. I'm connected in to one of the Servers using Terminal Services. But I am trying to connect to the Cluster name in Mgt Studio.
Any thoughts/ideas/Solutions greatly appreciated.
Thanks.
Andy
Another note, I was able to get the dtUtil working by using the argument /DestS, which is the destination server, and specifying the cluster name. However, I still have the issue that I can't actually use Management Studio to view these packages, I still get the above error. I'm able to run my packages using SQL Server Agent, and when I go to create a job that calls an ssis package, I'm able to see the list of packages installed on the cluster?!?! Very weird.
My main issue is I can't use Management studio to Manage my packages. Help!
Andy
|||I found the problem. Because of the cluster, the MsDtsSrvr.ini.xml file had a "." for the servername (I found this from another post that was due to 2 instances on a machine. I had to change the "." to our cluster name and now it works fine.
|||Hi,
Question for you - in your case Ingration Service runs under cluster? In my case I installed IS on 2 nodes separately, runs as a service and when I changed MsDtsSrvr.ini.xml to PC/node name, restart service it did not work. But when I changed in ini names of folder itself it presents on IS management studio.
Thanks
Subscribe to:
Posts (Atom)