Hi! I've been struggling with a SCCM issue for whole day. I noticed that tempdb transaction log file keeps growing fast and eventually fills all of the disk space. I even moved it to different disk where I had 80GB free, but it ate all of it within 3 hours. The DBCC OPENTRAN('tempdb') and DBCC INPUT BUFFER() gave me this result: Code Snippet Transaction information for database 'tempdb'. Oldest active transaction: SPID (server process ID): 76 UID (user ID) : -1 Name : sort_init LSN : (1290:92656:1137) Start time : Sep 10 2008 3:26:15:627PM SID : 0x010100000000000512000000 DBCC execution completed. If DBCC printed error messages, contact your system administrator. EventType Parameters EventInfo -------------- ---------- ---------------------------------------- Language Event 0 exec sp_UpdateResCollOfferMap 'P010009F' When I checked my primary site status, I noticed SMS_POLICY_PROVIDER messages (msg id: 620): Code Snippet Microsoft SQL Server reported SQL message 530, severity 16: [23000][530][Microsoft][ODBC SQL Server Driver][SQL Server]The statement terminated. The maximum recursion 100 has been exhausted before statement completion. : sp_UpdatePolicyTargetingMap Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information. ...and... Code Snippet Microsoft SQL Server reported SQL message 530, severity 16: [23000][530][Microsoft][ODBC SQL Server Driver][SQL Server]The statement terminated. The maximum recursion 100 has been exhausted before statement completion. : sp_GetListOfCollectionsNeedPolicyTargetingReEval Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information As I understand some SCCM SQL procedure is running something recursively, but it reaches the limit of 100 soon. I've tried restarting SQL service and the server itself, but the errors keep coming each time the server processes collection and policy changes as seen in policypv.log file: Code Snippet--Process Collection ChangesSMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180)Building Collection Change List from Collection Change Notification filesSMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180)Detected member change for collection 1.SMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180)*** exec sp_GetListOfCollectionsNeedPolicyTargetingReEval 1SMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180)*** [23000][530][Microsoft][ODBC SQL Server Driver][SQL Server]The statement terminated. The maximum recursion 100 has been exhausted before statement completion. : sp_GetListOfCollectionsNeedPolicyTargetingReEvalSMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180)AddAffectedCollectionsToChangeList: could not execute SQL cmd exec sp_GetListOfCollectionsNeedPolicyTargetingReEval 1SMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180)--Handle PolicyAssignment ResigningSMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180)--Process Policy ChangesSMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180)Found some Policy changes, returning New LastRowversion=0x0000000000312B8BSMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180)Processing Updated PoliciesSMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180)Building Collection Change List from New and Targeting Changed PoliciesSMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180)--Update Policy Targeting MapSMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180)**** Evaluating Collection 128 for targeting changes ****SMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180)*** exec sp_UpdatePolicyTargetingMap 128SMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180)*** [23000][530][Microsoft][ODBC SQL Server Driver][SQL Server]The statement terminated. The maximum recursion 100 has been exhausted before statement completion. : sp_UpdatePolicyTargetingMapSMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180)UpdatePolicyTargetingMap: could not process the Updated PoliciesSMS_POLICY_PROVIDER1.01.1601 0:00:004480 (0x1180) Has anyone had similar problems? Any ideas how to solve it? Br, Christjan

Case closed! I used Site Repair Wizard and restored the database. The errors disappeared. It might have had caused by two status filter rules that I added few days ago. They were for fixing permissions inheritance with VBScript for Collections and Advertisements. However, scripts were created for SMS, but the author thought they would work on SCCM as well. Actually they did work well, but may be there were side effects. I'll try creating these filtering rules again to confirm they caused the problem - now I know to make extra backup before doing so