SQL Server Settings Messed up everything?
- SCE was working fine until I realized that the SQL db properties for filegroups wasn't properly configured. Software was rolling out, updates was working fine... Groups and Computers working fine. Then the db filled up and I checked the settings on the DB because I wasn't the one who setup the server and Autogrowth was set to None. Then the console wouldn't even open and nothing was updating. Changed that setting to 10% growth increments. That worked for a day or two then the same problems occurred. Realized that the DB size was set to like 1.3 Mb. Changed that to pretty much unlimited and everything came back up but I've been getting NUMEROUS errors ever since including WSUS not synchronizing groups taking everything to a stand-still... SQL is working fine now but it appears to be the only thing!
I tried to create a new group to see if that would be a workaround but that doesn't appear to be making a difference.
I'm also in the middle of rolling out software and need to complete the task! HELP!
(Also, what can you use and not use in WSUS? Can you use the console and if so how would you go about using it properly without messing anything up?)
Réponses
Hello Steve,
While you said "SQL is working fine now", there are lots of errors that related to the SQL Server. For example, MSSQLSERVER Service cannot be started and the database Free Space Low. Please make sure the database server was properly configured and worked normally.
If you have backup the database before, you can restore it by following the article below:
How to Back Up and Restore System Center Essentials
http://technet.microsoft.com/en-us/library/bb437269.aspx
For the error about "The SCE Group could not synchronize to its associated WSUS Group", which indicates that WSUS computer groups are not same with SCE computer groups. It’s especially from that a computer group was deleted from the WSUS console, instead of using the SCE console. For more information, read the following thread:Event ID 30201
http://social.technet.microsoft.com/Forums/en-US/systemcenter/thread/7ee2423f-4f89-4eef-aa6e-5bf8598686f8Thanks,
Yog Li - MSFT- Marqué comme réponseYog Li - MSFTMSFT, Modérateurvendredi 3 juillet 2009 10:59
Toutes les réponses
Hello Steve,
Could you post some more details about this problem so we can understand it clearly? If everything is messed up, the only comment is that you can re-install the SCE server. We'd better handle a specific, concrete problem on this forum.
About the WSUS console, you can use it to view the updates and computers. Do not modify anything by using the WSUS console. For example, do not delete the agent or the computer group on it.
Thanks,
Yog Li - MSFT- Yog Li - If I knew that there wouldn't be a problem... Here are the error alerts since everything listed above. I don't really see reinstalling as an option, I was in the middle of a working Software rollout that clients are waiting for. Set the packaged to deploy and worked fine. Added more groups for a location based rollout and it failed. This all started with the problem above.
An error occurred while the query log table was being created Alert Description
Source: MSSQLSERVER The flight recorder was started.
Path: server.domain.local\MSSQLSERVER
Alert Rule: An error occurred while the query log table was being created
OleDB: Results Error Alert Description
Source: server.domain.local OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor Instance name: server.domain.local Instance ID: {C05CC737-80C4-4334-E029-0D95048C0AE8} Management group: SERVER_MG
Path: server.domain.local\server.domain.local
Alert Rule: OleDbProbe: Results Error
Created: 6/18/2009 11:00:11 AM
Ops DB Free Space Low Alert Description
Source: server.domain.local Operations Manager operational database percent free space is 13.94%. Ops DB Server Name: SERVER Ops DB Name: OperationsManager
Path: server.domain.local\server.domain.local
Alert Monitor: Operational Database Space Free (%)
Created: 6/18/2009 9:09:41 AM
The service cannot be started Alert Description
Source: MSSQLSERVER Service started.
Path: server.domain.local\MSSQLSERVER
Alert Rule: The service cannot be started
Created: 6/17/2009 4:39:36 PM
Content Synchronization Alert Description
Source: WSUS
Path: server.domain.local\WSUS
Alert Monitor: Content Synchronization
Created: 6/18/2009 3:12:03 PM
Operations Manager Connection Failure Warning Alert Description
Source: server.domain.local The SCE Group identified by 'df93d5ff-641f-7162-ac20-b43dac5a2568' could not synchronize to its associated WSUS Group identified by '46cd663f-db42-4b8e-a8ab-7d99f89df464' because a connection to the SCE server could not be made. The synchronization will be retried. Management Group: SERVER_MG Rule: System.SCE.MP.GroupSynchronizationRule Instance: 46cd663f-db42-4b8e-a8ab-7d99f89df464.df93d5ff-641f-7162-ac20-b43dac5a2568 Instance Id:{1500DF41-5D6C-F2D7-4981-5FB05A6361BC} The following error occurred. System.TimeoutException: The requested operation timed out. ---> System.TimeoutException: This request operation sent to net.tcp://localhost:5724/SdkDataAccess did not receive a reply within the configured timeout (00:30:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client. Server stack trace: at System.ServiceModel.Dispatcher.DuplexChannelBinder.SyncDuplexRequest.WaitForReply(TimeSpan timeout) at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnM
AEM: Permissions Error Alert Description
Source: server.domain.local FillerPA module has encountered a permissions error 'A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)'. Workflow name: Microsoft.SystemCenter.CM.AEM.Internal.ResponsePublisher Instance name: \server.domain.local\apps Errors Instance ID: {A421FDD2-D160-A1BB-E432-B4C1DCC54159} Management group: SERVER_MG
AEM: File Share Error Alert Description
Source: server.domain.loca CrashListenerPA module finds fileShare is not reachable/accessible or validation failed. Workflow name: Microsoft.SystemCenter.CM.AEM.Internal.ResponsePublisher Instance name: \\server.domain.local\apps Errors Instance ID: {A421FDD2-D160-A1BB-E432-B4C1DCC54159} Management group: SERVER_MG Hello Steve,
While you said "SQL is working fine now", there are lots of errors that related to the SQL Server. For example, MSSQLSERVER Service cannot be started and the database Free Space Low. Please make sure the database server was properly configured and worked normally.
If you have backup the database before, you can restore it by following the article below:
How to Back Up and Restore System Center Essentials
http://technet.microsoft.com/en-us/library/bb437269.aspx
For the error about "The SCE Group could not synchronize to its associated WSUS Group", which indicates that WSUS computer groups are not same with SCE computer groups. It’s especially from that a computer group was deleted from the WSUS console, instead of using the SCE console. For more information, read the following thread:Event ID 30201
http://social.technet.microsoft.com/Forums/en-US/systemcenter/thread/7ee2423f-4f89-4eef-aa6e-5bf8598686f8Thanks,
Yog Li - MSFT- Marqué comme réponseYog Li - MSFTMSFT, Modérateurvendredi 3 juillet 2009 10:59
- One of the most frustrating parts of working with SCE is the lack of documentation on it. WSUS, sure... Operations Manager, yeah. But actually the interworkings of SCE really isn't documented well anywhere.
Any idea, based on this post, what may have caused these issues? We went from working and rolling out Outlook 2007 to being down completely basically overnight.
And as far as I know no one has messed with any WSUS settings in the console. - Hello,
For SCE documents, you can visit the webpage below:
System Center Essentials 2007 Online Help
http://technet.microsoft.com/en-us/library/bb422837.aspx
Thanks,
Yog Li - MSFT - Hi,
For SCE documentation, you can visit the link below:
System Center Essentials 2007 Online Help
http://technet.microsoft.com/en-us/library/bb422837.aspx
Thanks,
Yog Li - MSFT Thanks Yog Li but that is what I was referring too. Really surface level stuff. Try to decipher how SCE connects to WSUS and how you can troubleshoot software not rolling out and if or how to reconnect SCE to WSUS if there is an issue. Or how to add Serial Numbers to Inventory collection or why the console hangs if the database gets full... This type of stuff isn't covered in there. I have a huge Operations Manager book that is a good reference source but there really needs to be a SCE book with full documentation.
- Hi Steve,
Thanks for sharing your experience and pointing out the questions. The SCE v2 will be released in a few months. There must be some improvements in the new version of SCE. And I hope there will be more SCE books with more and more SCE users.
Thanks,
Yog Li - MSFT
