Cannot Crete server object

I'm using a client software to connect to a server. Everytime I try to log in
to that software an error: " ERROR 70: Cannot Create Servre Object". I
currently use a Microsoft Advanced server with the clients having a WIndows
XP OS.
What do I need to do?
Contact your Software Vendor. It is not a SQL Server error, but an error
that is only understood by the vendor.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"thescene" <thescene@.discussions.microsoft.com> wrote in message
news:8C17E98A-A16F-4EEF-AE8F-D32F851B63F7@.microsoft.com...
> I'm using a client software to connect to a server. Everytime I try to log
> in
> to that software an error: " ERROR 70: Cannot Create Servre Object". I
> currently use a Microsoft Advanced server with the clients having a
> WIndows
> XP OS.
> What do I need to do?
|||I just changed my switch, is that a possible reason why it's not working
anymore?
Joseph
"Mike Epprecht (SQL MVP)" wrote:

> Contact your Software Vendor. It is not a SQL Server error, but an error
> that is only understood by the vendor.
> Regards
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "thescene" <thescene@.discussions.microsoft.com> wrote in message
> news:8C17E98A-A16F-4EEF-AE8F-D32F851B63F7@.microsoft.com...
>
>
sql

cannot create jobs on x64

Hi all,
Just installed sql 2005 x64 (DB Server + Client Tools incl. management tools) on a win2003 x64 server and encountered the following problems:

1) Could not create jobs
Getting Error:

Unable to cast object of type
'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'.
(Microsoft.SqlServer.Smo)

- Tried several different job types, always same result.
- Installing SP1 does not help.
- Installing with or without Integration Service does not help.

Any help is highly appreciated

TIA
Dan

Just as a checkup, have you installed SQLExpress before on thsi machine?

refer to KBA http://support.microsoft.com/kb/922214 for more information.

|||

No express installation before.

TIA
acki

|||

Just as a little add on.

I cannot create the jobs in management console.
If I create a job by script, job shows up under SQL Server Agent / Jobs but detail view of job contains no data (no jobsteps, no schedule, no name)

If I check jobdeails in detailed Activity Monitor view all looks fine ?

Please advice

acki

|||Check here http://connect.microsoft.com/ whether this has been reported, if not I suggest to report for a fix.|||Anyone learn anything on this? I have the same problems after installing the SQL Server 2005 Service Pack 2 for XP (SQLServer2005SP2-KB921896-x86-ENU.exe)?|||

gfay

I just got this realy helpful comment on a feedback I supplied to Microsoft:

"Thanks for letting us know about the problems you faced making agent jobs.

Because the problems are in the original setup, there is no way for us to address them in a service pack. I have, however, added this issue to the work items for our next major release. "

|||

Hi Guys

We succeded create job remotly (from another computer 32 bit SQL (x86))

but when you open it from x64 edition you cannot see the steps

|||Thanks (acki4711) for the info!
|||had same problem on x86 version. Reapplying SP2 to client tools on the server was the solution for me.|||

Make sure the client and server are up to date with all patches (especially if you're on SP2) and are at the same version level.

cannot create jobs on x64

Hi all,
Just installed sql 2005 x64 (DB Server + Client Tools incl. management tools) and encountered the following problems:

1) Could not create jobs
Getting Error:

Unable to cast object of type
'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'.
(Microsoft.SqlServer.Smo)

Tried several different job types always same result?

Installing SP1 does not help?

Any help is highly appreciated

TIA
Dan

I get the same error when I try to remotly run commands. It seems to be a problem with remote connections. In my situation the server is on another domain and that may be the problem.|||

Please post this to the "SQL Server Tools General" forum.

Thanks,

Peter Saddow

|||Check whether your MS Distributed Transaction Coordinator service is running or not. If not start the service.

cannot create jobs on x64

Hi all,
Just installed sql 2005 x64 (DB Server + Client Tools incl. management tools) and encountered the following problems:

1) Could not create jobs
Getting Error:

Unable to cast object of type
'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'.
(Microsoft.SqlServer.Smo)

Tried several different job types always same result?

Installing SP1 does not help?

Any help is highly appreciated

TIA
Dan

I get the same error when I try to remotly run commands. It seems to be a problem with remote connections. In my situation the server is on another domain and that may be the problem.|||

Please post this to the "SQL Server Tools General" forum.

Thanks,

Peter Saddow

|||Check whether your MS Distributed Transaction Coordinator service is running or not. If not start the service.

cannot create jobs on x64

Hi all,
Just installed sql 2005 x64 (DB Server + Client Tools incl. management tools) on a win2003 x64 server and encountered the following problems:

1) Could not create jobs
Getting Error:

Unable to cast object of type
'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'.
(Microsoft.SqlServer.Smo)

- Tried several different job types, always same result.
- Installing SP1 does not help.
- Installing with or without Integration Service does not help.

Any help is highly appreciated

TIA
Dan

Just as a checkup, have you installed SQLExpress before on thsi machine?

refer to KBA http://support.microsoft.com/kb/922214 for more information.

|||

No express installation before.

TIA
acki

|||

Just as a little add on.

I cannot create the jobs in management console.
If I create a job by script, job shows up under SQL Server Agent / Jobs but detail view of job contains no data (no jobsteps, no schedule, no name)

