32 bit BI-tool connecting a 64 bit SQL Server 2005

Hi,

I have Cognos 8 as BI-tool installed on a Windows 2003 Server, both 32 bit. We are thinking of using a 64 bit SQL Server 2005 with 64 bit Windows 2003 Server as database server for a new data warehouse.

Can I use the 32 bit SQL Native Client on the Cognos server for connecting to the 64 bit database server? If not, how should I set this up?

Thanks in advance for your help.

Kind regards,

Albert de Ruiter.

The communication channel between SQL Client and SQL server is independent of CPU arch on either side. There are should be no problem connecting each other. You just connect to the server as usual, as if you don't know the server is 64bit. Please let us know if you have issue.|||Thank you!

3 server scenario problem

Hi
I'm having trouble connecting to an instance of SQL Server 2005 (Express)
from 2 individual Windows Server 2003 machines running IIS (asp.net 2.0)
I have an IIS on each 2k3 machine, both with identical sites. The idea is
simply that we have a third sql server which is accessed by these 2 websites.
One server gives me a Server login error (user not found:
MYDomain\ServerName), which the second server gives me the usual error 26 -
Cannot connect to Server/Instance specified.
Both IIS apps use the same query string (server=MYSQLSERVER\DARTS;
database=dartsV2;trustedconnection=yes;)
but as I say, one connects, one doesn't! very odd. Anyone got any
suggestions? I've enabled named pipes and tcp/ip on the sql server, along
with "allowing remote and local connections" using surface area config. I've
even setup SQL Browser, which seemed to cure one of the servers (both were
giving me the cannot find instance specified error).
Any suggestions guys?! I'm getting kinda desperate on this one... :o)
Cheers
Dan
Hi,
To narrow down this issue, I have serveral questions which need your
confirmation:
1. Could you ping the SQL Server successfully from the two clients?
2. What will happen if you explicitly add the two domain accounts to the
users group of your third server ?
Also, I recommend you try configuring the client settings as following:
Click the Start menu;
Type cliconfg.exe;
Check if TCP/IP and Named Pipes protocols are enabled;
Select the Alias tab;
Check if the server instance exists in the list;
If it's not existed, click the Add button;
Input the alias name (<servername>\SQLEXPRESS) for Named Pipes protocol and
click OK.
Apply the settings, and then try again.
If you want to use TCP/IP protocol, please first check the listening TCP
port on your server via SQL Server Configuration Manager.
Then add an alias for TCP/IP protocol at the clients. Note that you need to
cancel the selection of "Dynamically determin the port" and input your TCP
port number.
An alias can be different with your SQL Server instance name, but the
server name should be same as your server name.
Please ensure that you can use telnet to access your SQL Server TCP port
before configuring the alias for TCP/IP:
telnet <your server name> <port number>
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 Community Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hi Charles,
Thanks for the reply. I've actually fixed this particular issue, I simply
copied the code with the "user" error onto the other IIS server, so now I
have that error on both. However, I'll post somewhere else for that...
For clarification...
1) yes. I could also use osql (or sqlcmd) to connect to the sql server from
both domain servers, cos they both had sqle installed but no instance
running).
2) I tried that, but it couldn't find the computer accounts when I tried
adding roles etc - presumbly because they were computer accounts and not
users, I'm not sure though?
I have named pipes enabled but this is considered a security risk is it not?
However, I'm not sure how to setup a connection string with an ip address? I
tried server=xxx.xxx.xxx.xxx but it that couldn't connect from either server?
(I have both named pipes and tcp/ip enabled).
Could you point me to an article on how to do that, because if named pipes
are risky, we shouldn't be using them!
Thanks for your reply and help.
Cheers
Dan
"Charles Wang[MSFT]" wrote:

