|
| WSUS 3.0 Replika problem |
 |
Tue, 4 Mar 2008 03:19:00 -0800 |
Hello,
Our WSUS 3.0 since October the 9th synchronisations are failing with the
following (and beautiful in itself) error:
SqlException: The specified revision could not be found.
at
Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(Sq
lException e)
at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteReader()
at
Microsoft.UpdateServices.Internal.SingleResultSetSPHandler.ExecuteStoredProcedur
e(DBConnection connection)
at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String
spName, DBParameterCollection args, IExecuteSPHandler handler, Int32
queryTimeoutInSeconds)
at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String
spName, DBParameterCollection args, IExecuteSPHandler handler)
at
Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ExecuteSPSingl
eResultSet(String
spName, DBParameterCollection args, Type resultType, Int32
queryTimeoutInSeconds)
at
Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ExecuteSPSingl
eResultSet(String spName, DBParameterCollection args, Type resultType)
at Microsoft.UpdateServices.Internal.DatabaseAccess.Admin
It only happens when the server is set up as a replica, otherwise all is ok
|
| Post Reply
|
| RE: WSUS 3.0 Replika problem |
 |
Tue, 18 Mar 2008 04:38:01 -070 |
On my environment looks like Internal Database das been broken. Because
reinstallation of WSUS 3.0 (even WSUS 3.0 SP1) only does not help.
In addition I had problem that UPSTREAM server is not under my
administration. So was even difficult to get info which versions of WSUS and
SQL is on it.
The working solution In my case was
-Uninstall WSUS and Internal database
-Rename directory used by uninstalled instance of WSUS
Then
installation SQL 2005 Express
installation WSUS 3.0 SP1
I did it on Friday March 15,2008 and seams to working well.
"Pawel" wrote:
> Hello,
> Our WSUS 3.0 since October the 9th synchronisations are failing with the
> following (and beautiful in itself) error:
>
> SqlException: The specified revision could not be found.
>
> at
>
Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(Sq
lException e)
>
> at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteReader()
>
> at
>
Microsoft.UpdateServices.Internal.SingleResultSetSPHandler.ExecuteStoredProcedur
e(DBConnection connection)
>
> at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String
> spName, DBParameterCollection args, IExecuteSPHandler handler, Int32
> queryTimeoutInSeconds)
>
> at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String
> spName, DBParameterCollection args, IExecuteSPHandler handler)
>
> at
>
Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ExecuteSPSingl
eResultSet(String
> spName, DBParameterCollection args, Type resultType, Int32
> queryTimeoutInSeconds)
>
> at
>
Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ExecuteSPSingl
eResultSet(String spName, DBParameterCollection args, Type resultType)
>
> at Microsoft.UpdateServices.Internal.DatabaseAccess.Admin
>
>
>
> It only happens when the server is set up as a replica, otherwise all is
ok
|
| Post Reply
|
|
|
|
|
|
|
|
|
|