If I check jobdeails in detailed Activity Monitor view all looks fine ?

Please advice

acki

|||Check here http://connect.microsoft.com/ whether this has been reported, if not I suggest to report for a fix.|||Anyone learn anything on this? I have the same problems after installing the SQL Server 2005 Service Pack 2 for XP (SQLServer2005SP2-KB921896-x86-ENU.exe)?|||

gfay

I just got this realy helpful comment on a feedback I supplied to Microsoft:

"Thanks for letting us know about the problems you faced making agent jobs.

Because the problems are in the original setup, there is no way for us to address them in a service pack. I have, however, added this issue to the work items for our next major release. "

|||

Hi Guys

We succeded create job remotly (from another computer 32 bit SQL (x86))

but when you open it from x64 edition you cannot see the steps

|||Thanks (acki4711) for the info!|||had same problem on x86 version. Reapplying SP2 to client tools on the server was the solution for me.|||

Make sure the client and server are up to date with all patches (especially if you're on SP2) and are at the same version level.

cannot create jobs on x64

Hi all,
Just installed sql 2005 x64 (DB Server + Client Tools incl. management tools) on a win2003 x64 server and encountered the following problems:

1) Could not create jobs
Getting Error:

Unable to cast object of type
'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'.
(Microsoft.SqlServer.Smo)

- Tried several different job types, always same result.
- Installing SP1 does not help.
- Installing with or without Integration Service does not help.

Any help is highly appreciated

TIA
Dan

Just as a checkup, have you installed SQLExpress before on thsi machine?

refer to KBA http://support.microsoft.com/kb/922214 for more information.

|||

No express installation before.

TIA
acki

|||

Just as a little add on.

I cannot create the jobs in management console.
If I create a job by script, job shows up under SQL Server Agent / Jobs but detail view of job contains no data (no jobsteps, no schedule, no name)

If I check jobdeails in detailed Activity Monitor view all looks fine ?

Please advice

acki

|||Check here http://connect.microsoft.com/ whether this has been reported, if not I suggest to report for a fix.|||Anyone learn anything on this? I have the same problems after installing the SQL Server 2005 Service Pack 2 for XP (SQLServer2005SP2-KB921896-x86-ENU.exe)?|||

gfay

I just got this realy helpful comment on a feedback I supplied to Microsoft:

"Thanks for letting us know about the problems you faced making agent jobs.

Because the problems are in the original setup, there is no way for us to address them in a service pack. I have, however, added this issue to the work items for our next major release. "

|||

Hi Guys

We succeded create job remotly (from another computer 32 bit SQL (x86))

but when you open it from x64 edition you cannot see the steps

|||Thanks (acki4711) for the info!|||had same problem on x86 version. Reapplying SP2 to client tools on the server was the solution for me.|||

