October 16, 2009 at 10:29 am
Hey all,
Couple things here. I have a really old server that I was just told about that is having issues. There is an instance of SQL called "SHAREPOINT" that no one is able to connect to anymore. Checked the error log, and shows that it's only running on shared memory. Using the server network utility, I tried enabling TCP/IP and named pipes ... several times. Every time I restart SQL, still just shared memory. I've seen this before and I was able to resolve by installing SP4.
To confirm I'm on MSDE (sp3a i think?), top of error log:
2009-10-16 12:07:02.63 server Microsoft SQL Server 2000 - 8.00.884 (Intel X86)
Nov 29 2003 20:52:47
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: Service Pack 2)
So, I am now trying to install the MSDE version of SP4:
setup /upgradesp sqlrun INSTANCENAME=SHAREPOINT /L*v C:\MSDELog.log
-- Results in "the instance name specified is invalid"
setup /upgradesp sqlrun DISABLENETWORKPROTOCOLORS=0 INSTANCENAME=SHAREPOINT /L*v C:\MSDELog.log
-- Results in "no version of MSDE was found to upgrade"
setup /upgradesp sqlrun INSTANCENAME=SHAREPOPINT SECURITYMODE=SQL
UPGRADEUSER=sa UPGRADEPWD=sa /L*v C:\MSDELog.log
-- I don't know the sa, so it was a guess as most left it blank back then, anways, results in: "the instance name specified is invalid"
So after some online searching, I found one reference to having to install WMSDE!? This is all I could find on it:
http://support.microsoft.com/?kbid=948110 &
Any thoughts here? I'm at a loss ...
October 19, 2009 at 8:53 am
Hello all, haven't had much luck on this issue and was hoping to catch someone's attention today.
Thanks
October 19, 2009 at 9:54 am
Can you start the instance in single user mode?
Also, any chance you can script out logins and rebuild master, then add them back? It sounds almost like a master database or registry corruption on the machine.
Open a case with MS?
October 19, 2009 at 10:05 am
Steve Jones - Editor (10/19/2009)
Can you start the instance in single user mode?Also, any chance you can script out logins and rebuild master, then add them back? It sounds almost like a master database or registry corruption on the machine.
Open a case with MS?
Hello again Steve. Yeah I could do a /T3608, but it would still be on shared memory. I like the idea, but if i can't connect, there is no way I could script out the logins. Again, I've seen this before on MSDE < SP4, several times actually. I've been able to resolve it every time by installing SP4, yet there in lies the problem.
October 19, 2009 at 10:11 am
good luck. Not sure what to do here. I lean towards calling MS since everything else might cause more issues. That at least provides some CYA to you if things go south. It sounds more and more like a registry issue.
October 19, 2009 at 10:44 am
Came across this: http://blogs.msdn.com/grahamtyler/archive/2004/10/19/244496.aspx. Not sure I completely follow, but I think this helps to fuel the fire that I should be installing the WMSDE SP4?
I checked windows update from the server and it found that Windows SharePoint Services 2.0 Service Pack 3 (KB923643) needs to be updated. The link to the KB is here: http://support.microsoft.com/kb/923643. It doesn't say anything about WMSDE or anything in regards to updating SQL.
Unsure what my next step(s) should be. I can't find an official Microsoft KB for WMSDE SP4...
October 20, 2009 at 4:40 am
Are you sure about the name as all my sharepoint servers default install as Servername\Sharepoint for the instance name? I'd put INSTANCENAME=DevBox\Sharepoint for example.
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy