|
|
I'm having some big problems with WSUS3. I installed it as an upgrade to
our WSUS2 install and kept getting the following errors. I reinstalled and
still got the errors. Everything worked fine to start with, but after a
reboot the errors started.
I have now got a brand new box running W2K3R2 + SP2 it's a vanilla install
running nothing else, and I'm STILL getting the same errors. I'm now
thinking it must be something that is configured in our group policy, its
driving me nuts!
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 12/07/2007
Time: 16:47:21
User: N/A
Computer: LUNDY
Description:
The Windows Internal Database (MICROSOFT##SSEE) service terminated with
service-specific error 3417 (0xD59).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSSQL$MICROSOFT##SSEE
Event Category: (2)
Event ID: 17053
Date: 12/07/2007
Time: 16:46:00
User: N/A
Computer: LUNDY
Description:
UpdateUptimeRegKey: Operating system error 5(error not found) encountered.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 9d 42 00 00 10 00 00 00 B......
0008: 16 00 00 00 4c 00 55 00 ....L.U.
0010: 4e 00 44 00 59 00 5c 00 N.D.Y.\.
0018: 4d 00 49 00 43 00 52 00 M.I.C.R.
0020: 4f 00 53 00 4f 00 46 00 O.S.O.F.
0028: 54 00 23 00 23 00 53 00 T.#.#.S.
0030: 53 00 45 00 45 00 00 00 S.E.E...
0038: 00 00 00 00 ....
Event Type: Error
Event Source: MSSQL$MICROSOFT##SSEE
Event Category: (2)
Event ID: 17207
Date: 12/07/2007
Time: 16:46:01
User: N/A
Computer: LUNDY
Description:
FCB::Open: Operating system error 5(error not found) occurred while creating
or opening file 'C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf'.
Diagnose and correct the operating system error, and retry the operation.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 37 43 00 00 10 00 00 00 7C......
0008: 16 00 00 00 4c 00 55 00 ....L.U.
0010: 4e 00 44 00 59 00 5c 00 N.D.Y.\.
0018: 4d 00 49 00 43 00 52 00 M.I.C.R.
0020: 4f 00 53 00 4f 00 46 00 O.S.O.F.
0028: 54 00 23 00 23 00 53 00 T.#.#.S.
0030: 53 00 45 00 45 00 00 00 S.E.E...
0038: 00 00 00 00 ....
Event Type: Error
Event Source: MSSQL$MICROSOFT##SSEE
Event Category: (2)
Event ID: 17204
Date: 12/07/2007
Time: 16:46:01
User: N/A
Computer: LUNDY
Description:
FCB::Open failed: Could not open file
C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf for file number 1.
OS error: 5(error not found).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 34 43 00 00 10 00 00 00 4C......
0008: 16 00 00 00 4c 00 55 00 ....L.U.
0010: 4e 00 44 00 59 00 5c 00 N.D.Y.\.
0018: 4d 00 49 00 43 00 52 00 M.I.C.R.
0020: 4f 00 53 00 4f 00 46 00 O.S.O.F.
0028: 54 00 23 00 23 00 53 00 T.#.#.S.
0030: 53 00 45 00 45 00 00 00 S.E.E...
0038: 00 00 00 00 ....
Event Type: Error
Event Source: MSSQL$MICROSOFT##SSEE
Event Category: (2)
Event ID: 17207
Date: 12/07/2007
Time: 16:46:01
User: N/A
Computer: LUNDY
Description:
FCB::Open: Operating system error 5(error not found) occurred while creating
or opening file 'C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf'.
Diagnose and correct the operating system error, and retry the operation.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 37 43 00 00 10 00 00 00 7C......
0008: 16 00 00 00 4c 00 55 00 ....L.U.
0010: 4e 00 44 00 59 00 5c 00 N.D.Y.\.
0018: 4d 00 49 00 43 00 52 00 M.I.C.R.
0020: 4f 00 53 00 4f 00 46 00 O.S.O.F.
0028: 54 00 23 00 23 00 53 00 T.#.#.S.
0030: 53 00 45 00 45 00 00 00 S.E.E...
0038: 00 00 00 00 ....
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 12/07/2007
Time: 16:47:39
User: N/A
Computer: LUNDY
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 7/12/2007 4:47:39 PM
Event time (UTC): 7/12/2007 3:47:39 PM
Event ID: acdc6edff6864aa69aa884ffcf7f67f0
Event sequence: 2
Event occurrence: 1
Event detail code: 0
Application information:
Application domain:
/LM/W3SVC/1/ROOT/ReportingWebService-3-128287287988599616
Trust level: Full
Application Virtual Path: /ReportingWebService
Application Path: C:\Program Files\Update
Services\WebServices\ReportingWebService\
Machine name: LUNDY
Process information:
Process ID: 2280
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: SqlException
Exception message: 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. (provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)
Request information:
Request URL: http://lundy/ReportingWebService/ReportingWebService.asmx
Request path: /ReportingWebService/ReportingWebService.asmx
User host address: 192.171.161.44
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 8
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception,
Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj)
at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner,
Boolean& failoverDemandDone, String host, String failoverPartner, String
protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean
encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection
owningObject, Boolean aliasLookup)
at
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo, String
newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect(String
connectionString)
at Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect()
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.ExecuteSPMultipleResultSets(String
spName, DBParameterCollection args, Type[] resultTypes)
at
Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetConfiguration()
at
Microsoft.UpdateServices.Internal.BaseApi.UpdateServerConfiguration.Load()
at
Microsoft.UpdateServices.Internal.BaseApi.UpdateServerConfiguration..ctor()
at
Microsoft.UpdateServices.Internal.ClassFactory.CreateWellKnownType(Type
type, Object[] args)
at Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type
type, Object[] args)
at
Microsoft.UpdateServices.Internal.Reporting.ReportingFactory.LoadSettings(ReportingQueue
queue, EventDispatcher dispatcher, Boolean updateServiceEventReporter)
at
Microsoft.UpdateServices.Internal.Reporting.ReportingFactory.CreateReportingQueue()
at Microsoft.UpdateServices.Internal.Reporting.ReportingServer..ctor()
at
Microsoft.UpdateServices.Internal.Reporting.ReportingServer.get_Instance()
at
Microsoft.UpdateServices.Internal.Reporting.Global.Application_BeginRequest(Object
sender, EventArgs e)
at
System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously)
Custom event details:
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 12/07/2007
Time: 16:48:10
User: N/A
Computer: LUNDY
Description:
Event code: 3001
Event message: The request has been aborted.
Event time: 7/12/2007 4:48:10 PM
Event time (UTC): 7/12/2007 3:48:10 PM
Event ID: 5d9beb45157346ee81b98d69f4035f28
Event sequence: 4
Event occurrence: 1
Event detail code: 0
Application information:
Application domain:
/LM/W3SVC/1/ROOT/ClientWebService-1-128287287672500000
Trust level: Full
Application Virtual Path: /ClientWebService
Application Path: C:\Program Files\Update
Services\WebServices\ClientWebService\
Machine name: LUNDY
Process information:
Process ID: 2280
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: HttpException
Exception message: Request timed out.
Request information:
Request URL: http://lundy/ClientWebService/client.asmx
Request path: /ClientWebService/client.asmx
User host address: 192.171.162.57
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace:
Custom event details:
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
|
|
"Kerry Hoskin" <kjho[ at ]npm.ac.uk> wrote in message
news:67E7DD70-65F4-433E-BA4E-D63453315C4C[ at ]microsoft.com...
[Quoted Text] > FCB::Open: Operating system error 5(error not found) occurred while
> creating or opening file
> 'C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf'.
> FCB::Open failed: Could not open file
> C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf for file number 1.
> FCB::Open: Operating system error 5(error not found) occurred while
> creating or opening file
> 'C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf'.
Looks to me like the installation of WID is corrupted.
Best suggestion is to uninstall WSUS and WID and start from scratch.
To uninstall WID after uninstalling WSUS, refer to this KB article:
http://support.microsoft.com/kb/920277
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://www.microsoft.com/wsus
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
trouble is this is happening every time I install it!
"Lawrence Garvin (MVP)" <onsitech[ at ]community.nospam> wrote in message
news:uupD44PxHHA.2488[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > "Kerry Hoskin" <kjho[ at ]npm.ac.uk> wrote in message > news:67E7DD70-65F4-433E-BA4E-D63453315C4C[ at ]microsoft.com... > >> FCB::Open: Operating system error 5(error not found) occurred while >> creating or opening file >> 'C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf'. > >> FCB::Open failed: Could not open file >> C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf for file number >> 1. > >> FCB::Open: Operating system error 5(error not found) occurred while >> creating or opening file >> 'C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf'. > > Looks to me like the installation of WID is corrupted. > > Best suggestion is to uninstall WSUS and WID and start from scratch. > > To uninstall WID after uninstalling WSUS, refer to this KB article: > http://support.microsoft.com/kb/920277> > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E> > Everything you need for WSUS is at > http://www.microsoft.com/wsus> > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com> .... > > >
|
|
|