Make sure the client and server are up to date with all patches (especially if you're on SP2) and are at the same version level.

Cannot connect with ODBC using TCP/IP?

Win 2003 Small business server with IIS being used as a web server.
Our client app can log in and run queries, but our web app when trying to log in gets the message,
'SQL server does not exsist or access denied'
The system DSN's are both sql drivers and the configuration is name pipes. Our recomended specs use TCP/IP, but when I try to change it, it craps out on me. He's opened up his firewall completely to this new box and his old box, a Win2k machine can connect using TCP/IP. This machine is in a work group.
Any suggestions on what it might be? :confused:instead of dsn, try dsn-less:
http://www.connectionstrings.com/

Cannot connect with Enterprise Manager

Hi All
I can connect to a server with Query Analyzer but not with
Enterprise manager (from a lot of clients so problem is
not client based). I used to be able to connect using
both, then all of a sudden it stopped. I rebooted the
server and Enterprise Manager connectivity worked for a
few hours and then stopped again (QA access still works!).
Can anyone think of any reason why this may be so?
Thanks
Jono
Jono
Any error message?
"Jono" <anonymous@.discussions.microsoft.com> wrote in message
news:ad9901c488df$5d5c9690$a501280a@.phx.gbl...
> Hi All
> I can connect to a server with Query Analyzer but not with
> Enterprise manager (from a lot of clients so problem is
> not client based). I used to be able to connect using
> both, then all of a sudden it stopped. I rebooted the
> server and Enterprise Manager connectivity worked for a
> few hours and then stopped again (QA access still works!).
> Can anyone think of any reason why this may be so?
> Thanks
> Jono
|||No, just hangs.

>--Original Message--
>Jono
>Any error message?
>
|||No, just hangs.

>--Original Message--
>Jono
>Any error message?
>

Cannot connect with Enterprise Manager

Hi All
I can connect to a server with Query Analyzer but not with
Enterprise manager (from a lot of clients so problem is
not client based). I used to be able to connect using
both, then all of a sudden it stopped. I rebooted the
server and Enterprise Manager connectivity worked for a
few hours and then stopped again (QA access still works!).
Can anyone think of any reason why this may be so?
Thanks
JonoJono
Any error message?
"Jono" <anonymous@.discussions.microsoft.com> wrote in message
news:ad9901c488df$5d5c9690$a501280a@.phx.gbl...
> Hi All
> I can connect to a server with Query Analyzer but not with
> Enterprise manager (from a lot of clients so problem is
> not client based). I used to be able to connect using
> both, then all of a sudden it stopped. I rebooted the
> server and Enterprise Manager connectivity worked for a
> few hours and then stopped again (QA access still works!).
> Can anyone think of any reason why this may be so?
> Thanks
> Jono|||No, just hangs.
>--Original Message--
>Jono
>Any error message?
>|||No, just hangs.
>--Original Message--
>Jono
>Any error message?
>

Cannot connect with Enterprise Manager

Hi All
I can connect to a server with Query Analyzer but not with
Enterprise manager (from a lot of clients so problem is
not client based). I used to be able to connect using
both, then all of a sudden it stopped. I rebooted the
server and Enterprise Manager connectivity worked for a
few hours and then stopped again (QA access still works!).
Can anyone think of any reason why this may be so?
Thanks
JonoJono
Any error message?
"Jono" <anonymous@.discussions.microsoft.com> wrote in message
news:ad9901c488df$5d5c9690$a501280a@.phx.gbl...
> Hi All
> I can connect to a server with Query Analyzer but not with
> Enterprise manager (from a lot of clients so problem is
> not client based). I used to be able to connect using
> both, then all of a sudden it stopped. I rebooted the
> server and Enterprise Manager connectivity worked for a
> few hours and then stopped again (QA access still works!).
> Can anyone think of any reason why this may be so?
> Thanks
> Jono|||No, just hangs.

>--Original Message--
>Jono
>Any error message?
>|||No, just hangs.

>--Original Message--
>Jono
>Any error message?
>

Cannot connect using TCP/IP protocol

Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
any advice?
What is the error number and error message?
There are some TCP/IP issues with older MDAC versions - did
you check/try updating the MDAC version on the 98 client?
-Sue
On Mon, 24 Oct 2005 01:50:02 -0700, "alex"
<alex@.discussions.microsoft.com> wrote:

>Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
>TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
>any advice?

Cannot connect using TCP/IP protocol

Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
any advice?What is the error number and error message?
There are some TCP/IP issues with older MDAC versions - did
you check/try updating the MDAC version on the 98 client?
-Sue
On Mon, 24 Oct 2005 01:50:02 -0700, "alex"
<alex@.discussions.microsoft.com> wrote:
>Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
>TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
>any advice?

Cannot connect using TCP/IP protocol

Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem
.
any advice?What is the error number and error message?
There are some TCP/IP issues with older MDAC versions - did
you check/try updating the MDAC version on the 98 client?
-Sue
On Mon, 24 Oct 2005 01:50:02 -0700, "alex"
<alex@.discussions.microsoft.com> wrote:

>Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
>TCP/IP protocol. NamePipe is OK. Other XP client can connect without proble
m.
>any advice?

Cannot connect to SQL Server from localhost (no problem from any xp client)

Hi ng!
The facts:
SQL Server 2005 is installed on a Windows 2003 server within a domain. Every
XP-Clients can connect to SQL Server via ODBC without any problems.
The problem
From the localhost I cannot connect to SQL-Server, AND from any (2) other
W2K
Server in the same domain I cannot connect to SQL Server.
Here is the original error message, in german:
SQLState: '01000'
SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
[Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
Have you any hints for me? I worked since 5 Days on this Problem...
The solution: :)
THX
Markus
PS: my german is much better...
Sorry for dubbleposting,I have not seen this ng bevor.For local, perhaps Shared Memory driver is disabled? See server config
manager, sql server 2005 network configuration tab.
For remote win2K, check surface area config for Remote Connections - are
both tcp and named pipes enables?
Also you can go to the win2K machines and set up aliases using ODBC or
native client managers.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
> Hi ng!
> The facts:
> SQL Server 2005 is installed on a Windows 2003 server within a domain.
> Every
> XP-Clients can connect to SQL Server via ODBC without any problems.
> The problem
> From the localhost I cannot connect to SQL-Server, AND from any (2) other
> W2K
> Server in the same domain I cannot connect to SQL Server.
>
> Here is the original error message, in german:
> SQLState: '01000'
> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
>
> Have you any hints for me? I worked since 5 Days on this Problem...
> The solution: :)
> THX
> Markus
> PS: my german is much better...
> Sorry for dubbleposting,I have not seen this ng bevor.
>
>|||Shared Memory is disabled.
3 Clients are XP, there are all works fine
3 Servers 2K3 (2 of this are TS): nobody can connect the database
I am only use ODBC, no native client, only tcp is activ
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krh3qgfmd58d8@.corp.supernews.com...
> For local, perhaps Shared Memory driver is disabled? See server config
> manager, sql server 2005 network configuration tab.
> For remote win2K, check surface area config for Remote Connections - are
> both tcp and named pipes enables?
> Also you can go to the win2K machines and set up aliases using ODBC or
> native client managers.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> Hi ng!
>> The facts:
>> SQL Server 2005 is installed on a Windows 2003 server within a domain.
>> Every
>> XP-Clients can connect to SQL Server via ODBC without any problems.
>> The problem
>> From the localhost I cannot connect to SQL-Server, AND from any (2) other
>> W2K
>> Server in the same domain I cannot connect to SQL Server.
>>
>> Here is the original error message, in german:
>> SQLState: '01000'
>> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
>> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
>> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
>> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
>>
>> Have you any hints for me? I worked since 5 Days on this Problem...
>> The solution: :)
>> THX
>> Markus
>> PS: my german is much better...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>|||Local connections on same box will attempt to use Shared Mem IIRC, so try
with it enabled.
You say you use only ODBC, but built-in sql server tools such as QA or SSMS
use whatever their default is set up to be, which could be named pipes. Try
forcibly setting the connection mechanism to tcp and see if it works.
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
> Shared Memory is disabled.
> 3 Clients are XP, there are all works fine
> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
> I am only use ODBC, no native client, only tcp is activ
> Markus
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server config
>> manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections - are
>> both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> Hi ng!
>> The facts:
>> SQL Server 2005 is installed on a Windows 2003 server within a domain.
>> Every
>> XP-Clients can connect to SQL Server via ODBC without any problems.
>> The problem
>> From the localhost I cannot connect to SQL-Server, AND from any (2)
>> other W2K
>> Server in the same domain I cannot connect to SQL Server.
>>
>> Here is the original error message, in german:
>> SQLState: '01000'
>> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
>> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
>> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
>> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
>>
>> Have you any hints for me? I worked since 5 Days on this Problem...
>> The solution: :)
>> THX
>> Markus
>> PS: my german is much better...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>|||Hi Kevin!
SSMS with tcp/ip works.
I have try to connect via MSSMS to connect from a w2k3 serve to the other
w2k3 Server (SQL Server), this works.
The only thing is, I cannot connect via ODBC from local host or any other
W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
Workstion without problems.
The ODBC - Driver Config is the same on XP ans W2k3. I think the only
differnt ist the ODBC Driver Version:
On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
on W2K3 : 2000.86.3959.00
I am not use the native client, shared memory and tcp/ip is on, the rest
off, SQL Native Client: all is off
\\sqlserver\myprog is always map to s:\
myprog.exe and myprog.ini is always the same
My connection string looks like this (with and without integratet security):
DSN=MYPROG_MSSQL;Database=MYPROG
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password;Trusted_Connection=No;Encrypt=No;
Any Ideas?
THX in advanced
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krpmsnuutd460@.corp.supernews.com...
> Local connections on same box will attempt to use Shared Mem IIRC, so try
> with it enabled.
> You say you use only ODBC, but built-in sql server tools such as QA or
> SSMS use whatever their default is set up to be, which could be named
> pipes. Try forcibly setting the connection mechanism to tcp and see if it
> works.
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Shared Memory is disabled.
>> 3 Clients are XP, there are all works fine
>> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
>> I am only use ODBC, no native client, only tcp is activ
>> Markus
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server config
>> manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections - are
>> both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> Hi ng!
>> The facts:
>> SQL Server 2005 is installed on a Windows 2003 server within a domain.
>> Every
>> XP-Clients can connect to SQL Server via ODBC without any problems.
>> The problem
>> From the localhost I cannot connect to SQL-Server, AND from any (2)
>> other W2K
>> Server in the same domain I cannot connect to SQL Server.
>>
>> Here is the original error message, in german:
>> SQLState: '01000'
>> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
>> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
>> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
>> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
>>
>> Have you any hints for me? I worked since 5 Days on this Problem...
>> The solution: :)
>> THX
>> Markus
>> PS: my german is much better...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>>
>|||Sorry - I have exhausted my ideas on this one. Time to give MS Support a
call!
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi Kevin!
> SSMS with tcp/ip works.
>
> I have try to connect via MSSMS to connect from a w2k3 serve to the other
> w2k3 Server (SQL Server), this works.
> The only thing is, I cannot connect via ODBC from local host or any other
> W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
> Workstion without problems.
> The ODBC - Driver Config is the same on XP ans W2k3. I think the only
> differnt ist the ODBC Driver Version:
> On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
> on W2K3 : 2000.86.3959.00
> I am not use the native client, shared memory and tcp/ip is on, the rest
> off, SQL Native Client: all is off
>
> \\sqlserver\myprog is always map to s:\
> myprog.exe and myprog.ini is always the same
> My connection string looks like this (with and without integratet
> security):
> DSN=MYPROG_MSSQL;Database=MYPROG
> -or-
> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password
> -or-
> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password;Trusted_Connection=No;Encrypt=No;
>
> Any Ideas?
> THX in advanced
> Markus
>
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krpmsnuutd460@.corp.supernews.com...
>> Local connections on same box will attempt to use Shared Mem IIRC, so try
>> with it enabled.
>> You say you use only ODBC, but built-in sql server tools such as QA or
>> SSMS use whatever their default is set up to be, which could be named
>> pipes. Try forcibly setting the connection mechanism to tcp and see if
>> it works.
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Shared Memory is disabled.
>> 3 Clients are XP, there are all works fine
>> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
>> I am only use ODBC, no native client, only tcp is activ
>> Markus
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server config
>> manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections -
>> are both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> Hi ng!
>> The facts:
>> SQL Server 2005 is installed on a Windows 2003 server within a domain.
>> Every
>> XP-Clients can connect to SQL Server via ODBC without any problems.
>> The problem
>> From the localhost I cannot connect to SQL-Server, AND from any (2)
>> other W2K
>> Server in the same domain I cannot connect to SQL Server.
>>
>> Here is the original error message, in german:
>> SQLState: '01000'
>> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
>> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
>> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
>> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
>>
>> Have you any hints for me? I worked since 5 Days on this Problem...
>> The solution: :)
>> THX
>> Markus
>> PS: my german is much better...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>>
>>
>|||Hi Kevin,
when I set my Programm "compatible with XP" (in Programm properties), then
the connection works!
But its not a real solution, so I have to connect from 2 Servers and the
property dialog for compatible mode is only availible on a local drive.
Any Ideas?
Thx
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13kui5qdav3mqed@.corp.supernews.com...
> Sorry - I have exhausted my ideas on this one. Time to give MS Support a
> call!
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hi Kevin!
>> SSMS with tcp/ip works.
>>
>> I have try to connect via MSSMS to connect from a w2k3 serve to the other
>> w2k3 Server (SQL Server), this works.
>> The only thing is, I cannot connect via ODBC from local host or any other
>> W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
>> Workstion without problems.
>> The ODBC - Driver Config is the same on XP ans W2k3. I think the only
>> differnt ist the ODBC Driver Version:
>> On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
>> on W2K3 : 2000.86.3959.00
>> I am not use the native client, shared memory and tcp/ip is on, the rest
>> off, SQL Native Client: all is off
>>
>> \\sqlserver\myprog is always map to s:\
>> myprog.exe and myprog.ini is always the same
>> My connection string looks like this (with and without integratet
>> security):
>> DSN=MYPROG_MSSQL;Database=MYPROG
>> -or-
>> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password
>> -or-
>> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password;Trusted_Connection=No;Encrypt=No;
>>
>> Any Ideas?
>> THX in advanced
>> Markus
>>
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krpmsnuutd460@.corp.supernews.com...
>> Local connections on same box will attempt to use Shared Mem IIRC, so
>> try with it enabled.
>> You say you use only ODBC, but built-in sql server tools such as QA or
>> SSMS use whatever their default is set up to be, which could be named
>> pipes. Try forcibly setting the connection mechanism to tcp and see if
>> it works.
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Shared Memory is disabled.
>> 3 Clients are XP, there are all works fine
>> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
>> I am only use ODBC, no native client, only tcp is activ
>> Markus
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server
>> config manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections -
>> are both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> Hi ng!
>> The facts:
>> SQL Server 2005 is installed on a Windows 2003 server within a
>> domain. Every
>> XP-Clients can connect to SQL Server via ODBC without any problems.
>> The problem
>> From the localhost I cannot connect to SQL-Server, AND from any (2)
>> other W2K
>> Server in the same domain I cannot connect to SQL Server.
>>
>> Here is the original error message, in german:
>> SQLState: '01000'
>> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
>> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
>> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
>> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL
>> Sicherheitsfehler
>>
>> Have you any hints for me? I worked since 5 Days on this Problem...
>> The solution: :)
>> THX
>> Markus
>> PS: my german is much better...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>>
>>
>>
>

