No problem.

Thanks for the log post. I am not sure if this will help or not, but there maybe another process that is logging onto your SQL Server prior to the service pack updating it. I would recommend stopping your instance and restarting it in single user mode, just like the script shows (or from the command-line sqlservr ... i.e. MSSQL\Binn\sqlservr -c -m -T4022 -T4010), and from another command line session logon to your instance as the script does i.e. osql -Slpc:SQLSVRDEV\EPA -d master (you can omit the -n and - b if you like). If this is the same problem that plagued us on a few systems, you should get something like the database is in use or only one connection is allowed while in single user mode.

For us, we had a Webservice running on the SQL Server (WSUS) that ran as the NT Authority/SYSTEM account, and reconnected to the database as soon as it became available. That was locking out the service pack from connecting and running the replsys.sql file. If something else is blocking you, I would recommend that if you have IIS or a Webserver running on your SQL Server machine, temporarily stop it or just the Web application that is running on it, until your update is complete. Otherwise, you may have hunt down and temporarily stop whatever application is connecting to your database while you update the system.

Hope that this helps ....