Re: Service Account Password Change

Just had to do this today as well, after multiple password lockouts. I
went through the services and changed the password, went through the
app pools and changed the passwords, when I got to the sharepoint admin
site, i experienced the same problems as you. I found that in sql
enterprise, the sharepoint domain account didnt have the database admin
role - I ticked the box, rebooted the server twice and hey presto, no
more lockouts. I could then go into the sharepoint admin site and
change the passwords as needed. everything now seems to be working
okay, its a dev environment anyway, so ho hum
Our dev environment is a domain member server running sharepoint portal
server 2003 and sql 2000 on the same box

hope this helps someone

cheers

matt


joshua_jacobsen@xxxxxxx wrote:
> For anybody with similar problems, we encountered the problem again,
> and Microsoft Technical Support worked us through it. I guess we got
> better guys this time around. It isn't an easy fix, however, and I
> think it's a bit risky. I'll summarize it, but I'm a bit lazy, and
> hope that anyone who needs this info will have enough administrative
> experience to follow me. You can email me, if I'm not being explicit
> enough.
>
> First, clean up your passwords.
>
> On each server in your farm, go into IIS Administration, and check
the
> properties of all your SharePoint-related app pools. On the identity
> tab, re-enter your current password and apply. Recycle all of your
app
> pools to make sure everything is using the good credentials. Open
the
> Services MMC, and look for the four SharePoint services. These are
> "Microsoft SharePointPS Search", "SharePoint Portal Administration",
> "SharePoint Portal Alert", and "SharePoint Timer Services". Open the
> properties for each one of these. Under the "Log On" tab, set the
> password to your current password. On the "General" tab, stop and
> restart the service.
>
> Tedius, eh?
>
> Next, tear apart your SharePoint Topology and scrap the Config
> Database.
>
> Go into sharepoint central administration, under the SharePoint
Portal
> Server section, and manage the topology. Select "Change Components"
> and removed every server from every role, and set the Job Server to
> none.
>
> Next, delete the portals (but do not delete the content databases,
when
> given the choice).
>
> Detach from the config database in SharePoint Central Administration
> and deleted the config database on the SQL Server.
>
> Sweet. Now rebuild it.
>
> SharePoint will force you to recreate the config database. You
should
> be able to use the same name, if you like. Next, recreate the portal
> sites, attaching to the still-existing content databases. Last, go
> into the topology and select the original roles for each server.
>
> That's it... resolved the database error for us.
>
> "Error accessing database. Ve rify that the database server name and
> the instance name (if present) are correct. Also, ensure the
> configuration database administration account has sufficient
> permissions on the server or instance and the service corresponding
to
> your SQL Server instance is running."

.

Relevant Pages

  • RE: transfer companyweb config db
    ... configuration database for sharepoint services to a new location on the sql ... You may mistake SQL server conception. ... Move the Monitoring Database ... >project web access not working correctly is to use a config database on ...
    (microsoft.public.windows.server.sbs)
  • I broke Sharepoint :(
    ... SBS was installed and the server was up and running including the default ... After 2 days I was looking at SQL backups I relaised that Sharepoint ... database and the other instances were not migrated accross. ...
    (microsoft.public.windows.server.sbs)
  • Steps for Migrating WSS 3.0 from Windows Internal Database to Microsoft SQL 2005
    ... done the stupid things I did when I started playing with Sharepoint ... when I first installed it and assuming that it would find the SQL 2005 ... Windows Internal Database). ... Reboot the server to finish up any uninstall scripts. ...
    (microsoft.public.sharepoint.windowsservices)
  • RE: Failing Application?
    ... logon the server, and you find the following error message in Event Log: ... Check the database connection information and make sure that the database ... this problem could be caused because the SharePoint ... Timer Service failed to contact the SharePoint database while the SBS is ...
    (microsoft.public.windows.server.sbs)
  • Re: SPS 2003 Portal change SQL server
    ... db's to new server and save the config database for last). ... Stop the virtual server in IIS ... Sharepoint Portal Server ...
    (microsoft.public.sharepoint.portalserver)