Cannot connect to SQL Server from localhost (no problem from any xp client)

Hi ng!
The facts:
SQL Server 2005 is installed on a Windows 2003 server within a domain. Every
XP-Clients can connect to SQL Server via ODBC without any problems.
The problem
From the localhost I cannot connect to SQL-Server, AND from any (2) other
W2K
Server in the same domain I cannot connect to SQL Server.
Here is the original error message, in german:
SQLState: '01000'
SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
Driver]& #91;SharedMemory]ConnectionOpen(SECDoCli
entHandshake())-
Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
[Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheits
fehler
Have you any hints for me? I worked since 5 Days on this Problem...
The solution:
THX
Markus
PS: my german is much better...
Sorry for dubbleposting,I have not seen this ng bevor.For local, perhaps Shared Memory driver is disabled? See server config
manager, sql server 2005 network configuration tab.
For remote win2K, check surface area config for Remote Connections - are
both tcp and named pipes enables?
Also you can go to the win2K machines and set up aliases using ODBC or
native client managers.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
> Hi ng!
> The facts:
> SQL Server 2005 is installed on a Windows 2003 server within a domain.
> Every
> XP-Clients can connect to SQL Server via ODBC without any problems.
> The problem
> From the localhost I cannot connect to SQL-Server, AND from any (2) other
> W2K
> Server in the same domain I cannot connect to SQL Server.
>
> Here is the original error message, in german:
> SQLState: '01000'
> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
> Driver]& #91;SharedMemory]ConnectionOpen(SECDoCli
entHandshake())-
> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherhei
tsfehler
>
> Have you any hints for me? I worked since 5 Days on this Problem...
> The solution:
> THX
> Markus
> PS: my german is much better...
> Sorry for dubbleposting,I have not seen this ng bevor.
>
>|||Shared Memory is disabled.
3 Clients are XP, there are all works fine
3 Servers 2K3 (2 of this are TS): nobody can connect the database
I am only use ODBC, no native client, only tcp is activ
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krh3qgfmd58d8@.corp.supernews.com...
> For local, perhaps Shared Memory driver is disabled? See server config
> manager, sql server 2005 network configuration tab.
> For remote win2K, check surface area config for Remote Connections - are
> both tcp and named pipes enables?
> Also you can go to the win2K machines and set up aliases using ODBC or
> native client managers.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>|||Local connections on same box will attempt to use Shared Mem IIRC, so try
with it enabled.
You say you use only ODBC, but built-in sql server tools such as QA or SSMS
use whatever their default is set up to be, which could be named pipes. Try
forcibly setting the connection mechanism to tcp and see if it works.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
> Shared Memory is disabled.
> 3 Clients are XP, there are all works fine
> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
> I am only use ODBC, no native client, only tcp is activ
> Markus
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krh3qgfmd58d8@.corp.supernews.com...
>|||Hi Kevin!
SSMS with tcp/ip works.
I have try to connect via MSSMS to connect from a w2k3 serve to the other
w2k3 Server (SQL Server), this works.
The only thing is, I cannot connect via ODBC from local host or any other
W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
Workstion without problems.
The ODBC - Driver Config is the same on XP ans W2k3. I think the only
differnt ist the ODBC Driver Version:
On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
on W2K3 : 2000.86.3959.00
I am not use the native client, shared memory and tcp/ip is on, the rest
off, SQL Native Client: all is off
\\sqlserver\myprog is always map to s:\
myprog.exe and myprog.ini is always the same
My connection string looks like this (with and without integratet security):
DSN=MYPROG_MSSQL;Database=MYPROG
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password;Trusted_Connection=No;E
ncrypt=No;
Any Ideas?
THX in advanced
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krpmsnuutd460@.corp.supernews.com...
> Local connections on same box will attempt to use Shared Mem IIRC, so try
> with it enabled.
> You say you use only ODBC, but built-in sql server tools such as QA or
> SSMS use whatever their default is set up to be, which could be named
> pipes. Try forcibly setting the connection mechanism to tcp and see if it
> works.
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>|||Sorry - I have exhausted my ideas on this one. Time to give MS Support a
call!
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi Kevin!
> SSMS with tcp/ip works.
>
> I have try to connect via MSSMS to connect from a w2k3 serve to the other
> w2k3 Server (SQL Server), this works.
> The only thing is, I cannot connect via ODBC from local host or any other
> W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
> Workstion without problems.
> The ODBC - Driver Config is the same on XP ans W2k3. I think the only
> differnt ist the ODBC Driver Version:
> On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
> on W2K3 : 2000.86.3959.00
> I am not use the native client, shared memory and tcp/ip is on, the rest
> off, SQL Native Client: all is off
>
> \\sqlserver\myprog is always map to s:\
> myprog.exe and myprog.ini is always the same
> My connection string looks like this (with and without integratet
> security):
> DSN=MYPROG_MSSQL;Database=MYPROG
> -or-
> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password
> -or-
> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password;Trusted_Connection=No
;Encrypt=No;
>
> Any Ideas?
> THX in advanced
> Markus
>
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krpmsnuutd460@.corp.supernews.com...
>|||Hi Kevin,
when I set my Programm "compatible with XP" (in Programm properties), then
the connection works!
But its not a real solution, so I have to connect from 2 Servers and the
property dialog for compatible mode is only availible on a local drive.
Any Ideas?
Thx
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13kui5qdav3mqed@.corp.supernews.com...
> Sorry - I have exhausted my ideas on this one. Time to give MS Support a
> call!
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
>

