|
Home > Archive > Microsoft SQL Server Desktop Engine > May 2005 > MSDE Connectivity Problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
MSDE Connectivity Problem
|
|
|
| I'm baffled at the following MSDE connectivity problem:
After installing MSDE 2000 SP3a (and hotfix 8.00.0818-enu) on a workstation
(XP, SP2), I get the following error when trying to connect to the database
using OSQL:
[DBMSLPCN]SQL Server does not exist or access denied.
& #91;DBMSLPCN]Connect
ionOpen (Connect()).
However, if I open REGEDIT to the
HKEY_LOCAL_MACHINE\S
OFTWARE\Microsoft\Mi
crosoft SQL Server key, I can connect
without issue. If REGEDIT is not open, or if any other key is selected, I
cannot connect via OSQL. The SQL Service Manager applet also exhibits the
same behavior (i.e., it can't connect to MSDE unless REGEDIT is open to the
Microsoft SQL Server key).
Other background info:
MSDE is installed via:
-setup.exe INSTANCENAME="CTSDB" SAPWD="ASecurePassword" SECURITYMODE=SQL
REBOOT=ReallySuppres
s REBOOTPROMPT=Suppres
s /Li*v c:\msdelog.txt
-MSDE installs without error, and the service can be stopped and started
without error
-I've uninstalled and reinstalled MSDE multiple times (deleting leftover reg
keys and files) to no avail
-This problem does not happen on most of my client workstations
| |
| Joe Yong 2005-05-20, 8:24 pm |
| Did you enable network access? It is turned off by default in MSDE 2000 SP3a
(was on by default prior to that).
joe.
"GregM" <GregM@discussions.microsoft.com> wrote in message
news:2B96699D-DA4B-482A-9F9F- 7BF6A3EFBEE9@microso
ft.com...
> I'm baffled at the following MSDE connectivity problem:
>
> After installing MSDE 2000 SP3a (and hotfix 8.00.0818-enu) on a
> workstation
> (XP, SP2), I get the following error when trying to connect to the
> database
> using OSQL:
>
> [DBMSLPCN]SQL Server does not exist or access denied.
> & #91;DBMSLPCN]Connect
ionOpen (Connect()).
>
> However, if I open REGEDIT to the
> HKEY_LOCAL_MACHINE\S
OFTWARE\Microsoft\Mi
crosoft SQL Server key, I can
> connect
> without issue. If REGEDIT is not open, or if any other key is selected, I
> cannot connect via OSQL. The SQL Service Manager applet also exhibits the
> same behavior (i.e., it can't connect to MSDE unless REGEDIT is open to
> the
> Microsoft SQL Server key).
>
> Other background info:
> MSDE is installed via:
> -setup.exe INSTANCENAME="CTSDB" SAPWD="ASecurePassword" SECURITYMODE=SQL
> REBOOT=ReallySuppres
s REBOOTPROMPT=Suppres
s /Li*v c:\msdelog.txt
> -MSDE installs without error, and the service can be stopped and started
> without error
> -I've uninstalled and reinstalled MSDE multiple times (deleting leftover
> reg
> keys and files) to no avail
> -This problem does not happen on most of my client workstations
>
| |
|
| I failed to mention that in the first post . . . network access is disabled
(intentionally). The testing (and issue) is experienced when trying to
connect to MSDE from the machine on which the database is installed.
Greg
"Joe Yong" wrote:
> Did you enable network access? It is turned off by default in MSDE 2000 SP3a
> (was on by default prior to that).
>
>
> joe.
>
> "GregM" <GregM@discussions.microsoft.com> wrote in message
> news:2B96699D-DA4B-482A-9F9F- 7BF6A3EFBEE9@microso
ft.com...
>
>
>
| |
| Allcomp 2005-05-24, 3:23 am |
| Hello,
Have you tried without the Win XP SP2 Firewall?
If it is OK without it, you can try to configure it correctly after...
Sometimes, you can have a problem even locally if you use the firewall...
Marc Allard
Allcomp
GregM wrote:[color=darkred
]
> I failed to mention that in the first post . . . network access is disabled
> (intentionally). The testing (and issue) is experienced when trying to
> connect to MSDE from the machine on which the database is installed.
>
> Greg
>
> "Joe Yong" wrote:
>
>
| |
|
| I've got the XP SP2 Firewall service turned off.
After more digging, it appears that the "shared memory" protocol isn't
functioning correctly. When I manually set the
HKEY_LOCAL_MACHINE\S
OFTWARE\Microsoft\Mi
crosoft SQL
Server\CTSDB\MSSQLSe
rver\SuperSocketNetL
ib -- ProtocolList reg key to "tcp",
OSQL (and my other apps) started working. The ProtocolList key was blank by
default, which is as designed, I think, and how it should be configured. Not
sure why the 'shared memory' side isn't working correctly.
"Allcomp" wrote:
> Hello,
>
> Have you tried without the Win XP SP2 Firewall?
> If it is OK without it, you can try to configure it correctly after...
> Sometimes, you can have a problem even locally if you use the firewall...
>
> Marc Allard
> Allcomp
>
> GregM wrote:
>
| |
| Kevin Beyer via SQLMonster.com 2005-05-25, 11:23 am |
| Excellent post, Greg! I have been beating my head against the wall for the
past day trying to figure this out. Your solution worked for me.
Thank you so much.
| |
|
| Kevin - I'm glad that the workaround helped! I've got a support request open
with MS on this, and will post the results of that whenever it becomes
available.
Greg
|
|
|
|
|