all groups > sql server msde > april 2005 >
You're in the

sql server msde

group:

Trouble Getting VS.Net 2003 WalkThroughs MSDE Connection


Re: Trouble Getting VS.Net 2003 WalkThroughs MSDE Connection Jens Süßmeyer
4/26/2005 12:00:00 AM
sql server msde: WHat does

OSQL -L say at the commandline ?

Is the instance running and ready, does the service come up without any
error, do you have an named instance installed or just the standard instance
?


HTH, Jens Suessmeyer.

---
http://www.sqlserver2005.de
---

"Hugh O" <HughLD@newsgroup.nospam> schrieb im Newsbeitrag
news:OtF%23gsnSFHA.2132@TK2MSFTNGP14.phx.gbl...
[quoted text, click to view]

Trouble Getting VS.Net 2003 WalkThroughs MSDE Connection Hugh O
4/26/2005 12:15:15 PM
Have successfully installed VS.Net 2003 and had started to use the VS
Startup WalkThroughs for Creating a Web app. It asked for the server
information for a Pub database. I asked the MS Newsgroup for VS.Net Setup
and they directed me to install MSDE and they attached a ConfigSamples app
to create the sample databases. I executed a SQL2KDeskSP3 exe and then the
related Setup asking to create an instance for NetSDK, that they said was
required for the ConfigSamples.



The SQL2KDeskSP3 completed with no message. I rebooted and there is a MSDE
icon in the Systray. It does say Not connected though. When I executed
ConfigSamples it ended with the following window heading and message.



MS.Net Framework SDK QuickStart Tutorials

The samples configuration has completed with errors. Review log for more
details.

And it offers an option to launch.



The log had all pass condition codes except these copied statements

6:43:39 AM Monday, April 25, 2005: [Info] Could not detect NetSDK instance
of SQL Server. Databases will not be installed.

10:45:39 AM Tuesday, April 26, 2005: [Fail] Error executing SQL script.
(Script/ExitCode): InstPubs.sql/1

10:45:41 AM Tuesday, April 26, 2005: [Fail] Could not add QuickStart user to
database.: Pubs: Cannot open database requested in login 'Pubs'. Login
fails.

Login failed for user 'HUGHDANC-BIWWOS\HughBoss'.



I believe that first warning message was left over from an attempt
yesterday. I was able to launch the QuickStart and launch the MS.Net
Framework SDK Tutorials. But when I tried to execute the VS.Net 2003
WalkThroughs and connect to the Pubs database I get the following error
message



Error enumerating data servers. Enumerator reports "Unspecified error"
(there was nothing listed in the server dropdown in the Connection Wizard)



What can I do to rectify this. All that I really want to do initially is to
be able to use the Walk Throughs for VS.Net and maybe try the QuickStarts
for MS.Net Framework SDK tutorials. I have an application I want to make
into a Web based software.



Thanks,

hugh

Re: Trouble Getting VS.Net 2003 WalkThroughs MSDE Connection Hugh O
4/27/2005 12:00:00 AM
Jens,



I checked MyComputer, Managed, and then Services. There were only two items
related to MSSQL. MSSQL$NETSDK was Started, Automatic, and Local System.
SQLAgent$NETSDK had a blank status, Manual, and Local System. I guess that
means there is only the instance NETSDK that I requested no default
instance.



I checked the Event Viewer and there were no ERROR messages only this
Warning that seems to happen when I boot my PC.