cannot connect to sql server 2005 from xp client when trying to create ODBC dsn

Newbie here,

I am trying to link tables from an access 2003 frontend to sql server 2005 backend.

I am doing this in a vmware test environment. I am using vmware server and running sbs 2003 and xp sp2 client. Both virtaul machine can talk to each other(using local host connection).

I have tried to create a dsn to the sql server but i cannot connect. I can ping the sbs server through the command interface but the error i get when i try to connect is :

Connection failed:
Sql state: hyt00
sqlserver error: 0
microsoft odbc sql server driver timeout expired.

spent a day trying various combinations - still no joy.

Any help would be much appreciatedvirtual machines are nothing but trouble. open a query window and execute SELECT @.@.SERVERNAME|||Thank you for your reply,

I would agree vmware is not the best scenario - but as i am new to sql server - and i am about to upsize an access mdb backend to sql server 2005 so I thought some sort of test environment was required. I didn't fancy multiple installs on our production sbs until i got it right.

So from your post - is it possible to create a linked table between access 2003 and sql server 2005 from an access 2003 query window? If so, what would the syntax be if the sbs server was called 'sbs1' and the database on the sql server's default instance was named 'db1'? Or was your code to simply test the connectivity of the sql server?

The ultimate goal is a distributed access mde residing on xp sp2 clients created from an access mdb stored on a restricted network share that has linked tables to sql server 2005.