> Hi,
> To narrow down this issue, I have serveral questions which need your
> confirmation:
> 1. Could you ping the SQL Server successfully from the two clients?
> 2. What will happen if you explicitly add the two domain accounts to the
> users group of your third server ?
> Also, I recommend you try configuring the client settings as following:
> Click the Start menu;
> Type cliconfg.exe;
> Check if TCP/IP and Named Pipes protocols are enabled;
> Select the Alias tab;
> Check if the server instance exists in the list;
> If it's not existed, click the Add button;
> Input the alias name (<servername>\SQLEXPRESS) for Named Pipes protocol and
> click OK.
> Apply the settings, and then try again.
> If you want to use TCP/IP protocol, please first check the listening TCP
> port on your server via SQL Server Configuration Manager.
> Then add an alias for TCP/IP protocol at the clients. Note that you need to
> cancel the selection of "Dynamically determin the port" and input your TCP
> port number.
> An alias can be different with your SQL Server instance name, but the
> server name should be same as your server name.
> Please ensure that you can use telnet to access your SQL Server TCP port
> before configuring the alias for TCP/IP:
> telnet <your server name> <port number>
> 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 Community Support
> ================================================== ====
> When responding to posts, please "Reply to Group" via your newsreader
> so that others may learn and benefit from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
|||Hi Dan,
Thanks for your updating and response.
The user error should be caused by the windows logon account at your client
computer not matching the Windows authentication on the server.
Please check if the Windows login account is a member of the Users or
Administrators group under your SQL Server machine. You can maunually add
it to the Users group and then add it to the logins of your SQL Server 2005
Express and assign it permissions in SQL Server 2005 Express.
If you did not install the SQL Server 2005 Management Studio Express, you
can download it from:
http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-
94B8-5A0F62BF7796&DisplayLang=en
This tool provides you an UI to manage your SQL Server 2005 Express like
SQL Server 2000 Enterprise Manager.
If this issue persists, it seems that it is related to the settings of your
web application. You can try using impersonation in your web.config file:
<system.web>
...
<authentication mode = "windows" />
...
<identity impersonate="true" />
...
</system.web>
For more information, you can refer to:
Using sql trusted Connections with asp.net
http://idunno.org/dotNet/trustedConnections.aspx
If you use impersonation, please ensure that the two Windows logon accounts
of your two web application servers must be as a member of the
Users/Administrators group on your SQL Server 2005 machine and be assigned
permissions in your SQL Server 2005 Express instance.
For the second error "Cannot connect to Server/Instance specified", it is
most likely a communication level error. If you are worried about the
security of Named Pipes, you can maually configure the TCP/IP protocol by
following my first reply. Also, you can configure a static TCP port at the
server side. By using SQL Server Configuration Manager, you can specify a
static TCP port under the IP All, and leave other fields under IP1 and IP2
blank:
1. Open SQL Server Configuration Manager;
2. Select Protocols for <instance name>;
3. Double click TCP/IP, switch to the IP Address tab;
4. Specify the TCP Port under the IPAll, leave all TCP Dynamics Ports under
IP1,IP2 and IPAll blank, and leave TCP Port under IP1 and IP2 blank.
5. Click OK and restart your SQL Server service.
On the client machines, ensure that you can use telnet to connect to the
server at the TCP port. Then try adding an alias for TCP/IP by using
cliconfg.exe at the client and try again.
Please feel free to let me know if you have any other questions or
concerns.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
|||Hi Dan,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support
sql

3 server scenario problem

Hi
I'm having trouble connecting to an instance of SQL Server 2005 (Express)
from 2 individual Windows Server 2003 machines running IIS (asp.net 2.0)
I have an IIS on each 2k3 machine, both with identical sites. The idea is
simply that we have a third sql server which is accessed by these 2 websites
.
One server gives me a Server login error (user not found:
MYDomain\ServerName), which the second server gives me the usual error 26 -
Cannot connect to Server/Instance specified.
Both IIS apps use the same query string (server=MYSQLSERVER\DARTS;
database=dartsV2;trustedconnection=yes;)
but as I say, one connects, one doesn't! very odd. Anyone got any
suggestions? I've enabled named pipes and tcp/ip on the sql server, along
with "allowing remote and local connections" using surface area config. I've
even setup SQL Browser, which seemed to cure one of the servers (both were
giving me the cannot find instance specified error).
Any suggestions guys?! I'm getting kinda desperate on this one... :o)
Cheers
DanHi,
To narrow down this issue, I have serveral questions which need your
confirmation:
1. Could you ping the SQL Server successfully from the two clients?
2. What will happen if you explicitly add the two domain accounts to the
users group of your third server ?
Also, I recommend you try configuring the client settings as following:
Click the Start menu;
Type cliconfg.exe;
Check if TCP/IP and Named Pipes protocols are enabled;
Select the Alias tab;
Check if the server instance exists in the list;
If it's not existed, click the Add button;
Input the alias name (<servername>\SQLEXPRESS) for Named Pipes protocol and
click OK.
Apply the settings, and then try again.
If you want to use TCP/IP protocol, please first check the listening TCP
port on your server via SQL Server Configuration Manager.
Then add an alias for TCP/IP protocol at the clients. Note that you need to
cancel the selection of "Dynamically determin the port" and input your TCP
port number.
An alias can be different with your SQL Server instance name, but the
server name should be same as your server name.
Please ensure that you can use telnet to access your SQL Server TCP port
before configuring the alias for TCP/IP:
telnet <your server name> <port number>
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 Community Support
========================================
==============
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Hi Charles,
Thanks for the reply. I've actually fixed this particular issue, I simply
copied the code with the "user" error onto the other IIS server, so now I
have that error on both. However, I'll post somewhere else for that...
For clarification...
1) yes. I could also use osql (or sqlcmd) to connect to the sql server from
both domain servers, cos they both had sqle installed but no instance
running).
2) I tried that, but it couldn't find the computer accounts when I tried
adding roles etc - presumbly because they were computer accounts and not
users, I'm not sure though?
I have named pipes enabled but this is considered a security risk is it not?
However, I'm not sure how to setup a connection string with an ip address? I
tried server=xxx.xxx.xxx.xxx but it that couldn't connect from either server
?
(I have both named pipes and tcp/ip enabled).
Could you point me to an article on how to do that, because if named pipes
are risky, we shouldn't be using them!
Thanks for your reply and help.
Cheers
Dan
"Charles Wang[MSFT]" wrote:

