MSDE and Access Project Issue

I installed MSDE SP3a on my XP Pro laptop using the following options:
SAPWD=abc456
instancename=MSDE01
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
DATADIR="C:\MSDE"
TARGETDIR="C:\MSDE"
I went to services and started MSSQL$MSDE01 and SQLAgent$MSDE01.
I opened up MSACCESS 2003 and created a new project with new data. The SQL Server Database Wizard popped up and I entered (local)MSDE01 for the SQL server and clicked the Use Trusted Connection.
After several seconds, I receive an error message:
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or access denied.
I can connect to this instance of MSDE using ASP.NET and the Server Explorer. So I'm pretty sure that I have a good install of MSDE.
Does anyone have a clue as to what I am doing wrong when I try to connect via Access?
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Hi,
Try (local)\MSDE01 instead.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:uv46MJeIEHA.3968@.TK2MSFTNGP12.phx.gbl...
> I installed MSDE SP3a on my XP Pro laptop using the following options:
> SAPWD=abc456
> instancename=MSDE01
> DISABLENETWORKPROTOCOLS=0
> SECURITYMODE=SQL
> DATADIR="C:\MSDE"
> TARGETDIR="C:\MSDE"
> I went to services and started MSSQL$MSDE01 and SQLAgent$MSDE01.
> I opened up MSACCESS 2003 and created a new project with new data. The
SQL Server Database Wizard popped up and I entered (local)MSDE01 for the SQL
server and clicked the Use Trusted Connection.
> After several seconds, I receive an error message:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen(Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or
access denied.
> I can connect to this instance of MSDE using ASP.NET and the Server
Explorer. So I'm pretty sure that I have a good install of MSDE.
> Does anyone have a clue as to what I am doing wrong when I try to connect
via Access?
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
|||or .\MSDE01
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:uv46MJeIEHA.3968@.TK2MSFTNGP12.phx.gbl...
> I installed MSDE SP3a on my XP Pro laptop using the following options:
> SAPWD=abc456
> instancename=MSDE01
> DISABLENETWORKPROTOCOLS=0
> SECURITYMODE=SQL
> DATADIR="C:\MSDE"
> TARGETDIR="C:\MSDE"
> I went to services and started MSSQL$MSDE01 and SQLAgent$MSDE01.
> I opened up MSACCESS 2003 and created a new project with new data. The
SQL Server Database Wizard popped up and I entered (local)MSDE01 for the SQL
server and clicked the Use Trusted Connection.
> After several seconds, I receive an error message:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen(Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or
access denied.
> I can connect to this instance of MSDE using ASP.NET and the Server
Explorer. So I'm pretty sure that I have a good install of MSDE.
> Does anyone have a clue as to what I am doing wrong when I try to connect
via Access?
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.

MSDE 2000a installation failure on XP Pro

Hi,
Everyone know why MSDE 2000a is refusing to load on a XP Pro wiht Office SBS installed on it. It seems to have MSDE already but the default instance isn't accessible so I tried to install under another instance name. I have set the SA password.
File and print sharing is installed and running (I think). I'm able to share out folders.
Any suggestions?
Jim
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
hi Jim,
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> ha scritto nel messaggio
news:eIKtRH8eEHA.3028@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Everyone know why MSDE 2000a is refusing to load on a XP Pro wiht Office
SBS installed on it. It seems to have MSDE already but the default instance
isn't accessible so I tried to install under another instance name. I have
set the SA password.
> File and print sharing is installed and running (I think). I'm able to
share out folders.
I'm not aware of such limitation... but, anyway, please add the /L*v
"c:\..\Log.txt" command line parameter in order to
inspect the resulting log file..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

msde 2000 sp3 install problem on win 2000

server. I am building an installshield package. During this process I must install to win 2000, xp pro etc, at home on my 2000 server I had hell of a time installing the msde. I have tried the msde 2000 sp3 patch as well. The installation rolls back after it is almost done. the log won't tell me anything meaningful. Is there any secret to msde on 2000 severs? I one time managed to install the server after succesfullu monkeying with the security profiles on the server, now it is uninstalled but despite the profile set correctlty I can't install? I need some help FAST!!!
The xp works like a charm.
I have attached the log...so if someone is an expert maybe can shed the ligh for me...Log file is not attached.|||msde setup has a bug - it needs upper case machine id for the network (I wonder if there is a workaround since changing my machine name is not that trivial - I am a cable broadband user.)|||Where did you find out about the upper case machine name - do you have a link ?|||Originally posted by rnealejr
Where did you find out about the upper case machine name - do you have a link ?
? if(document.domain.indexOf('.microsoft.com') > 0) document.domain = 'support.microsoft.com';

Home Search FAQs Downloads Newsgroups Customer Service

Microsoft Knowledge Base Article - 285100

Comments?
Provide us with feedback on this article

Support Centers
Small Business Server
SQL Server

Other Support Options
Contact Microsoft
Phone Numbers, Support Options and Pricing, Online Help, and more.

Customer Service
For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.

Newsgroups
Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.


Page Options
Send
Print



FIX: Installation Fails When Windows Computer Name Is Mixed or Lowercase
View products that this article applies to.
This article was previously published under Q285100
BUG #: 351711(SQL2000)
SYMPTOMS
Connection attempts over the shared memory network library fail on a server where GetComputerName returns a lower or mixed case server name.

When the shared memory connection attempt fails the SQL Server 2000 network library attempts to connect over an alternate protocol.

When you install any edition of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) on a computer whose name is all lowercase or mixed case, Setup may fail, and you receive one of the following messages:

For MSDE 2000:

Setup failed to configure the server. Refer to the server error logs and setup error logs for more information.
For SQL Server 2000:

Setup failed to configure the server. Refer to the server error logs and sqlstp.log for more information.
CAUSE
GetComputerName is used to obtain the local computer name. The client network library component (DBMSLPCn.dll) converts the name to all upper case. The server network library component (SSMSLPCn.dll) leaves the name as returned.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
File name Platform
-------

SSMSLPCn323 Intel

The following file is available for download from the Microsoft Download Center:

SSMSLPCn323.exe

Release Date: JAN-22-2001

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How To Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

The SSMSLPCn323.exe file contains the following files:

File name Size
EULA.txt 2 KB
Readme.txt 1 KB
SSmsLPCn.dll 29 KB
SSmsLPCn.pdb 73 KB
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.

WORKAROUND
To work around this problem, change the computer name to all uppercase characters.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
The failure is prohibitive to a SQL Server 2000 setup. A SQL Server 2000 setup prevents external connections by only allowing the shared network library connections.

If a shared memory connection can not be established, the setup fails when it attempts to configure the SQL Server server.

For SQL Server 2000:

The Sqlstp.log file contains an error message similar to:

2:44:57 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINNT\sqlstp.log" -dbdebug -I MSSQLSERVER -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 262404 -U sa -P
Starting Service ...
SQL_Latin1_General_CP1_CI_AS -m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=MyServer;UID=sa;PWD=;database=maste r [Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
In the same Sqlstp.log file you can verify the naming failure by locating the following at the top of the log file:
12:30:08 Name = MYSERVER, Type = 0x1
12:30:08 ComputerName: MyServer

For MSDE 2000:

Run the following command so the installation does not roll back upon failure:
setup.exe /DISABLEROLLBACK=1 /L*v C:\temp\msdesetup.log

You must run this code so that the Cnfgsvr.out file can be collected. Using the /L*v switch enables verbose logging for MSDE 2000 Setup.

After the MSDE 2000 installation fails, when you review the contents of the Cnfgsvr.out file, you see an error message similar to the following:

Starting Service ...

SQL_Latin1_General_CP1_CI_AS

-m -Q -T4022 -T3659

Connecting to Server ...

driver={sql server};server=MyServer;UID=sa;PWD=;database=maste r

[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.

[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
The naming failure can be located from the server parameter. The Msdesetup.log file has an entry similar to the following:
ComputerName =MyServer

The information in this article applies to:
Microsoft SQL Server 2000 (all editions)
Microsoft SQL Server 2000 Desktop Engine (MSDE)
Last Reviewed: 11/3/2003 (4.0)
Keywords: kbBug kbfix kbQFE KB285100 kbAudDeveloper






Contact Us

? 2003 Microsoft Corporation. All rights reserved. Terms of use Security & Privacy Accessibility
function thisLoad(){ setcookieval("SITE","GN"); gsfxUpLevel(); g_reSupportedHostnames = new RegExp(".msn.com$|.passport.com$|.xbox.com$|.microsoft.com $|.microsoft.cz$|.msbpn.com$|.microsoft.co.*", "i"); ForeignLink_Hookup(true);LogHit('http://c.microsoft.com/trans_pixel.asp?TYPE=SSPV&SOURCE=SUPPORT&URI=/GN/EN-US/kb_en-us_285100&GUID=1F4FC18C-F71E-47fb-8FC9-612F8EE59C61&R='); } function thisUnload(){ ; }|||The fix is included in the article - do you download the fix ?|||Originally posted by rnealejr
The fix is included in the article - do you download the fix ?
Yes.
The problem is that I do not know how to update the CAB file and I can't even find reference to SSmsLPCn.pdb - I found the dll but I have not replace it yet in the CAB.
I found it incomprehansible that there is this bug and MSFT can NOT provide a decent fix only this weird one that you need to manually update dll's and fix THEIR setup. I have yet to find a reference to fix an existing setup distributable.|||If you follow the instructions in the readme.txt, you should be fine.

MSDE 2000 Release A won't talk

MSDE 2000 Release A installed under windows 2000 pro will not
communicate with SQL Server Manager nor MS Access on peer computer.
Can someone help?
Have set DISABLENETWORKPROTOCOLS=0 at install time.
Install log shows installation successful..
Control Panel> Admin Tools> Services section shows SQL server instance
running.
Disabling firewall has no effect.
SQL Server Manager (icon at bottom right in task tray - this
starts/stops Server instances), on same computer as SQL Server
instance, shows only instance "H" which is the same as the computer
name. (This instance was uninstalled before new instance was
installed.) Typing new instance name ("H\ABC" and variations) into
top combo box produces error messages such as "wrong format for name",
"Network path not found" "RPC service not running". What is the
correct computer/name format? Key problem is clearly that Service
Manager can't communicate with this local MSDE instance.
All Windows 2000 updates from MS web site have been installed.
Objective is to operate MS Access on computer X (also running Win 2000
Pro) with computer H as a peer that hosts MSDE.
Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system?
Have you installed SP3a?
Steve
<noname@.noname.com> wrote in message
news:40d55341.11850570@.nntp.flfrd.phub.net.cable.r ogers.com...
> MSDE 2000 Release A installed under windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format? Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system?
|||Hi Steve,
MSDE 2000A already contains SQL Server SP3a updates.
Mark
Ottawa, Canada
On Tue, 22 Jun 2004 15:25:07 -0400, "Steve Thompson"
<stevethompson@.nomail.please> wrote:

>Have you installed SP3a?
>Steve

MSDE 2000 Release A won't talk

MSDE 2000 Release A installed under Windows 2000 pro will not
communicate with SQL Server Manager nor MS Access on peer computer.
Can someone help?
Have set DISABLENETWORKPROTOCOLS=0 at install time.
Install log shows installation successful..
Control Panel> Admin Tools> Services section shows SQL server instance
running.
Disabling firewall has no effect.
SQL Server Manager (icon at bottom right in task tray - this
starts/stops Server instances), on same computer as SQL Server
instance, shows only instance "H" which is the same as the computer
name. (This instance was uninstalled before new instance was
installed.) Typing new instance name ("H\ABC" and variations) into
top combo box produces error messages such as "wrong format for name",
"Network path not found" "RPC service not running". What is the
correct computer/name format' Key problem is clearly that Service
Manager can't communicate with this local MSDE instance.
All Windows 2000 updates from MS web site have been installed.
Objective is to operate MS Access on computer X (also running Win 2000
Pro) with computer H as a peer that hosts MSDE.
Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system'Have you installed SP3a?
Steve
<noname@.noname.com> wrote in message
news:40d55341.11850570@.nntp.flfrd.phub.net.cable.rogers.com...
> MSDE 2000 Release A installed under Windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format' Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system'|||Hi Steve,
MSDE 2000A already contains SQL Server SP3a updates.
Mark
Ottawa, Canada
On Tue, 22 Jun 2004 15:25:07 -0400, "Steve Thompson"
<stevethompson@.nomail.please> wrote:

>Have you installed SP3a?
>Steve

MSDE 2000 Release A wont talk

MSDE 2000 Release A installed under windows 2000 pro will not
communicate with SQL Server Manager nor MS Access on peer computer.
Can someone help?

Have set DISABLENETWORKPROTOCOLS=0 at install time.

Install log shows installation successful..

Control Panel> Admin Tools> Services section shows SQL server instance
running.

Disabling firewall has no effect.

SQL Server Manager (icon at bottom right in task tray - this
starts/stops Server instances), on same computer as SQL Server
instance, shows only instance "H" which is the same as the computer
name. (This instance was uninstalled before new instance was
installed.) Typing new instance name ("H\ABC" and variations) into
top combo box produces error messages such as "wrong format for name",
"Network path not found" "RPC service not running". What is the
correct computer/name format?? Key problem is clearly that Service
Manager can't communicate with this local MSDE instance.

All Windows 2000 updates from MS web site have been installed.

Objective is to operate MS Access on computer X (also running Win 2000
Pro) with computer H as a peer that hosts MSDE.

Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
--
Mark Ferguson<noname@.noname.com> wrote in message
news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
> MSDE 2000 Release A installed under windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format?? Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
> --
> Mark Ferguson

I must admit that I don't know the difference between MSDE Release A and
MSDE SP3a. There is no clear information on the MS site (or at least I
couldn't find it), but the download sizes are different, so the obvious
conclusion is that they are different versions. If this assumption is
correct, then you might be seeing this issue:

http://support.microsoft.com/defaul...010&Product=sql

However, I could be wrong, so perhaps you can check some more things. Can
you actually connect to the instance on H using a local osql.exe command
also on H? If you're logged on to Windows as an administrator, then this
should be enough:

osql -S H\ABC -E

If that works, then presumably the problem is the Service Manager itself
(possibly as described in the article above). If you can connect, you can
then check the version with this query:

1> select @.@.version
2> go

If you don't see version 8.00.760, then you don't have SP3a, so I would
completely remove MSDE and then install MSDE SP3a. See "Remove all known
instances of SQL Server" in this article:

http://support.microsoft.com/defaul...991&Product=sql

If you cannot connect with osql.exe, then what error message do you get? In
the final analysis, however, I would suggest that Server Manager is a small,
unimportant component which probably is not worth worrying about. As long as
MSDE is running and you can connect from client applications with no
problems, then I would not spend too much time trying to make it work.

Regarding connecting from a different PC (with Access or any other tool),
there are a number of possible connection issues:

http://support.microsoft.com/defaul...306&Product=sql

I guess when you say "peer" you mean that the PCs are in a workgroup, not a
domain. If this is the case, then trusted connections can be awkward - the
article above has a link to another KB article which describes a possible
workaround. Mixed security using SQL logins should work fine, but is not
generally recommended unless there is no other alternative.

Simon|||Hi

You may get more help in the microsoft.public.sqlserver.msde newsgroup.

John
<noname@.noname.com> wrote in message
news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
> MSDE 2000 Release A installed under windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format?? Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
> --
> Mark Ferguson|||"Simon Hayes" <sql@.hayes.ch> wrote in message
news:40d5ade5$1_2@.news.bluewin.ch...
|
| <noname@.noname.com> wrote in message
| news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
| > MSDE 2000 Release A installed under windows 2000 pro will not
| > communicate with SQL Server Manager nor MS Access on peer computer.
| > Can someone help?
| >
| > Have set DISABLENETWORKPROTOCOLS=0 at install time.
| >
| > Install log shows installation successful..
| >
| > Control Panel> Admin Tools> Services section shows SQL server instance
| > running.
| >
| > Disabling firewall has no effect.
| >
| > SQL Server Manager (icon at bottom right in task tray - this
| > starts/stops Server instances), on same computer as SQL Server
| > instance, shows only instance "H" which is the same as the computer
| > name. (This instance was uninstalled before new instance was
| > installed.) Typing new instance name ("H\ABC" and variations) into
| > top combo box produces error messages such as "wrong format for name",
| > "Network path not found" "RPC service not running". What is the
| > correct computer/name format?? Key problem is clearly that Service
| > Manager can't communicate with this local MSDE instance.
| >
| > All Windows 2000 updates from MS web site have been installed.
| >
| > Objective is to operate MS Access on computer X (also running Win 2000
| > Pro) with computer H as a peer that hosts MSDE.
| >
| > Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
| > --
| > Mark Ferguson
|
| I must admit that I don't know the difference between MSDE Release A and
| MSDE SP3a. There is no clear information on the MS site (or at least I
| couldn't find it), but the download sizes are different, so the obvious
| conclusion is that they are different versions. If this assumption is
| correct, then you might be seeing this issue:
|
| http://support.microsoft.com/defaul...010&Product=sql
|
| However, I could be wrong, so perhaps you can check some more things. Can
| you actually connect to the instance on H using a local osql.exe command
| also on H? If you're logged on to Windows as an administrator, then this
| should be enough:
|
| osql -S H\ABC -E
|
| If that works, then presumably the problem is the Service Manager itself
| (possibly as described in the article above). If you can connect, you can
| then check the version with this query:
|
| 1> select @.@.version
| 2> go
|
| If you don't see version 8.00.760, then you don't have SP3a, so I would
| completely remove MSDE and then install MSDE SP3a. See "Remove all known
| instances of SQL Server" in this article:
|
| http://support.microsoft.com/defaul...991&Product=sql
|
| If you cannot connect with osql.exe, then what error message do you get? In
| the final analysis, however, I would suggest that Server Manager is a small,
| unimportant component which probably is not worth worrying about. As long as
| MSDE is running and you can connect from client applications with no
| problems, then I would not spend too much time trying to make it work.
|
| Regarding connecting from a different PC (with Access or any other tool),
| there are a number of possible connection issues:
|
| http://support.microsoft.com/defaul...306&Product=sql
|
| I guess when you say "peer" you mean that the PCs are in a workgroup, not a
| domain. If this is the case, then trusted connections can be awkward - the
| article above has a link to another KB article which describes a possible
| workaround. Mixed security using SQL logins should work fine, but is not
| generally recommended unless there is no other alternative.
|
| Simon
|
|

MSDE 2000 Release A is a developer version (SDK) of Microsoft SQL Server 2000
Desktop Engine SP3a. SELECT @.@.VERSION returns the same version info for both.

This brief description of Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
Release A is quoted from the download page -
<
MSDE 2000 Release A is functionally equivalent to SQL Server 2000 Desktop
Engine SP3a except for the following:

New licensing agreement

Removal of the merge modules that can be used to embed MSDE 2000 Release A
with applications

New ReadMeMSDE2000A.htm that contains information specific to this release.

This new version of MSDE contains all the fixes that are included with SQL
Server 2000 SP3a version of MSDE.

http://www.microsoft.com/downloads/...&DisplayLang=en
Additional information can be found in the Microsoft SQL Server 2000 Desktop
Engine
(MSDE 2000) Release A ReadMe

http://download.microsoft.com/downl...meMSDE2000A.htm

Additions to the SQL Server 2000 Desktop Engine (MSDE) Release A
ReadmeMSDE2000A.htm File
http://support.microsoft.com/?kbid=829925

Dan|||<noname@.noname.com> wrote in message
news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
| MSDE 2000 Release A installed under windows 2000 pro will not
| communicate with SQL Server Manager nor MS Access on peer computer.
| Can someone help?
|
| Have set DISABLENETWORKPROTOCOLS=0 at install time.
|
| Install log shows installation successful..
|
| Control Panel> Admin Tools> Services section shows SQL server instance
| running.
|
| Disabling firewall has no effect.
|
| SQL Server Manager (icon at bottom right in task tray - this
| starts/stops Server instances), on same computer as SQL Server
| instance, shows only instance "H" which is the same as the computer
| name. (This instance was uninstalled before new instance was
| installed.) Typing new instance name ("H\ABC" and variations) into
| top combo box produces error messages such as "wrong format for name",
| "Network path not found" "RPC service not running". What is the
| correct computer/name format?? Key problem is clearly that Service
| Manager can't communicate with this local MSDE instance.
|
| All Windows 2000 updates from MS web site have been installed.
|
| Objective is to operate MS Access on computer X (also running Win 2000
| Pro) with computer H as a peer that hosts MSDE.
|
| Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
| --
| Mark Ferguson

Hi Mark,

There is known bug when reinstalling with same instance name.
Follow the instructions for editing the registry keys given in
the article at:
http://support.microsoft.com/defaul...kb;en-us;823467

If that fails then you will have to uninstall MSDE 2000 Release A
and follow the instructions for editing the registry keys given in
the article at:
http://support.microsoft.com/defaul...kb;en-us;320873
Then reinstall MSDE 2000 Release A

Hope this helps.

Dan|||Thanks John, but I dont see a newsgroup named
microsoft.public.sqlserver.msde. I just checked for new groups and
that one doesn't show up there either. Not sure where i might find
this group.

On Sun, 20 Jun 2004 16:07:34 GMT, "John Bell"
<jbellnewsposts@.hotmail.com> wrote:

>Hi
>You may get more help in the microsoft.public.sqlserver.msde newsgroup.
>John
><noname@.noname.com> wrote in message
>news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
>> MSDE 2000 Release A installed under windows 2000 pro will not
>> communicate with SQL Server Manager nor MS Access on peer computer.
>> Can someone help?
>>
>> Have set DISABLENETWORKPROTOCOLS=0 at install time.
>>
>> Install log shows installation successful..
>>
>> Control Panel> Admin Tools> Services section shows SQL server instance
>> running.
>>
>> Disabling firewall has no effect.
>>
>> SQL Server Manager (icon at bottom right in task tray - this
>> starts/stops Server instances), on same computer as SQL Server
>> instance, shows only instance "H" which is the same as the computer
>> name. (This instance was uninstalled before new instance was
>> installed.) Typing new instance name ("H\ABC" and variations) into
>> top combo box produces error messages such as "wrong format for name",
>> "Network path not found" "RPC service not running". What is the
>> correct computer/name format?? Key problem is clearly that Service
>> Manager can't communicate with this local MSDE instance.
>>
>> All Windows 2000 updates from MS web site have been installed.
>>
>> Objective is to operate MS Access on computer X (also running Win 2000
>> Pro) with computer H as a peer that hosts MSDE.
>>
>> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
>> --
>> Mark Ferguson|||Hi

Try the news.microsoft.com news server or
http://groups.google.com/groups?hl=...sqlserver.msde

John

<Mark_Ferguson@.noname.com> wrote in message
news:40d736bf.12602391@.nntp.flfrd.phub.net.cable.r ogers.com...
> Thanks John, but I dont see a newsgroup named
> microsoft.public.sqlserver.msde. I just checked for new groups and
> that one doesn't show up there either. Not sure where i might find
> this group.
> On Sun, 20 Jun 2004 16:07:34 GMT, "John Bell"
> <jbellnewsposts@.hotmail.com> wrote:
> >Hi
> >You may get more help in the microsoft.public.sqlserver.msde newsgroup.
> >John
> ><noname@.noname.com> wrote in message
> >news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
> >> MSDE 2000 Release A installed under windows 2000 pro will not
> >> communicate with SQL Server Manager nor MS Access on peer computer.
> >> Can someone help?
> >>
> >> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> >>
> >> Install log shows installation successful..
> >>
> >> Control Panel> Admin Tools> Services section shows SQL server instance
> >> running.
> >>
> >> Disabling firewall has no effect.
> >>
> >> SQL Server Manager (icon at bottom right in task tray - this
> >> starts/stops Server instances), on same computer as SQL Server
> >> instance, shows only instance "H" which is the same as the computer
> >> name. (This instance was uninstalled before new instance was
> >> installed.) Typing new instance name ("H\ABC" and variations) into
> >> top combo box produces error messages such as "wrong format for name",
> >> "Network path not found" "RPC service not running". What is the
> >> correct computer/name format?? Key problem is clearly that Service
> >> Manager can't communicate with this local MSDE instance.
> >>
> >> All Windows 2000 updates from MS web site have been installed.
> >>
> >> Objective is to operate MS Access on computer X (also running Win 2000
> >> Pro) with computer H as a peer that hosts MSDE.
> >>
> >> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
> >> --
> >> Mark Ferguson|||>I must admit that I don't know the difference between MSDE Release A and
>MSDE SP3a. There is no clear information on the MS site (or at least I
>couldn't find it), but the download sizes are different, so the obvious
>conclusion is that they are different versions. If this assumption is
>correct, then you might be seeing this issue:
>http://support.microsoft.com/defaul...010&Product=sql
This article applies to MSDE Service pack . I have installed MSDE
2000A which includes Service Pack 3. The symptoms don't and conditions
don't apply, nor do the workaround instructions make sense.
>However, I could be wrong, so perhaps you can check some more things. Can
>you actually connect to the instance on H using a local osql.exe command
>also on H? If you're logged on to Windows as an administrator, then this
>should be enough:
>osql -S H\ABC -E
This works. But the SQL Server *is* running - we knew that.

>If that works, then presumably the problem is the Service Manager itself
>(possibly as described in the article above). If you can connect, you can
>then check the version with this query:
>1> select @.@.version
>2> go
Result is:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copy
right (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT
5.0 (Build 2195: Service Pack 4)

>If you don't see version 8.00.760, then you don't have SP3a, so I would
>completely remove MSDE and then install MSDE SP3a. See "Remove all known
>instances of SQL Server" in this article:
>http://support.microsoft.com/defaul...991&Product=sql

Thank you... This may be very useful indeed.
>If you cannot connect with osql.exe, then what error message do you get? In
>the final analysis, however, I would suggest that Server Manager is a small,
>unimportant component which probably is not worth worrying about. As long as
>MSDE is running and you can connect from client applications with no
>problems, then I would not spend too much time trying to make it work.
>Regarding connecting from a different PC (with Access or any other tool),
>there are a number of possible connection issues:
>http://support.microsoft.com/defaul...306&Product=sql
>I guess when you say "peer" you mean that the PCs are in a workgroup, not a
>domain. If this is the case, then trusted connections can be awkward - the
>article above has a link to another KB article which describes a possible
>workaround. Mixed security using SQL logins should work fine, but is not
>generally recommended unless there is no other alternative.

You are correct, the two computers are not in a domain and so there is
no user authentication provided by a domain server. Thanks for the
link I will look it up.

The Server Manager is only important in that its a good first
indication that everything is working at the local computer - an
encouraging first sign, insofar as the client computer cannot connect
to the server.
>Simon
>
I am also working on the problem of fixing ports used by the SQL
Server. The instance now installed is named and so uses dynamic ports
rather than the fixed 1433 and 1434 ports. The question is: what does
the SQL Server Manager use?|||I think you are correct. I need to uninstall MSDE2000A and then fix up
the registry or re-install windows 2000. I have already uninstalled
the old default version that came with MS office. I have also
installed the MSDE2000A version several times.

I have never checked the MDAC version (don't know how), but that may
also be a problem.

I need to try these and then request more help.

Many thanks.
Mark.

On Mon, 21 Jun 2004 05:22:56 -0400, "Daniel A. Thomas"
<dathomas@.--spam--istar.ca> wrote:

>Hi Mark,
>There is known bug when reinstalling with same instance name.
>Follow the instructions for editing the registry keys given in
>the article at:
>http://support.microsoft.com/defaul...kb;en-us;823467
>If that fails then you will have to uninstall MSDE 2000 Release A
>and follow the instructions for editing the registry keys given in
>the article at:
>http://support.microsoft.com/defaul...kb;en-us;320873
>Then reinstall MSDE 2000 Release A
>Hope this helps.
>Dan|||OK, John. The google web page is the same as the MS Discussion forum
for SQL Server. I posted a similar article there, but no help came
there.

Mark.

On Mon, 21 Jun 2004 19:56:20 GMT, "John Bell"
<jbellnewsposts@.hotmail.com> wrote:

>Hi
>Try the news.microsoft.com news server or
>http://groups.google.com/groups?hl=...sqlserver.msde
>John|||I'm grateful for the help from you all, but the one real symptom of
the problem with the Service Manager is its error message:
"The format of the computer name is inavlid."

This is the response to asking it to find the instance ABC on the
computer named "H" - (H\ABC). Recall that running osql.exe against the
name H\ABC works fine.

Mark.

MSDE / SQL Server 2005 express

Is it possible to install both MSDE and SQL Server 2005 express on the same
XP Pro machine?
Thanks
hi,
Bamboozled wrote:
> Is it possible to install both MSDE and SQL Server 2005 express on
> the same XP Pro machine?
>
yes it is...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE & Business Contact Manager

I have a computer (XP PRO) that I attempted to install MSDE on for a database
application we use, not realizing that the Outlook Business Contact Manager
has some sort of SQL server already installed. The installation failed. In
looking through the services I noticed the MicrosoftBCM instance and realized
that must be my problem.
I attempted to connect to this instance via odbc and not knowing the
connection method was unable to connect (server does not exist or access
denied...) but the computer name and (local) were listed in the SQL servers
list.
So I installed a new instance of MSDE SP3. The installation went fine. The
new instance appeared in the services. I started the new service and
everything looked OK, but in trying to connect via ODBC, now SQL servers list
was empty and typing in the computer name did not help.
I restarted the computer and had the same symptoms. I started the SQL server
agent and none of the services were listed here either.
I looked in the reg key HKLM\SOFTWARE\MICROSOFT\Microsoft SQL
Server\InstalledInstances, and both were listed there.
The services were started and there were not any errors in the event log.
I uninstalled and re-installed MSDE, but that did not help either. So I
uninstalled the Business contact manager, since we were not yet using it and
the MSDE, then reinstalled MSDE and that is now working just fine with the
database application.
Does anyone have any idea what my problem may have been, if I am just unable
to have the Business contact manager and MSDE on the same comptuer or if
there is a fix or workaround for the problem I am experiencing?
Thanks so much,
ST
hi,
ST wrote:
> I have a computer (XP PRO) that I attempted to install MSDE on for a
> database application we use, not realizing that the Outlook Business
> Contact Manager has some sort of SQL server already installed. The
> installation failed. In looking through the services I noticed the
> MicrosoftBCM instance and realized that must be my problem.
> I attempted to connect to this instance via odbc and not knowing the
> connection method was unable to connect (server does not exist or
> access denied...) but the computer name and (local) were listed in
> the SQL servers list.
> So I installed a new instance of MSDE SP3. The installation went
> fine. The new instance appeared in the services. I started the new
> service and everything looked OK, but in trying to connect via ODBC,
> now SQL servers list was empty and typing in the computer name did
> not help.
> I restarted the computer and had the same symptoms. I started the SQL
> server agent and none of the services were listed here either.
> I looked in the reg key HKLM\SOFTWARE\MICROSOFT\Microsoft SQL
> Server\InstalledInstances, and both were listed there.
> The services were started and there were not any errors in the event
> log.
> I uninstalled and re-installed MSDE, but that did not help either. So
> I uninstalled the Business contact manager, since we were not yet
> using it and the MSDE, then reinstalled MSDE and that is now working
> just fine with the database application.
> Does anyone have any idea what my problem may have been, if I am just
> unable to have the Business contact manager and MSDE on the same
> comptuer or if there is a fix or workaround for the problem I am
> experiencing?
> Thanks so much,
> ST
I do not know about Outlook Business Contact Manager, but as regard the
empty SQL Server list in the SQL Server Service Manager, it probably depends
on network protocols setting for the installed MSDE instance, as reported in
http://support.microsoft.com/default...b;EN-US;814132
to modify this behaviour, run the Server Network Utility (svrnetcn.exe) and
enable the desired networkprotocol, if this is a viable solution..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE - Not associated with a trusted SQL Server connection

I have just installed MSDE on my PC running WinXP Pro. I set it up to use
mixed mode for security mode. However, when I try to log in to the database
using a user account I created I get the following error:
Login Failed for user 'username'. Reason: Not associated with a trusted SQL
server connection.
I am using DbaMgr 2k to view the database settings. I have provided all
admin level access to this user. However, I just cannot login using a
username. I have tried using the sa account to login and I get the same
error. I can only login using a Trusted NT Connection option. Any ideas what
I should try? When I searched it on the web, the only suggestion I can see
is to make sure the security mode is set to mixed mode, which seems to be
correct in this case.
Any help will be appreciated.
DeepaliHi
You don't say how you are trying to connect to the server? Try the following
from a command prompt
osql -S <Servername> -U <username> -P <Password>
John
"Deepali Garg" wrote:

> I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the databas
e
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted SQ
L
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas wh
at
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>
>|||SQL will not use the changes until it has been re-started... The error
seems to be saying it will only use trusted connections... perhaps you
simply need to re-start SQL...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
>I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the
> database
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted
> SQL
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas
> what
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>|||Wayne,
Thanks for your help. This is exactly what the problem was. As soon as I
restarted the SQL Server everything worked ok!
Deepali
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eW1ECQnGFHA.3628@.TK2MSFTNGP15.phx.gbl...
> SQL will not use the changes until it has been re-started... The error
> seems to be saying it will only use trusted connections... perhaps you
> simply need to re-start SQL...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
> news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
see[vbcol=seagreen]
be[vbcol=seagreen]
>

MSDE - Not associated with a trusted SQL Server connection

I have just installed MSDE on my PC running WinXP Pro. I set it up to use
mixed mode for security mode. However, when I try to log in to the database
using a user account I created I get the following error:
Login Failed for user 'username'. Reason: Not associated with a trusted SQL
server connection.
I am using DbaMgr 2k to view the database settings. I have provided all
admin level access to this user. However, I just cannot login using a
username. I have tried using the sa account to login and I get the same
error. I can only login using a Trusted NT Connection option. Any ideas what
I should try? When I searched it on the web, the only suggestion I can see
is to make sure the security mode is set to mixed mode, which seems to be
correct in this case.
Any help will be appreciated.
Deepali
Hi
You don't say how you are trying to connect to the server? Try the following
from a command prompt
osql -S <Servername> -U <username> -P <Password>
John
"Deepali Garg" wrote:

> I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the database
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted SQL
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas what
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>
>
|||SQL will not use the changes until it has been re-started... The error
seems to be saying it will only use trusted connections... perhaps you
simply need to re-start SQL...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
>I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the
> database
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted
> SQL
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas
> what
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>
|||Wayne,
Thanks for your help. This is exactly what the problem was. As soon as I
restarted the SQL Server everything worked ok!
Deepali
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eW1ECQnGFHA.3628@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> SQL will not use the changes until it has been re-started... The error
> seems to be saying it will only use trusted connections... perhaps you
> simply need to re-start SQL...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
> news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
see[vbcol=seagreen]
be
>

MSDE - Not associated with a trusted SQL Server connection

I have just installed MSDE on my PC running WinXP Pro. I set it up to use
mixed mode for security mode. However, when I try to log in to the database
using a user account I created I get the following error:
Login Failed for user 'username'. Reason: Not associated with a trusted SQL
server connection.
I am using DbaMgr 2k to view the database settings. I have provided all
admin level access to this user. However, I just cannot login using a
username. I have tried using the sa account to login and I get the same
error. I can only login using a Trusted NT Connection option. Any ideas what
I should try? When I searched it on the web, the only suggestion I can see
is to make sure the security mode is set to mixed mode, which seems to be
correct in this case.
Any help will be appreciated.
DeepaliHi
You don't say how you are trying to connect to the server? Try the following
from a command prompt
osql -S <Servername> -U <username> -P <Password>
John
"Deepali Garg" wrote:
> I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the database
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted SQL
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas what
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>
>|||SQL will not use the changes until it has been re-started... The error
seems to be saying it will only use trusted connections... perhaps you
simply need to re-start SQL...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
>I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the
> database
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted
> SQL
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas
> what
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>|||Wayne,
Thanks for your help. This is exactly what the problem was. As soon as I
restarted the SQL Server everything worked ok!
Deepali
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eW1ECQnGFHA.3628@.TK2MSFTNGP15.phx.gbl...
> SQL will not use the changes until it has been re-started... The error
> seems to be saying it will only use trusted connections... perhaps you
> simply need to re-start SQL...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
> news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
> >I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> > mixed mode for security mode. However, when I try to log in to the
> > database
> > using a user account I created I get the following error:
> >
> > Login Failed for user 'username'. Reason: Not associated with a trusted
> > SQL
> > server connection.
> >
> > I am using DbaMgr 2k to view the database settings. I have provided all
> > admin level access to this user. However, I just cannot login using a
> > username. I have tried using the sa account to login and I get the same
> > error. I can only login using a Trusted NT Connection option. Any ideas
> > what
> > I should try? When I searched it on the web, the only suggestion I can
see
> > is to make sure the security mode is set to mixed mode, which seems to
be
> > correct in this case.
> >
> > Any help will be appreciated.
> >
> > Deepali
> >
> >
>