I do not even wish to go down the dsn road - would prefer the dsn-less road if possible - but i cannot proceed much further with that until i learn more about server logins, user id's and application roles etc and how passwords and user id's will be transferred accross network or stored on local machines. Hence I'm starting with dsn's and testing how to link the tables.

Any advice/guidance would be appreciated.|||I was eventually able to connect using named pipes - syntax had eluded me until i got lucky - server name 'sbs1' and pipe name was 'sbs1'.

So thats one hurdle - the next is which dsn settings to use - which server logins to use and which server roles to use.

The ultimate goal is a distributed access mde residing on xp sp2 clients created from an access mdb stored on a restricted network share that has linked tables to sql server 2005. Approx 4 users will have the abilty to link and import tables from sql server - all other users will be using an mde.

Any advice?

Cannot connect to SQL 2000 remotely

I'm trying to install a bespoke application for a new client, and am
embarassed by not being able to connect to their DB Server.
The server and clients are XP all running on a workgroup called OFFICE
File access is not problem and the DB Server name appears in a dropdown box
of SQL servers on the network - e.g. when trying to create an ODBC DSN.
The SQL Server is now configured to accept Windows and SQL authentication
connection requests - and restarted.
I have switched off or uninstalled everything that looks like a firewall on
both server and clients.
When trying to set up local ODBC DSN to connect as sa, I can connect no
problem, but from one of the client laptops I just get the error:
"Access denied or SQL Server does not exist"
Can anyone tell me where else to look or what else to try?
Is there a step by step procedure which could take me to the cause of the
problem?
The network is a wireless Lan - and IPX/SPX is featuring in the network
stack. Could that be something to do with it?
Any help very very much appreaciated!
Thank you
Clive (London UK)On the server, from the Start menu, point to All Programs, point to
Microsoft SQL Server, and then click Server Network Utility. That utility
should help you understand if SQL Server is using the IPX/SPX or TCP/IP
protocols, which might indicate a problem. On the client there is a similar
program, the Client Network Utility. Obviously the client and server should
be using the same protocols.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
news:OxUCSSVyHHA.5856@.TK2MSFTNGP02.phx.gbl...
> I'm trying to install a bespoke application for a new client, and am
> embarassed by not being able to connect to their DB Server.
> The server and clients are XP all running on a workgroup called OFFICE
> File access is not problem and the DB Server name appears in a dropdown
> box of SQL servers on the network - e.g. when trying to create an ODBC
> DSN.
> The SQL Server is now configured to accept Windows and SQL authentication
> connection requests - and restarted.
> I have switched off or uninstalled everything that looks like a firewall
> on both server and clients.
> When trying to set up local ODBC DSN to connect as sa, I can connect no
> problem, but from one of the client laptops I just get the error:
> "Access denied or SQL Server does not exist"
> Can anyone tell me where else to look or what else to try?
> Is there a step by step procedure which could take me to the cause of the
> problem?
> The network is a wireless Lan - and IPX/SPX is featuring in the network
> stack. Could that be something to do with it?
> Any help very very much appreaciated!
> Thank you
> Clive (London UK)
>
>
>
>|||Could it be because the default MSDE 2000 sp3a setup is to Disable network
protocols?
It seems that you can't rely on the setup utility to warn of this kind of
change between sp3 and sp3a. You just have to make sure you read all the
gumf every time - just in case they've decided to quietly cripple your
system this time.
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:1CAB65A1-509E-4338-8C33-65D98FDA7300@.microsoft.com...
> On the server, from the Start menu, point to All Programs, point to
> Microsoft SQL Server, and then click Server Network Utility. That utility
> should help you understand if SQL Server is using the IPX/SPX or TCP/IP
> protocols, which might indicate a problem. On the client there is a
> similar program, the Client Network Utility. Obviously the client and
> server should be using the same protocols.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
> news:OxUCSSVyHHA.5856@.TK2MSFTNGP02.phx.gbl...
>|||Apologies for flame throwing. Default of DisableNetworkProtocols WAS the
problem, but in any case
thank for taking the time and trouble to get back to me Rick.
Clive Elsworth
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:1CAB65A1-509E-4338-8C33-65D98FDA7300@.microsoft.com...
> On the server, from the Start menu, point to All Programs, point to
> Microsoft SQL Server, and then click Server Network Utility. That utility
> should help you understand if SQL Server is using the IPX/SPX or TCP/IP
> protocols, which might indicate a problem. On the client there is a
> similar program, the Client Network Utility. Obviously the client and
> server should be using the same protocols.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
> news:OxUCSSVyHHA.5856@.TK2MSFTNGP02.phx.gbl...
>|||Glad to help. I recognize customers stress and confusion as a problem that
we (Microsoft) often cause... and have an obligation to resolve.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
news:O7J9R4pzHHA.3400@.TK2MSFTNGP03.phx.gbl...
> Apologies for flame throwing. Default of DisableNetworkProtocols WAS the
> problem, but in any case
> thank for taking the time and trouble to get back to me Rick.
> Clive Elsworth
>
>
> "Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
> news:1CAB65A1-509E-4338-8C33-65D98FDA7300@.microsoft.com...
>

