I have set up a new SCCM SP2 primary site server in a new environment hosted on Windows 2008 SP2 using SQL Server 2005 Standard SP3. When I install the PSP role, I notice immediately the following errors in smsdbmon.log and hman.log
smsdbmon.log:
Evaluating tasks and commands.SMS_DATABASE_NOTIFICATION_MONITOR13/11/2009 12:42:24 PM4256 (0x10A0)
SND: Dropped E:\Microsoft Configuration Manager\inboxes\ddmnotif.box\CAB.SCA [1686C827-D5B4-49A4-96C9-FA0898983BC2]SMS_DATABASE_NOTIFICATION_MONITOR13/11/2009 12:42:24 PM4252 (0x109C)
*** exec spGetChangeNotificationsSMS_DATABASE_NOTIFICATION_MONITOR13/11/2009 12:43:04 PM4252 (0x109C)
*** [08S01][11][Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.SMS_DATABASE_NOTIFICATION_MONITOR13/11/2009 12:43:04 PM4252 (0x109C)
ERROR - SQL Error -1 in CSQLPollingThread::Poll()SMS_DATABASE_NOTIFICATION_MONITOR13/11/2009 12:43:04 PM4252 (0x109C)
Setting SMS SQL Server Availability State to a value of 1SMS_DATABASE_NOTIFICATION_MONITOR13/11/2009 12:43:09 PM4252 (0x109C)
*** exec spGetChangeNotificationsSMS_DATABASE_NOTIFICATION_MONITOR13/11/2009 12:43:09 PM4252 (0x109C)
*** [08S01][0][Microsoft][ODBC SQL Server Driver]Communication link failureSMS_DATABASE_NOTIFICATION_MONITOR13/11/2009 12:43:09 PM4252 (0x109C)
*** exec spGetChangeNotificationsSMS_DATABASE_NOTIFICATION_MONITOR13/11/2009 12:43:09 PM4252 (0x109C)
*** [08S01][0][Microsoft][ODBC SQL Server Driver]Communication link failureSMS_DATABASE_NOTIFICATION_MONITOR13/11/2009 12:43:09 PM4252 (0x109C)
Setting SMS SQL Server Availability State to a value of 0SMS_DATABASE_NOTIFICATION_MONITOR13/11/2009 12:43:09 PM4252 (0x109C)
hman.log:
*** set quoted_identifier off;set ansi_warnings off;set ansi_padding off;set ansi_nulls off;set concat_null_yields_null off;set arithabort on;set numeric_roundabort off;set DATEFORMAT mdy;SMS_HIERARCHY_MANAGER13/11/2009 12:42:54 PM3968 (0x0F80)
*** [HY018][11][Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.SMS_HIERARCHY_MANAGER13/11/2009 12:42:54 PM3968 (0x0F80)
*** Failed to connect to the SQL Server.SMS_HIERARCHY_MANAGER13/11/2009 12:42:54 PM3968 (0x0F80)
These error messages then constantly appear in these logs. If I uninstall the PSP role then these error messages dissapear and the site is healthy again. The PSP installation logs appear to be clean aswell and the smspxe.log only states "Failed to read PXE settings. The system cannot find the file specified. (Error: 80070002; Source: Windows)smspxe13/11/2009 12:42:29 PM4632 (0x1218)" which I believe can be ignored
I have tried removing and reinstalling WDS and the PSP with the same result. I have even rebuilt the entire server from scratch and I still have this problem.
Any ideas would be greatly appreciated
Thanks
Hi there ,
Did you :
1. Configure the WDS server , before adding the PSP role ?
2. I guess the sql is on a remote box:
If SQL is installed with the system account : Is the computer account of the SCCM server member of the local admin group on the SQL server.
If SQL is installed witha serviceaccount : Register the SPN
please provide us with some more detail of the backend infra ...
Hope it helps
Kenny
Thanks for the reply!
1. WDS was installed before the PSP role was added.
2. SQL has been installed on the same box as ConfigMgr as follows:
- Installed with the local system account and is using windows authentication. The SPN has not been registered as I am using the local system account.
The site is perfectly healthy until I install the PSP and once I remove the PSP role the SQLcommunication failure errorsdissapear.
I've never seen this type of behavior before - perhaps it's an issue with ConfigMgr SP2 and SQL 2005?
Any suggestions appreciated
Cheers
- Marked as answer by Moiz Rassiwala[MSFT]Microsoft employee, Moderator Friday, February 24, 2012 9:29 PM
Thanks for the reply!
1. WDS was installed before the PSP role was added.
2. SQL has been installed on the same box as ConfigMgr as follows:
- Installed with the local system account and is using windows authentication. The SPN has not been registered as I am using the local system account.
The site is perfectly healthy until I install the PSP and once I remove the PSP role the SQLcommunication failure errorsdissapear.
I've never seen this type of behavior before - perhaps it's an issue with ConfigMgr SP2 and SQL 2005?
Any suggestions appreciated
Cheers
- Marked as answer by Moiz Rassiwala[MSFT]Microsoft employee, Moderator Friday, February 24, 2012 9:29 PM
My apologies for replying to an old post, but was this issue ever resolved?
If it was, what was the fix?
I am having a similar issue where the 'exec spGetChangeNotifications' transaction gets SUSPENDED in the SMS database. Program name is SMS_DATABASE_NOTIFICATION_MONITOR.
I am a DBA, not a SCCM guy, the SCCM guys are complaining that SCCM is not working though, so I am wondering if this was ever resolved. Looks like the same issue...