> Hi,
> To narrow down this issue, I have serveral questions which need your
> confirmation:
> 1. Could you ping the SQL Server successfully from the two clients?
> 2. What will happen if you explicitly add the two domain accounts to the
> users group of your third server ?
> Also, I recommend you try configuring the client settings as following:
> Click the Start menu;
> Type cliconfg.exe;
> Check if TCP/IP and Named Pipes protocols are enabled;
> Select the Alias tab;
> Check if the server instance exists in the list;
> If it's not existed, click the Add button;
> Input the alias name (<servername>\SQLEXPRESS) for Named Pipes protocol an
d
> click OK.
> Apply the settings, and then try again.
> If you want to use TCP/IP protocol, please first check the listening TCP
> port on your server via SQL Server Configuration Manager.
> Then add an alias for TCP/IP protocol at the clients. Note that you need t
o
> cancel the selection of "Dynamically determin the port" and input your TCP
> port number.
> An alias can be different with your SQL Server instance name, but the
> server name should be same as your server name.
> Please ensure that you can use telnet to access your SQL Server TCP port
> before configuring the alias for TCP/IP:
> telnet <your server name> <port number>
> 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 Community Support
> ========================================
==============
> When responding to posts, please "Reply to Group" via your newsreader
> so that others may learn and benefit from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>|||Hi Dan,
Thanks for your updating and response.
The user error should be caused by the windows logon account at your client
computer not matching the Windows authentication on the server.
Please check if the Windows login account is a member of the Users or
Administrators group under your SQL Server machine. You can maunually add
it to the Users group and then add it to the logins of your SQL Server 2005
Express and assign it permissions in SQL Server 2005 Express.
If you did not install the SQL Server 2005 Management Studio Express, you
can download it from:
http://www.microsoft.com/downloads/...A5AE-4BD1-4E3D-
94B8-5A0F62BF7796&DisplayLang=en
This tool provides you an UI to manage your SQL Server 2005 Express like
SQL Server 2000 Enterprise Manager.
If this issue persists, it seems that it is related to the settings of your
web application. You can try using impersonation in your web.config file:
<system.web>
..
<authentication mode = "windows" />
..
<identity impersonate="true" />
..
</system.web>
For more information, you can refer to:
Using sql trusted Connections with asp.net
http://idunno.org/dotNet/trustedConnections.aspx
If you use impersonation, please ensure that the two Windows logon accounts
of your two web application servers must be as a member of the
Users/Administrators group on your SQL Server 2005 machine and be assigned
permissions in your SQL Server 2005 Express instance.
For the second error "Cannot connect to Server/Instance specified", it is
most likely a communication level error. If you are worried about the
security of Named Pipes, you can maually configure the TCP/IP protocol by
following my first reply. Also, you can configure a static TCP port at the
server side. By using SQL Server Configuration Manager, you can specify a
static TCP port under the IP All, and leave other fields under IP1 and IP2
blank:
1. Open SQL Server Configuration Manager;
2. Select Protocols for <instance name>;
3. Double click TCP/IP, switch to the IP Address tab;
4. Specify the TCP Port under the IPAll, leave all TCP Dynamics Ports under
IP1,IP2 and IPAll blank, and leave TCP Port under IP1 and IP2 blank.
5. Click OK and restart your SQL Server service.
On the client machines, ensure that you can use telnet to connect to the
server at the TCP port. Then try adding an alias for TCP/IP by using
cliconfg.exe at the client and try again.
Please feel free to let me know if you have any other questions or
concerns.
Sincerely yours,
Charles Wang
Microsoft Online Community Support|||Hi Dan,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support