Cannot connect to MSDE on SBS 2003

My client has installed e scanner program wich is suposed til run on a MSDE
database. The program has to run on a reasently installed SBS 2003 server.
The server is installed with only standard features, the isa server is not
installed. Clients are running in a standard 2003 domain.
The program is working fine on the server but clients cannot connect. I test
from Excel to make the test as basic as possible. The primary client is a
terminal server 2000 but trying from XP machines do not make any difference.
I get the following error fra Excel:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server does not exist or
acces is denied.
To your infomation, the msde is the latest build and updates. The MDAC is
updatet on the terminalserver.
I suspect the SBS 2003 has shut down something somewhere but I have no clue
where to look. I am a total norvice in SQL.
I have checked the port 1433 an it is not "LISTENING" (nor 1434 if thats the
port) Shall it be Listening and if so, how do I get it to listen?
Michael,
I had this exact problem on one of my SBS 2003 machines running MSDE.
Often 3rd party backup software like Veritas Backup Exec, attaches to
SQL/MSDE and modifies settings. Sometimes all communication protocols
are disabled.
To fix this, on the server run 'svrnetcn' and make sure that at least
one protocol is enabled. As you checked port 1433 I assume you want to
use TCP/IP, so ensure that at least TCP is in the 'Enabled Protocols'
section.
You also need to confirm that SQL is configured to communicate via this
protocol on the client machines. To do this, run 'cliconfg' on the
client machines. You will see a similar configuration tool to the
server. Make sure the 'Enabled Protocols' match the server, ie
confirm/add TCP.
Good luck, Al.
*** Sent via Developersdex http://www.codecomments.com ***

