dcsimg
Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: MSDE SP3
Expertise: Advanced
Dec 15, 2003

WEBINAR:

On-Demand

Building the Right Environment to Support AI, Machine Learning and Deep Learning


Registering a MSDE SP3 instance into a group in Enterprise Manager

I installed MSDE SP3 as per MS's directions. However, running Enterprise Manager and trying to register the SQL Server instance into a group (this is on the same box that MSDE was installed, BTW) resulted in the old "Server does not exist or access denied" error. This occured whether I used SQL or NT authentication. After the 5th re-install - luckily, I had taken a snap-shot of the machine beforehand, so was able to quickly return to its original state - I figured something was wrong.

The MSKB didn't help, and none of the solutions I was suggested to try worked. What DID work was running SVRNETCN (Start/Run/SVRNETCN). This popped up a basic dialog which immediately told me that SQL wasn't "connected" with any protocol. I clicked TCP/IP over into the right-hand box, clicked Apply and viola! The server registered.

It appears that SP3 installs with no protocol defined. This is in contrast to previous flavours: I'd never encountered SVRNETCN before, as previous installations simply worked.

Ian Northwood
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date