2005: cannot to connect from .NET

Hello,
Could you help me please to solve the prblem with connecting to SQL Server
from .NET development environment?
I have the following error:

"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 setting SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could nott open a connection to
SQL Server)

Please help. I changed option for remote connections but it doesn't help.
/RAM/RAM (r_ahimsa_m@.poczta.onet.pl) writes:

Quote:

Originally Posted by

Could you help me please to solve the prblem with connecting to SQL Server
from .NET development environment?
I have the following error:
>
"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 setting SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could nott
open a connection to SQL Server)
>
Please help. I changed option for remote connections but it doesn't help.

Does the server accept connection from Named Pipes? Check this in
the SQL Server Configuration Manager.

Have you tried to connect over TCP/IP.

Also check firewalls etc.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Does the server accept connection from Named Pipes? Check this in

Quote:

Originally Posted by

the SQL Server Configuration Manager.

Yes

Quote:

Originally Posted by

Have you tried to connect over TCP/IP.

I am configuring data source. The message is displayed in Visual Web
Developer, the problem is not in source code.|||RAM (r_ahimsa_m@.poczta.onet.pl) writes:

Quote:

Originally Posted by

Quote:

Originally Posted by

>Does the server accept connection from Named Pipes? Check this in
>the SQL Server Configuration Manager.

>
Yes

And client and server agree on the name of the pipe?

Quote:

Originally Posted by

Quote:

Originally Posted by

>Have you tried to connect over TCP/IP.

>
I am configuring data source. The message is displayed in Visual Web
Developer, the problem is not in source code.

Eh? Whether you configure a data source, have a program, or connect from
a tool like SSMS has nothing do with it. You can still set up the connection
to use TCP/IP. Usually TCP/IP is preferrable over named pipes.

Sorry, but I can't help more, because know next to nothing about your
machines. Are client and server on the same machine or different? Is the
instance a named instance or a default instance?

Did you check that the SQL Server Browser service is running and accepts
remote connections?

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||I have noticed something interesting.
The problem occurs when I am configuring data source control. The connection
string is taken from web.config:
<add name="MIMMagazynDemo" connectionString="Data Source=localhost;Initial
Catalog=MIMMagazynDemo;Integrated Security=True"
providerName="System.Data.SqlClient" />

I have noticed that the problem do not exist when I change localhost to
PC\SQLEXPRESS (PC is name of my computer).

Could you explain me why? Thank you!

/RAM/|||RAM (r_ahimsa_m@.poczta.onet.pl) writes:

Quote:

Originally Posted by

I have noticed something interesting.
The problem occurs when I am configuring data source control. The
connection string is taken from web.config:
><add name="MIMMagazynDemo" connectionString="Data Source=localhost;Initial
Catalog=MIMMagazynDemo;Integrated Security=True"
providerName="System.Data.SqlClient" />
>
I have noticed that the problem do not exist when I change localhost to
PC\SQLEXPRESS (PC is name of my computer).
>
Could you explain me why? Thank you!

SQL Server permits you to install several instances on the same machine.
One of these instances can be a default instances, all other instances
must be named.

When you refer to a default instance, you refer only to the machine name,
or, if you are on the machine itself, you can use ".", "localhost" or
"(local)" instead.

When you refer to a named instance, you must also include the instance
name separated from the machine name with a backslash, for instance
MYSERVER\MY2NDINSTANCE.

By default, SQL Server Express is installed as a named instance as
SQLEXPRESS, and thus "localhost" alone will not work on a machine that
only has SQL Express.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Thank you very much

Uzytkownik "Erland Sommarskog" <esquel@.sommarskog.senapisal w wiadomosci
news:Xns98189D268B5C9Yazorman@.127.0.0.1...

Quote:

Originally Posted by

RAM (r_ahimsa_m@.poczta.onet.pl) writes:

Quote:

Originally Posted by

>I have noticed something interesting.
>The problem occurs when I am configuring data source control. The
>connection string is taken from web.config:
>><add name="MIMMagazynDemo" connectionString="Data Source=localhost;Initial
>Catalog=MIMMagazynDemo;Integrated Security=True"
>providerName="System.Data.SqlClient" />
>>
>I have noticed that the problem do not exist when I change localhost to
>PC\SQLEXPRESS (PC is name of my computer).
>>
>Could you explain me why? Thank you!