Cannot connect to MSDE on SBS 2003

My client has installed e scanner program wich is suposed til run on a MSDE
database. The program has to run on a reasently installed SBS 2003 server.
The server is installed with only standard features, the ISA server is not
installed. Clients are running in a standard 2003 domain.
The program is working fine on the server but clients cannot connect. I test
from Excel to make the test as basic as possible. The primary client is a
terminal server 2000 but trying from XP machines do not make any difference.
I get the following error fra Excel:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Con
nect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server does not
exist or
acces is denied.
To your infomation, the msde is the latest build and updates. The MDAC is
updatet on the terminalserver.
I suspect the SBS 2003 has shut down something somewhere but I have no clue
where to look. I am a total norvice in SQL.
I have checked the port 1433 an it is not "LISTENING" (nor 1434 if thats the
port) Shall it be Listening and if so, how do I get it to listen?Michael,
I had this exact problem on one of my SBS 2003 machines running MSDE.
Often 3rd party backup software like Veritas Backup Exec, attaches to
SQL/MSDE and modifies settings. Sometimes all communication protocols
are disabled.
To fix this, on the server run 'svrnetcn' and make sure that at least
one protocol is enabled. As you checked port 1433 I assume you want to
use TCP/IP, so ensure that at least TCP is in the 'Enabled Protocols'
section.
You also need to confirm that SQL is configured to communicate via this
protocol on the client machines. To do this, run 'cliconfg' on the
client machines. You will see a similar configuration tool to the
server. Make sure the 'Enabled Protocols' match the server, ie
confirm/add TCP.
Good luck, Al.
*** Sent via Developersdex http://www.codecomments.com ***

Cannot connect to MSDE on a W2003 server

I have installed MSDE with SP3a with a instance name on a
Windwos Server 2003 Enterprise edition.
The install works fine.
I installed the client software on a W2k en W98 client
PC, the install work fine.
When i run the program, the program normaly sees the
servernaam and instance name.
This do'nt work on the Windows 2003 server. (2000 server
works fine)
Have enyone a idee?* Did you apply the SP3 version of MSDE? If not TCP will be disabled on
Windows 2003. You must apply SP3 before TCP connections (the default from a
remote client) will work.
* What error do you get when you try to connect?
* Do you get the same error from Query Analyzer, OSQL, and Enterprise
Manager or just from your application?
* If you force TCP, named pipes, or shared memory does it start working or
change the error?
* Do both remote and local connections fail for each protocol? For MSDE
2000 SP3 remote connections are disabled by default, you have to enable TCP
and/or named pipes on the server side before remote connections will work.
To Enable TCP/IP Sockets Server Net-Library
1. On the taskbar, click "Start", and then click "Run".
2. In the "Open" text box, type "svrnetcn.exe" (without the quotation
marks). Note: By default, the svrnetcn.exe is available in the
following folder: <Installation Drive>/Program Files/Microsoft SQL
Server/80/Tools/BINN
3. Click "OK".
4. In the "SQL Server Network Utility" dialog box, click "General" tab.
5. Click the desired instance of Microsoft SQL Server 2000 Desktop Engine
(Windows) or MSDE 2000 SP3a or SQL Server 2000 in the
"Instance(s) on this server" list.
6. In the "Disabled Protocols" list box, click "TCP/IP", and then click
"Enable".
7. In the "Enabled Protocols" list box, click "TCP/IP", and then click
"Properties".
8. In the "<Server Name> - TCP/IP" dialog box, in the "Default Port" text
box, type "0" (without the quotation marks), and then click "OK".
9. In the "SQL Server Network Utility" dialog box, click "OK". Note: You
may receive a message stating that the changes made will be saved, but will
take effect only after restarting the SQL Server service. In the "SQL
Server Network Utility" message box, click "OK".
10. Restart the SQL Server service of the instance of Microsoft SQL Server
2000 Desktop Engine (Windows) or MSDE 2000 SP3a or SQL Server 2000.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.