Re: SP4 error running replsys.sql

Tech-Archive recommends: Fix windows errors by optimizing your registry



Curt, thank you very for posting these info here, I've been looked around for
days for the answer!

Even I couldn't delete the 'LPC' key, but after I changed the logins for
both server and agent from local user to local system, then stop/start them
via services mmc, sp4 installation worked. I didn't bother change the logins
back because this is a test/dev box.

Thanks once again!

"curt.mader@xxxxxxxxx" wrote:

> I will reply to my own message and tell you how my issue was resolved
> (with the help of a Microsoft Phone Support person in India and to the
> detriment of my wallet to the tune of $245). Hopefully this will help
> any other who are having this same problem...
>
> Here's the short version:
>
> I had switched the account that SQL Server uses to start and I did this
> through the Services MMC. This caused the SQL Server to not listen
> properly on LPC(shared memory). Apparently replsys.sql uses this
> protocol to communicate with the SQL Server.
>
> 1) In the registry, made a backup copy of the LPC key under
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLserver\SuperSocketNetLib
>
> 2) Then delete the LPC key under
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLserver\SuperSocketNetLib
> (Disclaimer: I make no guarantees to anyone who messes with the
> registry)
>
> 3) Using the Services MMC I set the SQL Server startup account back to
> the Local System account and restarted the SQL Server instance.
>
> 4) Changed the SQL start up account to domain account using the SQL
> Enterprise Manager and again restarted that instance of SQL Server.
>
> Ta-da! The SP4 installation worked!
>
> Here are some other MS KB links that the tech support guy sent to me:
>
> Potential causes of the "SQL Server does not exist or access denied"
> error message http://support.microsoft.com/?id=328306
>
> How to troubleshoot the "Cannot generate SSPI context" error message
> http://support.microsoft.com/default.aspx?scid=kb;en-us;811889
>
> How to troubleshoot connectivity issues in SQL Server 2000
> http://support.microsoft.com/default.aspx?scid=kb;en-us;827422
>
> HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
> http://support.microsoft.com/default.aspx?scid=kb;en-us;246133
>
> -Curt Mader (I got by with a little help from my friends (at Microsoft
> tech Support))...
>
>
.



Relevant Pages

  • Re: Error 15401 using sp_grantlogin (not addressed by current KB articles)
    ... Restarting Windows 2000 resolved the problem for this particular account, ... confused when it sees a duplicate SID. ... > One way to get SQL Server to agree with the renamed NT ... > Preview (to ensure the script was created), ...
    (microsoft.public.sqlserver.security)
  • Re: SharePoint V3 Install Error
    ... But it our case it had to do with Group Policies that forbid the account of ... WSS FAQ:www.wssv3faq.com/wss.collutions.com ... Event Source: WindowsSharePointServices3Search ... whatever you are installing WSS as sufficient rights to the SQL Server ...
    (microsoft.public.sharepoint.windowsservices)
  • RE: Problems with WebParts
    ... to a database called aspnetdb. ... > The connection string specifies a local SQL Server Express instance using a ... > server account must have read and write access to the applications directory. ... > This is necessary because the web server account will automatically create ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Cannot connect to Query Analyzer
    ... For Query Analyzer, I tried replacing the file as you suggested but had the ... same results (Enterprise Manager starts up fine, ... I created an account on my laptop and changed SQL ... Try replacing the MMC app for SQL Server from the original ...
    (microsoft.public.sqlserver.connect)
  • Re: Does anyone know how to fix this??
    ... > Inside the Active Directory Users and Computers in the folder of SYSTEM I ... Give the site's SMS Service account full control rights to the ... MP encountered an error when connecting to SQL Server. ...
    (microsoft.public.sms.setup)