2005 SP1 (remote Reporting Services upgrade failures)

Why can it never be easy? I applied SP1 to one of our 2005 database servers and upgraded all components successfully. However when trying to install on a stand alone Reporting Services instance that uses the above database server I can't get past the Login verification. Windows or Sql...Per the ReadMe I am using an acccount that is administrator on both servers and sysadmin in sql, also am running the exe as same admin account.

There are no logs under %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files but I found this error in the hotfix log.

[SQL Native Client]TCP Provider: The requested address is not valid in
its context.
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a
connection to the server. When connecting to SQL Server 2005, this
failure may be caused by the fact that under the default settings SQL
Server does not allow remote connections.

Verified that the SQL Server allows remote connections (TCP\IP is enabled, Named Pipes is not); even started the Browser sevice that hasn't been running and still get the same error.

Will the steps outlined by Lukasz at http://blogs.msdn.com/lukaszp/archive/2006/05/18/601340.aspx solve my problem or will I still need to upgrade the RS files somehow? I think I belong to 'Sometimes does not work" #3. The Native Client upgrade runs fine by itself.

Advice and commiserations appreciated.

AB

Solved error above by recreating the client alias to the sql server. The port designation had disappeared even though it was default port.

Now am experiencing locked file errors - SQL Reporting Services service is disabled and the web site is stopped. What other services need to be stopped? Do services on the remote sql server also need to be stopped?

AB