>
SQL Server permits you to install several instances on the same machine.
One of these instances can be a default instances, all other instances
must be named.
>
When you refer to a default instance, you refer only to the machine name,
or, if you are on the machine itself, you can use ".", "localhost" or
"(local)" instead.
>
When you refer to a named instance, you must also include the instance
name separated from the machine name with a backslash, for instance
MYSERVER\MY2NDINSTANCE.
>
By default, SQL Server Express is installed as a named instance as
SQLEXPRESS, and thus "localhost" alone will not work on a machine that
only has SQL Express.
>
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

2005 Reporting Srv cannot connect to Oracle datasource on web server

created an Oracle datasource (tried both ole db & oracle client) in Visual Studio 2005 report project - works fine connecting and preview of report within ide , deployed to Reporting Services web server, received the following error when attempting to run the report on web server:

An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'oracle'. (rsErrorOpeningConnection)
System.Data.OracleClient requires Oracle client software version 8.1.7 or greater.

web server has oracle client 9i client installed and connecting to db ok through sql plus (this server also is loaded with VS2005 and the SqlServer2005 db)

any thoughts or direction greatly appreciated

Most likely the RS web service and the RS windows service cannot access the Oracle client installation due to missing file system permissions. Please read the following KB article: http://support.microsoft.com/default.aspx?scid=kb;en-us;870668

-- Robert

|||

Robert,

Thanks for the help, this did in fact solve the issue (once the permissions were granted for the entire Oracle directory). Why would such a helpful article not show up in my searches through the help maze? Is there another entry point to search for these articles other than the help search engine?

thanks again,

Richard

|||

Wow this really helped me out also, had the exact same problem. Thanks. I too had to set the permissions for the entire Oracle directory for this to work. Also take note of which account your installation is using, mine wasn't using the Network Service account but instead a special service account created by the system admins, I had to set the permissions for that account on the folders.

Dave

2005 Reporting Srv cannot connect to Oracle datasource on web server

created an Oracle datasource (tried both ole db & oracle client) in Visual Studio 2005 report project - works fine connecting and preview of report within ide , deployed to Reporting Services web server, received the following error when attempting to run the report on web server:

An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'oracle'. (rsErrorOpeningConnection)
System.Data.OracleClient requires Oracle client software version 8.1.7 or greater.

web server has oracle client 9i client installed and connecting to db ok through sql plus (this server also is loaded with VS2005 and the SqlServer2005 db)

any thoughts or direction greatly appreciated

Most likely the RS web service and the RS windows service cannot access the Oracle client installation due to missing file system permissions. Please read the following KB article: http://support.microsoft.com/default.aspx?scid=kb;en-us;870668

-- Robert

|||

Robert,

Thanks for the help, this did in fact solve the issue (once the permissions were granted for the entire Oracle directory). Why would such a helpful article not show up in my searches through the help maze? Is there another entry point to search for these articles other than the help search engine?

thanks again,

Richard

|||

Wow this really helped me out also, had the exact same problem. Thanks. I too had to set the permissions for the entire Oracle directory for this to work. Also take note of which account your installation is using, mine wasn't using the Network Service account but instead a special service account created by the system admins, I had to set the permissions for that account on the folders.

Dave

2005 Remote Connection Error

Hi,

Hope someone can help with this, having a huge problem connecting to SQL 2005 from a client machine. I get the following error:

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

I have SQL 2005 installed on a server containing SQL 2000 (default instance) and then SQL 2005 as the instance SERVER\SQL2005. 2005 is running SP1. I'm connecting via windows authentication, using just using Management Studio. I've also configured the server to accept remote connections.

I can connect locally to the 2005 instance. Does anyone have any ideas why this might be happening?

Thanks

Jeremy

See my Screencast about Remote connections on my site which describes in detail how to enable remote connections.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Thanks for the reply Jens,

I have definitely enable remote connections already. Do you have any other ideas?

Thanks

Jeremy

|||Can anyone help with this?|||

Sorry for not coming back earlier, lsot the focus on the post. DO you have SQL Server Browser started on the server ? SQL Browser will redirect the client request to connect to the assigned port without naming explictly the port of the SQL Server. If you don′t start the browser on the server, the client will try to connect to the port 1433 which might not be used by the named instance. If you know the port of the named instance, you can also specify that directly within the connection string using servername\instanceName,Portnumber.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

2005 connecting 2000 ?

if I install SServer Express Edition
Can I connect to SServer 2000 DB ?

thanksYes, but you can't use the database designer.

klabu wrote:

Quote:

Originally Posted by

if I install SServer Express Edition
Can I connect to SServer 2000 DB ?
>
thanks