The description for Event ID ( 19011 ) in Source ( MSSQL$NETSDK ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event:
(SpnRegister) : Error 1355.



I checked C:\Program Files and there was a MS SQL Server folder with two
folders within it. One was named 80 and the other MSSQL$NETSDK. I looked
in the log files for NetSDK. The most recent log from this mornings boot of
my PC did not have any warning or error messages. I am pasting the log file
from yesterday at the end of this email. It does have both Error and
Warning messages.



If you direct me how I could undo this install, maybe I could reinstall this
MSDE either from the Setup or from the SQL2KDeskSP3 execute. I clearly
remember that the setup executed and then simply disappeared with no
completion status message. I probably should have looked for a log file at
that time. Instead I simply continued on with the execution of the
ConfigSamples execute file that they sent me to create the samples
databases. If I reinstalled MSDE, this time I could look at the Setup log
file, it might tell us what went wrong.



By the way, it does look like some of the sample databases have been
created. Northwind, GrocerToGo, and Portal. But not the Pubs database that
I need.



Unfortunately, I do not understand your first question.



WHat does
OSQL -L say at the commandline ?



Where would I have seen this, on what command line?



Thank you for any advice or direction you can offer. Yesterday's error log
follows.

Hugh



2005-04-26 10:37:42.15 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)

Dec 17 2002 14:22:05

Copyright (c) 1988-2003 Microsoft Corporation

Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)



2005-04-26 10:37:42.15 server Copyright (C) 1988-2002 Microsoft
Corporation.

2005-04-26 10:37:42.15 server All rights reserved.

2005-04-26 10:37:42.15 server Server Process ID is 2608.

2005-04-26 10:37:42.15 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.

2005-04-26 10:37:42.17 server SQL Server is starting at priority class
'normal'(1 CPU detected).

2005-04-26 10:37:42.51 server SQL Server configured for thread mode
processing.

2005-04-26 10:37:42.53 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.

2005-04-26 10:37:42.62 spid3 Warning ******************

2005-04-26 10:37:42.62 spid3 SQL Server started in single user mode.
Updates allowed to system catalogs.

2005-04-26 10:37:42.70 spid3 Starting up database 'master'.

2005-04-26 10:37:43.78 server Using 'SSNETLIB.DLL' version '8.0.766'.

2005-04-26 10:37:43.78 spid5 Starting up database 'model'.

2005-04-26 10:37:43.82 spid3 Server name is 'HUGHDANC-BIWWOS\NETSDK'.

2005-04-26 10:37:43.82 spid3 Skipping startup of clean database id 5

2005-04-26 10:37:43.82 spid3 Skipping startup of clean database id 6

2005-04-26 10:37:43.82 spid3 Starting up database 'msdb'.

2005-04-26 10:37:44.39 spid5 Clearing tempdb database.

2005-04-26 10:37:44.51 server SQL server listening on Shared Memory.

2005-04-26 10:37:44.51 server SQL Server is ready for client connections

2005-04-26 10:37:45.23 spid5 Starting up database 'tempdb'.

2005-04-26 10:37:45.32 spid3 Recovery complete.

2005-04-26 10:37:45.32 spid3 SQL global counter collection task is
created.

2005-04-26 10:37:45.34 spid3 Warning: override, autoexec procedures
skipped.

2005-04-26 10:37:56.85 spid51 Error: 15457, Severity: 0, State: 1

2005-04-26 10:37:56.85 spid51 Configuration option 'allow updates'
changed from 0 to 1. Run the RECONFIGURE statement to install..

2005-04-26 10:37:56.93 spid51 Error: 15457, Severity: 0, State: 1

2005-04-26 10:37:56.93 spid51 Configuration option 'allow updates'
changed from 1 to 0. Run the RECONFIGURE statement to install..

2005-04-26 10:37:57.35 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.













"Jens Süßmeyer" <Jens@Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:%2351vgpqSFHA.2304@tk2msftngp13.phx.gbl...
[quoted text, click to view]
Re: Trouble Getting VS.Net 2003 WalkThroughs MSDE Connection Hugh O
4/28/2005 7:51:49 AM
Jens,

Please excuse my ignorance. This is my first experience with a public
newsgroup. I was not trying to communicate outside of the newsgroup. When I
tried the ReplyGroup Option on my OutLook Express, the message made me
concerned that my response would be going to everyone in the group. I
thought that would have me bothering a lot of people unnecessarily.

