JYBejesh
asked on
SQL Crash with working SCCM 2007 environment
HI, my SQL database crashed for my working SCCM 2007 environment and I could not connect to the SCCM admin console. After reinstalling the SQL database(SQL Server 2008 R2), I am able to connect to the admin console and I can see all the packages etc. But I am not able to deploy any packages any more. Can any one point me to the right direction to fix this. I had all the packages and task sequences working prior to the crash. Any clues?
X Layer
What error do you get? Site status is ok?
Please post all Logfiles from the Site Server.
Are the Packages still installed on the DPs?
Are the Packages still installed on the DPs?
ASKER
Hi All,
Thanks for the quick response:
-I am not getting any error. From the advertisement status, I can see that the client machine has received the advertisment and is downloading the program, but then no further status messages.
- Site System Status all shows Ok, but Under component status I can see some critical errors in SMS_CLIENT_CONFIG_MANAGER;
I am attaching the screen shots for those errors.
I checked the statesys.log file and found many sql related errors
CMessageProcessor - Encountered a non-fatal SQL error while processing SMS_STATE_SYSTEM 10/13/2011 12:17:01 PM 25868 (0x650C)
CMessageProcessor - Non-fatal error while processing q55hepa7.SMW SMS_STATE_SYSTEM 10/13/2011 12:17:01 PM 25868 (0x650C)
I am attaching the log file as well. Is there any other log files you want to have a look?
component-status-errors.doc component-status-errors.doc
statesys.log
Thanks for the quick response:
-I am not getting any error. From the advertisement status, I can see that the client machine has received the advertisment and is downloading the program, but then no further status messages.
- Site System Status all shows Ok, but Under component status I can see some critical errors in SMS_CLIENT_CONFIG_MANAGER;
I am attaching the screen shots for those errors.
I checked the statesys.log file and found many sql related errors
CMessageProcessor - Encountered a non-fatal SQL error while processing SMS_STATE_SYSTEM 10/13/2011 12:17:01 PM 25868 (0x650C)
CMessageProcessor - Non-fatal error while processing q55hepa7.SMW SMS_STATE_SYSTEM 10/13/2011 12:17:01 PM 25868 (0x650C)
I am attaching the log file as well. Is there any other log files you want to have a look?
component-status-errors.doc component-status-errors.doc
statesys.log
First check BITS and .NET Framework. You can try reinstalling them.
ASKER
Tried reinstalling them, but still looks the same :(
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check out this:
1. Explore "SQL Server 2005/Configuration Tools/Surface Area Configuration" in your Start menu.
2. Select "Surface Area Configuration for Features"
3. You will find "CLR Integration" option, activate it and save.
1. Explore "SQL Server 2005/Configuration Tools/Surface Area Configuration" in your Start menu.
2. Select "Surface Area Configuration for Features"
3. You will find "CLR Integration" option, activate it and save.
ASKER
Thanks, after enabling CLR integration, it worked :)...
Cheers!
Bejesh
Cheers!
Bejesh