I am replying here as I am not able to view your last reply posted on

http://www.sqlservercentral.com/Forums/Topic669605-146-1.aspx

Is that upgrade problem resolved? If not then locate instmsdb file and specify a...

TYpe gpedit.msc at the run command of the machine where your are performing the upgrade. Go to COmputer configuration-->windows settings-->security settings-->Account Policies-->Password....

Or

Just use a strong password.

MJ

Have you tried what I suggested just now. Changin hard coded password.

Check-->

The work-around is to edit the INSTMSDB.SQL script and change two instances of Yukon90_ to something more complex. ...

Leave what I said above.

Try this:

It appears that the offending password is in the line:

encryption by password = 'Yukon90_'

in the script sqlagent90_msdb_upgrade.sql.

I found this problem, changed the password in the...

Try performing those steps for SQL 2000 instance:

Instead of configuration manager use services applet.

MJ

Have you tried Method1 stated in KB article-->http://support.microsoft.com/kb/936892/en-us.

Method 1: Update the password of the SQL Server login to comply with the password policy in Windows Server 2003

MJ

See if this helps:

A workaround solution has been discovered, in relation to this Microsoft KB (Knowledge Base) Article : Error message in the SQL Server Error log file after you...

Attached is a .bat file and sql script for moving system databases. Try altering it to include the user databases.

MJ

You can specify a different path.

MJ

Moin,

Just use sp_dropsubscription(http://msdn.microsoft.com/en-us/library/ms184385(SQL.90).aspx) and get rid of that subscriber.

EXEC sp_dropsubscription

@publication = @publication,

@article = N'all',

@subscriber = @subscriber;

GO

MJ

Rebuild indexes when avg_fragmentation_in_percent > 30

Check-->http://blogs.msdn.com/jorgepc/archive/2007/12/09/how-to-check-fragmentation-on-sql-server-2005.aspx

For script-->http://sql-server-performance.com/Community/forums/p/27772/149694.aspx

HTH!

MJ

Have you checked the installation log file at

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG

MJ

Why don't you start with comparing sp_configure output first.

MJ

Don't forget to check Books online(installed with sql server installation).

MJ

I noticed it now. Better take help from books online for this:

http://msdn.microsoft.com/en-us/library/ms174997(SQL.90).aspx

MJ