Since your email I have read up a little on the OSQL utility.

From a DOS command prompt I typed

osql -L
the response was
Servers:
-- NONE --

When I typed osql -E the response was

[Shared Memory]SQL Servr does not exist or access denied.
[Shared Memory]ConnectionOpen <Connect<>>.

thanks,
hugh



"Jens Süßmeyer" <Jens@Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:%2351vgpqSFHA.2304@tk2msftngp13.phx.gbl...
[quoted text, click to view]

Re: Trouble Getting VS.Net 2003 WalkThroughs MSDE Connection Alexander Baumgart
4/29/2005 12:00:00 AM
[quoted text, click to view]

+AD4- Jens,
+AD4-
+AD4-
+AD4-
+AD4- I checked MyComputer, Managed, and then Services. There were only
+AD4- two items related to MSSQL. MSSQL+ACQ-NETSDK was Started,
Automatic,
+AD4- and Local System. SQLAgent+ACQ-NETSDK had a blank status, Manual,
+AD4- and Local System. I guess that means there is only the instance
+AD4- NETSDK that I requested no default instance.
+AD4-
+AD4-
+AD4-
+AD4- I checked the Event Viewer and there were no ERROR messages only
this
+AD4- Warning that seems to happen when I boot my PC.
+AD4-
+AD4-
+AD4-
+AD4- The description for Event ID ( 19011 ) in Source (
MSSQL+ACQ-NETSDK )
+AD4- cannot be found. The local computer may not have the necessary
+AD4- registry information or message DLL files to display messages
from a
+AD4- remote computer. You may be able to use the /AUXSOURCE+AD0- flag
to
+AD4- retrieve this description+ADs- see Help and Support for details.
The
+AD4- following information is part of the event: (SpnRegister) : Error
+AD4- 1355.
+AD4-
+AD4-
+AD4-
+AD4- I checked C:+AFw-Program Files and there was a MS SQL Server
folder
+AD4- with two folders within it. One was named 80 and the other
+AD4- MSSQL+ACQ-NETSDK. I looked in the log files for NetSDK. The most
+AD4- recent log from this mornings boot of my PC did not have any
warning
+AD4- or error messages. I am pasting the log file from yesterday at
the
+AD4- end of this email. It does have both Error and Warning messages.
+AD4-
+AD4-
+AD4-
+AD4- If you direct me how I could undo this install, maybe I could
+AD4- reinstall this MSDE either from the Setup or from the SQL2KDeskSP3
+AD4- execute. I clearly remember that the setup executed and then
simply
+AD4- disappeared with no completion status message. I probably should
+AD4- have looked for a log file at that time. Instead I simply
continued
+AD4- on with the execution of the ConfigSamples execute file that they
+AD4- sent me to create the samples databases. If I reinstalled MSDE,
this
+AD4- time I could look at the Setup log file, it might tell us what
went
+AD4- wrong.

Normaly u find MSDE under +ACI-ADD and Remove Software+ACI- under
System Controll. As i read from your post u installled a INSTANCE
(NETSDK).
Try to reinstall with +ACI-/L+ACo-v msde.log+ACI- and parse for Return
Value 3 Items.


Re: Trouble Getting VS.Net 2003 WalkThroughs MSDE Connection Jens Süßmeyer
5/5/2005 12:00:00 AM
Post private conversation via Mail:




-E will connect to your local defaut instance, if only a named one is
installed you have to type in something like -SServername/NameOfInstance,
the fact that no servers can be listed could result in the network settings,
does the SQL server listen to TCPIP ? Did you check that via the network
Config Tool of SQL Server ? There is also a checkbox in there which says
Hide Server, therefor you cannot see it in the LIST via the -L switch..
Another way should be to ceck wheter the service is listening on the
appopiate port with a portscanner like superscan.

We will find your problem ;-) !

Let me know if thi fixed it.

HTH, Jens Suessmeyer.


[quoted text, click to view]
AddThis Social Bookmark Button