Monday, March 26, 2012

MSDE Seems to Install - Service Manager Loads - No Connection

Hi,
I uninstalled MSDE 2000 prior to installing SQL Server 2000 Developer
Edition. I then found I could not use Developer Edition with Visual Basic
..net Standard Edition and tried to reinstall MSDE. The installation seems
to go fine but when the Service Manager loads is tells me "Not Connected -
\\" no servers are in the Server drop-down and no services are listed in
the Services drop-down. I am very new to all of this and would very much
appreciate any help/advice you could offer. I have since uninstalled
Developer Edition to no avail. I am running Windows XP Pro.
Regards
Barry-Jon
hi Barry-Jon,
Microsoft wrote:
> Hi,
> I uninstalled MSDE 2000 prior to installing SQL Server 2000 Developer
> Edition. I then found I could not use Developer Edition with Visual
> Basic .net Standard Edition and tried to reinstall MSDE. The
> installation seems to go fine but when the Service Manager loads is
> tells me "Not Connected - \\" no servers are in the Server drop-down
> and no services are listed in the Services drop-down. I am very new
> to all of this and would very much appreciate any help/advice you
> could offer. I have since uninstalled Developer Edition to no avail.
> I am running Windows XP Pro.
> Regards
> Barry-Jon
please have a look at
http://support.microsoft.com/default...b;EN-US;814132 ...
you can modify this behaviour enabling the desired/required network protocol
by running the Server Network Utility (svrnetcn.exe)...
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
|||"Microsoft" <barryjonoconnell_spam_no@.yahoo.co.uk> wrote in message
news:ucCLTwKEFHA.1188@.tk2msftngp13.phx.gbl...
> Hi,
> I uninstalled MSDE 2000 prior to installing SQL Server 2000 Developer
> Edition. I then found I could not use Developer Edition with Visual Basic
> .net Standard Edition and tried to reinstall MSDE. The installation seems
> to go fine but when the Service Manager loads is tells me "Not Connected -
> \\" no servers are in the Server drop-down and no services are listed in
> the Services drop-down. I am very new to all of this and would very much
> appreciate any help/advice you could offer. I have since uninstalled
> Developer Edition to no avail. I am running Windows XP Pro.
> Regards
> Barry-Jon
I posted this in the vb group as well, but just in case...
I'm not sure you're doing anything wrong, but perhaps the instructions we
use for classroom/lab installs of MSDE to work with Visual Studio .NET 2003
will be helpful:
<quote>
1. Before you begin, check the PC to ensure there are no remnants of prior
MSDE installation attempts hanging around. The place to check is: C:\Program
Files\Microsoft SQL Server. If you locate a folder named Microsoft SQL
Server, delete it and its contents!
2. Execute the file: SQL2KDeskSP3.exe(or whatever the file name for your
MSDE download is). This step will extract the contents of the file to a
designated folder. Make a note of the destination folder. You'll need it
later. This step does not install MSDE (although the dialogs seem to hint
that it does)!
4. Navigate to the folder you created in Step 2. In that folder, you will
find a subfolder named MSDE. In MSDE, you will find SETUP.EXE. Executing
SETUP.EXE will install MSDE.
5. To execute SETUP.EXE correctly, you must supply an instance name and a
system administrator password as part of the command: i.e. the command must
be:
SETUP.EXE INSTANCENAME="NetSDK" SAPWD="yourSAPassword"
where yourSAPassword is your actual system administrator password. This
password is needed only to install MDSE, not to use it. Access to MSDE is
controlled by normal "NT Security" which should allow users access based on
network logon and password. It is very important the the INSTANCENAME
parameter be NetSDK, as this name will enable you to generate the sample
databases automatically instead of having to run SQL scripts from the
command line.
6. Once installation is complete, you must reboot the PC before you will
see MSDE. After the reboot, you should see the MSDE icon in SysTray.
7. You now must execute the file: ConfigSamples.exe to configure sample
applications and MSDE system databases. This step will also create user
databases in the following location: C:\Program Files\Microsoft SQL
Server\MSSQL\Data.
</quote>
If you have trouble locating the ConfigSamples.exe, it's a small file
(56k) and I can send it to your email if needed.
Hope this helps.
Peter [MVP Visual Developer]
Jack of all trades, master of none.
|||Thanks Peter - that looks pretty much like what I did in the end. Saved
your post in case I ever forget :-)
"Peter van der Goes" <p_vandergoes@.toadstool.u> wrote in message
news:edfqWhQEFHA.3592@.TK2MSFTNGP15.phx.gbl...
> "Microsoft" <barryjonoconnell_spam_no@.yahoo.co.uk> wrote in message
> news:ucCLTwKEFHA.1188@.tk2msftngp13.phx.gbl...
> I posted this in the vb group as well, but just in case...
> I'm not sure you're doing anything wrong, but perhaps the instructions we
> use for classroom/lab installs of MSDE to work with Visual Studio .NET
> 2003 will be helpful:
> <quote>
> 1. Before you begin, check the PC to ensure there are no remnants of
> prior MSDE installation attempts hanging around. The place to check is:
> C:\Program Files\Microsoft SQL Server. If you locate a folder named
> Microsoft SQL Server, delete it and its contents!
>
> 2. Execute the file: SQL2KDeskSP3.exe(or whatever the file name for your
> MSDE download is). This step will extract the contents of the file to a
> designated folder. Make a note of the destination folder. You'll need it
> later. This step does not install MSDE (although the dialogs seem to hint
> that it does)!
>
> 4. Navigate to the folder you created in Step 2. In that folder, you will
> find a subfolder named MSDE. In MSDE, you will find SETUP.EXE. Executing
> SETUP.EXE will install MSDE.
>
> 5. To execute SETUP.EXE correctly, you must supply an instance name and a
> system administrator password as part of the command: i.e. the command
> must be:
>
> SETUP.EXE INSTANCENAME="NetSDK" SAPWD="yourSAPassword"
>
> where yourSAPassword is your actual system administrator password. This
> password is needed only to install MDSE, not to use it. Access to MSDE is
> controlled by normal "NT Security" which should allow users access based
> on network logon and password. It is very important the the INSTANCENAME
> parameter be NetSDK, as this name will enable you to generate the sample
> databases automatically instead of having to run SQL scripts from the
> command line.
>
> 6. Once installation is complete, you must reboot the PC before you will
> see MSDE. After the reboot, you should see the MSDE icon in SysTray.
>
> 7. You now must execute the file: ConfigSamples.exe to configure sample
> applications and MSDE system databases. This step will also create user
> databases in the following location: C:\Program Files\Microsoft SQL
> Server\MSSQL\Data.
> </quote>
>
> If you have trouble locating the ConfigSamples.exe, it's a small file
> (56k) and I can send it to your email if needed.
>
> Hope this helps.
>
> --
> Peter [MVP Visual Developer]
> Jack of all trades, master of none.
>

No comments:

Post a Comment