Notification Agent

The notification agent is loaded in the ServerManager.
The NotificationAgent status is active and the priority is set to '5'.
When I am testing this agent, I do not get an e-mail from the editor of a document.
What can be the problem ?

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by GB ():
The notification agent is loaded in the ServerManager.
The NotificationAgent status is active and the priority is set to '5'.
When I am testing this agent, I do not get an e-mail from the editor of a document.
What can be the problem ?<HR></BLOCKQUOTE>
-> Must I install the sendmail application ?
null

Similar Messages

Client Notification Agent error

hello,
I've been using client notification to update computer policy for a certain device collection but it is failing to do, the status of the client shows as "offline" when I check the status of the policy update in "Client
Operations" even though the client is online, and has the sccm client installed and active, and I get the following error when I look at CCMNotificationAgent.log file on the client:
<![LOG[Both TCP and http are enabled, let's try TCP connection first.]LOG]!><time="12:59:27.915+420" date="11-01-2014" component="BgbAgent" context="" type="1" thread="3488" file="bgbcontroller.cpp:792">
<![LOG[Connecting to server with IP: 192.168.137.131 Port: 10123
]LOG]!><time="12:59:27.915+420" date="11-01-2014" component="BgbAgent" context="" type="1" thread="3488" file="bgbtcpclient.cpp:699">
<![LOG[Failed to connect to server with IP v4 address with error 10060. Try next IP...
]LOG]!><time="12:59:48.947+420" date="11-01-2014" component="BgbAgent" context="" type="1" thread="3488" file="bgbtcpclient.cpp:703">
<![LOG[Failed to signin bgb client with error = 80004005.]LOG]!><time="12:59:48.947+420" date="11-01-2014" component="BgbAgent" context="" type="3" thread="3488" file="bgbcontroller.cpp:635">
<![LOG[Connecting to server with IP: 192.168.137.131 Port: 10123
]LOG]!><time="13:00:48.951+420" date="11-01-2014" component="BgbAgent" context="" type="1" thread="3488" file="bgbtcpclient.cpp:699">
<![LOG[Failed to connect to server with IP v4 address with error 10060. Try next IP...
]LOG]!><time="13:01:09.979+420" date="11-01-2014" component="BgbAgent" context="" type="1" thread="3488" file="bgbtcpclient.cpp:703">
<![LOG[Failed to signin bgb client with error = 80004005.]LOG]!><time="13:01:09.979+420" date="11-01-2014" component="BgbAgent" context="" type="3" thread="3488" file="bgbcontroller.cpp:635">
<![LOG[Fallback to HTTP connection.]LOG]!><time="13:01:09.979+420" date="11-01-2014" component="BgbAgent" context="" type="1" thread="3488" file="bgbcontroller.cpp:828">
<![LOG[Raising event:
instance of CCM_CcmHttp_Status
ClientID = "GUID:8C18125B-D340-45F9-86AF-C05EA762DDD3";
DateTime = "20141101200109.995000+000";
HostName = "cm01.viamonstra.local";
HRESULT = "0x00000000";
ProcessID = 3728;
StatusCode = 0;
ThreadID = 3488;
]LOG]!><time="13:01:09.995+420" date="11-01-2014" component="BgbAgent" context="" type="1" thread="3488" file="event.cpp:715">
<![LOG[Raising event:
instance of CCM_CcmHttp_Status
ClientID = "GUID:8C18125B-D340-45F9-86AF-C05EA762DDD3";
DateTime = "20141101200111.167000+000";
HostName = "cm01.viamonstra.local";
HRESULT = "0x00000000";
ProcessID = 3728;
StatusCode = 0;
ThreadID = 3488;
]LOG]!><time="13:01:11.167+420" date="11-01-2014" component="BgbAgent" context="" type="1" thread="3488" file="event.cpp:715">
<![LOG[Message validation failure with error = 87d00309.]LOG]!><time="13:01:11.182+420" date="11-01-2014" component="BgbAgent" context="" type="3" thread="3488" file="bgbconnector.cpp:371">
<![LOG[Failed to signin bgb client with error = 87d00309.]LOG]!><time="13:01:11.182+420" date="11-01-2014" component="BgbAgent" context="" type="3" thread="3488" file="bgbcontroller.cpp:635">
I'm using SCCM 2012 R2 CU3, and other clients in other device collections are not having this issue, so I'm assuming it's this one client. I tried to disable firewall completely on the client and even restarted it a couple of times, no luck. Any thoughts?
Thanks,

That's really strange if there's only a single client that's not able to connect to the BGB server on the MP. The 10060 error means that:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Have you verified that the client can actually establish a connection on port 10123? Like with telnet, or a custom PowerShell script?
Here's some more information regarding the error message:
Message : A TCPIP socket error has occurred (10052): The connection has been broken due to the keep-alive activity detecting a failure while the operation was in progress.
Reason : The server closed the client connection.
Have a look at the Troubleshooting section in this blog post:
http://blogs.technet.com/b/configmgrteam/archive/2012/10/11/3522960.aspx
Regards,
Nickolaj Andersen | www.scconfigmgr.com | @Nickolaja

Agent notification on upload

Hi,
i have read the sample code for the notification agent. I want to write an agent that notifies me when a document is uploaded in iFS. Could you tell me what i must write in the agent code?
thanks in advance
loukas

Before we respond, I want to make sure I understand the requirement. Are you asking how to notify...
* On all uploads?
* On uploads to a particular directory?
* On upload of a particular type of file to any directory?
null

Clients Agent no longer installing all components properly

I attempted an upgrade to R2, but it failed, so I reverted back to a VM snapshot before the upgrade attempt and all is well except for installing the client during OSD.
The imaging process works fine, but once complete the agent isn't listing all the Components as installed or enabled:
1) CCM Notification Agent: Disabled
2) Most of the components that should have a status of Enabled are listed as Installed.
On top of that I'm running SP1 CU2 (5.00.7804.1300), but the newly imaged devices list all components as SP1 base (5.00.7804.1000).
I checked the LocationServices.log file on a client and after a few failed attempts to reach my MP it eventually finds the MP and connects using HTTPS (we use a PKI cert).
I reinstalled the MP by deleting the role, waiting, rebooting, adding it back.
What else can I do? I'm thinking I'll try installing CU5.
So in short the client no longer completely installs, which prevents any WSUS updates or Software from being installed post OSD.

I only see errors under 3 components:
SMS_NETWORK_DISCOVERY:
Network Discovery failed to connect to a DHCP server due to a connection error. (Network Discovery can communicate only with Microsoft DHCP servers; if you do not use these servers, you can ignore this error.)
Solution: If you are using Microsoft DHCP servers, then refer to the specific error string for details. This error message means that fewer clients and networks will be found than otherwise. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs.
SMS_MP_CONTROL_MANAGER:
Management Point encountered an error when connecting to the database CM_SITECODE on SQL Server sccmDatabase.domain.local. The OLEDB error code was 0x80004005.
Possible cause: The computer running SQL Server is turned off, not connected to the network, or not functioning properly.
Solution: Verify that the SQL Server is turned on, connected to the network, and functioning properly.
Possible cause: Management point does not have sufficient access rights to the database.
Solution: Verify that management point computer account or the Management Point Database Connection Account is a member of Management Point Role (msdbrole_MP) in the SQL Server database.
Possible cause: Network problems are preventing the management point from properly accessing the SQL Server.
Solution: Investigate and correct any problems with your network.
Possible cause: The management point having problems is at a secondary site, and SQL access account being used was recently reset by the parent site.
Solution: This can automatically repair itself after one hour , as long as the account in use is not locked out. Check that the account in use is not locked out. Instead of waiting an hour, you can stop and start the SMS_SITE_COMPONENT_MANAGER service to immediately apply the new configuration.
Possible cause: The SQL Server Service Principal Names (SPNs) are not registered correctly in Active Directory
Solution: Ensure SQL Server SPNs are correctly registered. Review Q829868.
Then when I attempt the SCCM upgrade I see a lot of USMT and Boot Images fail to upgrade:
Error connecting to WMI while getting remote system drive. Configuration Manager Setup 1/7/2015 4:05:27 PM 5072 (0x13D0)
WARN: Failed to create USMT package instance - ConnectServer failed. Will retry in 10 seconds Configuration Manager Setup 1/7/2015 4:05:27 PM 5072 (0x13D0)
ERROR: Failed to create USMT package instance - ConnectServer failed. Configuration Manager Setup 1/7/2015 4:07:57 PM 5072 (0x13D0)
Error connecting to WMI while getting remote system drive. Configuration Manager Setup 1/7/2015 4:08:58 PM 5072 (0x13D0)
ERROR: Failed to create SMS_BootPackageImage instances - ConnectWmiNamespace failed. Will retry in 10 seconds Configuration Manager Setup 1/7/2015 4:08:58 PM 5072 (0x13D0)
ERROR: Failed to create SMS_BootPackageImage instances - ConnectServer failed Configuration Manager Setup 1/7/2015 4:11:28 PM 5072 (0x13D0)

Skipping request for user policy assignments due to agent configuration for authority

Hello all,
Symptoms:
The Configuration Manager only shows the following actions:
Application Deployment Evaluation Cycle
Machine Policy Retrieval & Evaluation Cycle
Software Updates Deployment Evaluation Cycle
User Policy Retrieval & Evaluation Cycle
In Software Center there are no applications visible. Also the default 'IT Organization' is shown instead of the 'real' name.
The Confugration Manager:
shows in the tab 'General' the correct Management point. Connection type is 'currently intranet' (ok)
shows in the tab 'Site' the correct site code.
shows in the tab 'Components' all components as either 'installed' or 'enabled'. Only CCM Notification Agent shows 'Disabled'.
In SCCM 2012 under 'Client Settings' -> 'Default Settings' -> 'Client Policy' the setting 'Enable User policy on clients' has been enabled.
Done so far (without success):
Re-installed the MP
Run a query on the SCCM Database to check if there are any corrupt records. There are not.
Installed version 5.00.7958.1000
CCM Framework: 5.00.7958.1203
The computer is installed with a task sequence. There is a reboot after 'Setup Windows and ConfigMgr (CM2012 R2 CU1)'.
Installation command of the SCCM Client (during OSD deployment):
SMSCACHEFLAGS=PERCENTDISKSPACE SMSCACHESIZE=10 SMSSLP=demo-sccm.demoforest.local SMSMP=demo-sccm.demoforest.local PATCH="%_SMSTSMDataPath%\OSD\TDS00020\KB2938441\configmgr2012ac-r2-kb2938441-i386.msp"
Content log files on the client:
PolicyAgent.log:
Processing PreShutdown event PolicyAgent_RequestAssignments 8/4/2014 11:56:52 PM 2204 (0x089C)
Processing PostStartup event PolicyAgent_RequestAssignments 8/4/2014 11:57:37 PM 2436 (0x0984)
Policy Download Endpoint's message queue is empty; proceeding with maintenance work PolicyAgent_Cleanup 8/4/2014 11:57:37 PM 2436 (0x0984)
Registered for MP notifications. PolicyAgent_PostStartup 8/4/2014 11:57:37 PM 2436 (0x0984)
Not rerequesting policy on site code change in provisioning mode. PolicyAgent_ReRequestPolicy 8/5/2014 12:01:55 AM 3212 (0x0C8C)
Processing PostStartup event PolicyAgent_RequestAssignments 8/5/2014 12:02:48 AM 2352 (0x0930)
Policy Download Endpoint's message queue is empty; proceeding with maintenance work PolicyAgent_Cleanup 8/5/2014 12:02:48 AM 2352 (0x0930)
Registered for MP notifications. PolicyAgent_PostStartup 8/5/2014 12:02:48 AM 2352 (0x0930)
Processing PostStartup event PolicyAgent_RequestAssignments 8/5/2014 12:11:36 AM 2720 (0x0AA0)
Policy Download Endpoint's message queue is empty; proceeding with maintenance work PolicyAgent_Cleanup 8/5/2014 12:11:36 AM 2720 (0x0AA0)
Registered for MP notifications. PolicyAgent_PostStartup 8/5/2014 12:11:36 AM 2720 (0x0AA0)
Processing PostStartup event PolicyAgent_RequestAssignments 8/5/2014 1:25:02 AM 3164 (0x0C5C)
Policy Download Endpoint's message queue is empty; proceeding with maintenance work PolicyAgent_Cleanup 8/5/2014 1:25:02 AM 3164 (0x0C5C)
Registered for MP notifications. PolicyAgent_PostStartup 8/5/2014 1:25:02 AM 3164 (0x0C5C)
Processing PostStartup event PolicyAgent_RequestAssignments 8/5/2014 1:26:05 AM 2652 (0x0A5C)
Policy Download Endpoint's message queue is empty; proceeding with maintenance work PolicyAgent_Cleanup 8/5/2014 1:26:05 AM 2652 (0x0A5C)
Registered for MP notifications. PolicyAgent_PostStartup 8/5/2014 1:26:05 AM 2652 (0x0A5C)
Triggered update of user S-1-5-21-1840543543-1948091412-3654635223-1109 settings PolicyAgent_RequestAssignments 8/5/2014 9:00:57 AM 3232 (0x0CA0)
Requesting User policy assignments for 'S-1-5-21-1840543543-1948091412-3654635223-1109' PolicyAgent_RequestAssignments 8/5/2014 9:02:34 AM 2484 (0x09B4)
Requesting User policy from authority 'SMS:TDS' PolicyAgent_RequestAssignments 8/5/2014 9:02:34 AM 2484 (0x09B4)
Skipping request for user policy assignments due to agent configuration for authority 'SMS:TDS'. PolicyAgent_RequestAssignments 8/5/2014 9:02:34 AM 2484 (0x09B4)
ClientIDManagerStartup.log:
[----- STARTUP -----] ClientIDManagerStartup 8/5/2014 1:24:34 AM 372 (0x0174)
Read SMBIOS (encoded): 31003800300035002D0030003700310038002D0035003700330038002D0035003500350033002D0034003800350030002D0038003000390030002D0032003800 ClientIDManagerStartup 8/5/2014 1:24:52 AM 2932 (0x0B74)
Evaluated SMBIOS (encoded): 31003800300035002D0030003700310038002D0035003700330038002D0035003500350033002D0034003800350030002D0038003000390030002D0032003800 ClientIDManagerStartup 8/5/2014 1:24:52 AM 2932 (0x0B74)
No SMBIOS Changed ClientIDManagerStartup 8/5/2014 1:24:52 AM 2932 (0x0B74)
SMBIOS unchanged ClientIDManagerStartup 8/5/2014 1:24:52 AM 2932 (0x0B74)
SID unchanged ClientIDManagerStartup 8/5/2014 1:24:52 AM 2932 (0x0B74)
HWID unchanged ClientIDManagerStartup 8/5/2014 1:24:53 AM 2932 (0x0B74)
GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE ClientIDManagerStartup 8/5/2014 1:24:53 AM 2932 (0x0B74)
Windows To Go requires a minimum operating system of Windows 8 ClientIDManagerStartup 8/5/2014 1:24:53 AM 2932 (0x0B74)
Computed HardwareID=2:0760033F87CBB92FC5D6343C630C99002655F937
Win32_SystemEnclosure.SerialNumber=1805-0718-5738-5553-4850-8090-28
Win32_SystemEnclosure.SMBIOSAssetTag=2522-6626-0190-0004-7023-0906-91
Win32_BaseBoard.SerialNumber=1805-0718-5738-5553-4850-8090-28
Win32_BIOS.SerialNumber=1805-0718-5738-5553-4850-8090-28
Win32_NetworkAdapterConfiguration.MACAddress=00:15:5D:00:2A:0C ClientIDManagerStartup 8/5/2014 1:24:53 AM 2932 (0x0B74)
Persisted hardware IDs in CCM_ClientIdentificationInformation=@:
HardwareID1=2:0760033F87CBB92FC5D6343C630C99002655F937
HardwareID2=98130500010000EE ClientIDManagerStartup 8/5/2014 1:24:53 AM 2932 (0x0B74)
Failed to open to WMI namespace '\\.\root\ccmvdi' (8007045b) ClientIDManagerStartup 8/5/2014 1:25:02 AM 372 (0x0174)
[----- SHUTDOWN -----] ClientIDManagerStartup 8/5/2014 1:25:02 AM 372 (0x0174)
[----- STARTUP -----] ClientIDManagerStartup 8/5/2014 1:25:42 AM 2012 (0x07DC)
Read SMBIOS (encoded): 31003800300035002D0030003700310038002D0035003700330038002D0035003500350033002D0034003800350030002D0038003000390030002D0032003800 ClientIDManagerStartup 8/5/2014 1:25:51 AM 2504 (0x09C8)
Evaluated SMBIOS (encoded): 31003800300035002D0030003700310038002D0035003700330038002D0035003500350033002D0034003800350030002D0038003000390030002D0032003800 ClientIDManagerStartup 8/5/2014 1:25:51 AM 2504 (0x09C8)
No SMBIOS Changed ClientIDManagerStartup 8/5/2014 1:25:51 AM 2504 (0x09C8)
SMBIOS unchanged ClientIDManagerStartup 8/5/2014 1:25:51 AM 2504 (0x09C8)
SID unchanged ClientIDManagerStartup 8/5/2014 1:25:51 AM 2504 (0x09C8)
HWID unchanged ClientIDManagerStartup 8/5/2014 1:25:53 AM 2504 (0x09C8)
GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE ClientIDManagerStartup 8/5/2014 1:25:53 AM 2504 (0x09C8)
Windows To Go requires a minimum operating system of Windows 8 ClientIDManagerStartup 8/5/2014 1:25:53 AM 2504 (0x09C8)
Computed HardwareID=2:0760033F87CBB92FC5D6343C630C99002655F937
Win32_SystemEnclosure.SerialNumber=1805-0718-5738-5553-4850-8090-28
Win32_SystemEnclosure.SMBIOSAssetTag=2522-6626-0190-0004-7023-0906-91
Win32_BaseBoard.SerialNumber=1805-0718-5738-5553-4850-8090-28
Win32_BIOS.SerialNumber=1805-0718-5738-5553-4850-8090-28
Win32_NetworkAdapterConfiguration.MACAddress=00:15:5D:00:2A:0C ClientIDManagerStartup 8/5/2014 1:25:53 AM 2504 (0x09C8)
Persisted hardware IDs in CCM_ClientIdentificationInformation=@:
HardwareID1=2:0760033F87CBB92FC5D6343C630C99002655F937
HardwareID2=98C70600010000EE ClientIDManagerStartup 8/5/2014 1:25:53 AM 2504 (0x09C8)
ClientAuth.log:
Error signing client message (0x80004005). ClientAuth 4/22/2014 9:25:01 PM 1612 (0x064C)
Error signing client message (0x80004005). ClientAuth 4/22/2014 9:25:01 PM 1612 (0x064C)
Error signing client message (0x80004005). ClientAuth 4/22/2014 9:25:02 PM 1612 (0x064C)
Error signing client message (0x80004005). ClientAuth 4/22/2014 9:25:02 PM 1612 (0x064C)
ClientLocation.log:
Current AD forest name is demoforest.local, domain name is demoforest.local ClientLocation 8/5/2014 1:24:34 AM 372 (0x0174)
Domain joined client is in Intranet ClientLocation 8/5/2014 1:24:34 AM 372 (0x0174)
Current AD forest name is demoforest.local, domain name is demoforest.local ClientLocation 8/5/2014 1:24:53 AM 2932 (0x0B74)
Domain joined client is in Intranet ClientLocation 8/5/2014 1:24:53 AM 2932 (0x0B74)
Rotating assigned management point, new management point [1] is: DEMO-SCCM.demoforest.local (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities> ClientLocation 8/5/2014
1:24:53 AM 2932 (0x0B74)
Assigned MP changed from <DEMO-SCCM.demoforest.local> to <DEMO-SCCM.demoforest.local>. ClientLocation 8/5/2014 1:24:53 AM 2932 (0x0B74)
Rotating assigned management point, new management point [1] is: DEMO-SCCM.demoforest.local (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities> ClientLocation 8/5/2014
1:24:54 AM 2932 (0x0B74)
Assigned MP changed from <DEMO-SCCM.demoforest.local> to <DEMO-SCCM.demoforest.local>. ClientLocation 8/5/2014 1:24:54 AM 2932 (0x0B74)
Current AD forest name is demoforest.local, domain name is demoforest.local ClientLocation 8/5/2014 1:25:42 AM 2012 (0x07DC)
Domain joined client is in Intranet ClientLocation 8/5/2014 1:25:42 AM 2012 (0x07DC)
Current AD forest name is demoforest.local, domain name is demoforest.local ClientLocation 8/5/2014 1:25:53 AM 2504 (0x09C8)
Domain joined client is in Intranet ClientLocation 8/5/2014 1:25:53 AM 2504 (0x09C8)
Rotating assigned management point, new management point [1] is: DEMO-SCCM.demoforest.local (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities> ClientLocation 8/5/2014
1:25:53 AM 2504 (0x09C8)
Assigned MP changed from <DEMO-SCCM.demoforest.local> to <DEMO-SCCM.demoforest.local>. ClientLocation 8/5/2014 1:25:53 AM 2504 (0x09C8)
Rotating assigned management point, new management point [1] is: DEMO-SCCM.demoforest.local (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities> ClientLocation 8/5/2014
1:25:53 AM 2504 (0x09C8)
Assigned MP changed from <DEMO-SCCM.demoforest.local> to <DEMO-SCCM.demoforest.local>. ClientLocation 8/5/2014 1:25:53 AM 2504 (0x09C8)
Getting Assigned Site ClientLocation 8/5/2014 9:02:38 AM 2264 (0x08D8)
Assigned Site is TDS ClientLocation 8/5/2014 9:02:38 AM 2264 (0x08D8)
Getting Assigned Site ClientLocation 8/5/2014 1:19:20 PM 2604 (0x0A2C)
Assigned Site is TDS ClientLocation 8/5/2014 1:19:20 PM 2604 (0x0A2C)
execmgr.log (with errors):
Requesting MTC to delete task with id: {C5DCEE82-C903-4CBD-98CC-534646B3EFD7} execmgr 4/22/2014 7:14:28 PM 1872 (0x0750)
This execution request does not own the corresponding task in MTC, returning without deleting it from MTC. execmgr 4/22/2014 7:14:28 PM 1872 (0x0750)
Service startup. execmgr 4/22/2014 7:16:09 PM 2332 (0x091C)
Service startup. execmgr 4/22/2014 9:17:36 PM 2216 (0x08A8)
Service startup. execmgr 4/22/2014 9:23:02 PM 2348 (0x092C)
Service startup. execmgr 4/22/2014 9:24:53 PM 1000 (0x03E8)
Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client.
If the client is not yet registered, this is expected behavior. execmgr 8/4/2014 11:56:52 PM 3224 (0x0C98)
Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client.
If the client is not yet registered, this is expected behavior. execmgr 8/4/2014 11:56:52 PM 1292 (0x050C)
Service startup. execmgr 8/4/2014 11:57:32 PM 3696 (0x0E70)
Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client.
If the client is not yet registered, this is expected behavior. execmgr 8/4/2014 11:57:33 PM 3696 (0x0E70)
Software distribution agent was enabled execmgr 8/5/2014 12:01:55 AM 3448 (0x0D78)
Service startup. execmgr 8/5/2014 12:02:44 AM 2272 (0x08E0)
ExecMgr::GetTaskState - GetTaskState Failed with error code 0x87d00317 execmgr 8/5/2014 12:03:02 AM 1652 (0x0674)
Policy arrived for child program Install execmgr 8/5/2014 12:03:02 AM 1648 (0x0670)
Creating mandatory request for advert TDS20014, program Install, package TDS00014 execmgr 8/5/2014 12:03:02 AM 1652 (0x0674)
An existing MTC token was supplied, this execution request is not owner of MTC object. execmgr 8/5/2014 12:03:02 AM 1652 (0x0674)
CertificateMaintanance.log:
HTTP is selected for Client. The current state is 0. CertificateMaintenance 4/22/2014 6:49:04 PM 604 (0x025C)
Raising pending event:
instance of CCM_ServiceHost_CertRetrieval_Status
DateTime = "20140422164904.539000+000";
HRESULT = "0x00000001";
ProcessID = 3320;
ThreadID = 604;
CertificateMaintenance 4/22/2014 6:49:04 PM 604 (0x025C)
Raising event:
instance of CCM_ServiceHost_CertRetrieval_Status
ClientID = "GUID:7ff40832-4c01-456f-9705-096da67985b3";
DateTime = "20140422164946.336000+000";
HRESULT = "0x00000001";
ProcessID = 3320;
ThreadID = 3216;
CertificateMaintenance 4/22/2014 6:49:46 PM 3216 (0x0C90)
HTTP is selected for Client. The current state is 0. CertificateMaintenance 8/4/2014 11:56:39 PM 2212 (0x08A4)
Raising pending event:
instance of CCM_ServiceHost_CertRetrieval_Status
DateTime = "20140804215639.612000+000";
HRESULT = "0x00000001";
ProcessID = 2144;
ThreadID = 2212;
CertificateMaintenance 8/4/2014 11:56:39 PM 2212 (0x08A4)
Raising event:
instance of CCM_ServiceHost_CertRetrieval_Status
ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
DateTime = "20140804215651.440000+000";
HRESULT = "0x00000001";
ProcessID = 2144;
ThreadID = 3348;
CertificateMaintenance 8/4/2014 11:56:51 PM 3348 (0x0D14)
Client is set to use HTTPS when available. The current state is 480. CertificateMaintenance 8/4/2014 11:56:56 PM 1096 (0x0448)
Client is set to use HTTPS when available. The current state is 480. CertificateMaintenance 8/5/2014 12:02:33 AM 1656 (0x0678)
Client is set to use HTTPS when available. The current state is 480. CertificateMaintenance 8/5/2014 12:11:17 AM 384 (0x0180)
Client is set to use HTTPS when available. The current state is 480. CertificateMaintenance 8/5/2014 1:24:34 AM 372 (0x0174)
Client is set to use HTTPS when available. The current state is 480. CertificateMaintenance 8/5/2014 1:25:42 AM 2012 (0x07DC)
smscliui.log:
Perform Action: Request & Evaluate User Policy - {3A88A2F3-0C39-45fa-8959-81F21BF500CE}. Message sent, id={FC736B58-2635-45B8-8002-E7C8D6CCEB8D} smscliui 8/5/2014 9:02:34 AM 2484 (0x09B4)
Current Assigned Site: TDS smscliui 8/5/2014 9:02:38 AM 868 (0x0364)
Currently assigned FQDN: smscliui 8/5/2014 9:02:41 AM 868 (0x0364)
Failed to set DNSSuffix value to the registry. smscliui 8/5/2014 9:02:58 AM 868 (0x0364)
SMS Site code has not been changed. smscliui 8/5/2014 9:02:58 AM 868 (0x0364)
Current Assigned Site: TDS smscliui 8/5/2014 1:19:20 PM 2160 (0x0870)
CcmMessaging.log:
Queue 'StateMessageManager' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'StateMessageManager'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'CTMDTSReply'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'CTMDTSReply' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'CTMDTSReply'. Enabled=true Concurrency=5 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'execmgr'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'execmgr' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'execmgr'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'PolicyAgent_RequestAssignments'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'PolicyAgent_RequestAssignments' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'PolicyAgent_RequestAssignments'. Enabled=true Concurrency=5 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'ClientRegistration'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'ClientRegistration' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'ClientRegistration'. Enabled=true Concurrency=5 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'EndpointProtectionAgent'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'EndpointProtectionAgent' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'EndpointProtectionAgent'. Enabled=true Concurrency=20 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'LS_ScheduledCleanup'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'LS_ScheduledCleanup' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'LS_ScheduledCleanup'. Enabled=true Concurrency=5 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'PolicyAgent_Cleanup'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'PolicyAgent_Cleanup' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'PolicyAgent_Cleanup'. Enabled=true Concurrency=5 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'DCMAgent'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'DCMAgent' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'DCMAgent'. Enabled=true Concurrency=5 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'CertEnrollAgent'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'CertEnrollAgent' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'CertEnrollAgent'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'ExternalEventAgent'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'ExternalEventAgent' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'ExternalEventAgent'. Enabled=true Concurrency=20 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'UpdateStore'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'UpdateStore' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'UpdateStore'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'PolicyAgent_ReplyAssignments'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'PolicyAgent_ReplyAssignments' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'PolicyAgent_ReplyAssignments'. Enabled=true Concurrency=5 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'SMSSHA'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'SMSSHA' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'SMSSHA'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'lmp_[http]mp_locationmanager'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'lmp_[http]mp_locationmanager' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'lmp_[http]mp_locationmanager'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'mp_statusreceiver'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'mp_statusreceiver' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'mp_statusreceiver'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initializing queue 'mp_[http]mp_locationmanager'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Queue 'mp_[http]mp_locationmanager' initialized with 1 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Initialized queue processor 'mp_[http]mp_locationmanager'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
Raising event:
instance of CCM_CcmHttp_Status
ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
DateTime = "20140804232553.423000+000";
HostName = "DEMO-SCCM.demoforest.local";
HRESULT = "0x00000000";
ProcessID = 1996;
StatusCode = 0;
ThreadID = 2504;
CcmMessaging 8/5/2014 1:25:53 AM 2504 (0x09C8)
Raising event:
instance of CCM_CcmHttp_Status
ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
DateTime = "20140804232553.485000+000";
HostName = "DEMO-SCCM.demoforest.local";
HRESULT = "0x00000000";
ProcessID = 1996;
StatusCode = 0;
ThreadID = 2504;
CcmMessaging 8/5/2014 1:25:53 AM 2504 (0x09C8)
Raising event:
instance of CCM_CcmHttp_Status
ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
DateTime = "20140804232553.563000+000";
HostName = "DEMO-SCCM.demoforest.local";
HRESULT = "0x00000000";
ProcessID = 1996;
StatusCode = 0;
ThreadID = 2504;
CcmMessaging 8/5/2014 1:25:53 AM 2504 (0x09C8)
Raising event:
instance of CCM_CcmHttp_Status
ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
DateTime = "20140804232553.657000+000";
HostName = "DEMO-SCCM.demoforest.local";
HRESULT = "0x00000000";
ProcessID = 1996;
StatusCode = 0;
ThreadID = 2504;
CcmMessaging 8/5/2014 1:25:53 AM 2504 (0x09C8)
Raising event:
instance of CCM_CcmHttp_Status
ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
DateTime = "20140804232606.048000+000";
HostName = "DEMO-SCCM.demoforest.local";
HRESULT = "0x00000000";
ProcessID = 1996;
StatusCode = 0;
ThreadID = 2508;
CcmMessaging 8/5/2014 1:26:06 AM 2508 (0x09CC)
Raising event:
instance of CCM_CcmHttp_Status
ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
DateTime = "20140804232606.110000+000";
HostName = "DEMO-SCCM.demoforest.local";
HRESULT = "0x00000000";
ProcessID = 1996;
StatusCode = 0;
ThreadID = 2188;
CcmMessaging 8/5/2014 1:26:06 AM 2188 (0x088C)
Raising event:
instance of CCM_CcmHttp_Status
ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
DateTime = "20140804232606.188000+000";
HostName = "DEMO-SCCM.demoforest.local";
HRESULT = "0x00000000";
ProcessID = 1996;
StatusCode = 0;
ThreadID = 2504;
CcmMessaging 8/5/2014 1:26:06 AM 2504 (0x09C8)
CcmNotificationAgent.log:
Bgb client agent is starting... BgbAgent 8/5/2014 1:26:05 AM 2504 (0x09C8)
Bgb client agent is disabled BgbAgent 8/5/2014 1:26:05 AM 2504 (0x09C8)
TCP Listener is disabled. BgbAgent 8/5/2014 1:26:05 AM 2504 (0x09C8)
BgbController main thread is started with settings: {bgb enable = 0}, {tcp enabled = 0}, {tcp port = 0} and {http enabled = 0}. BgbAgent 8/5/2014 1:26:05 AM 2504 (0x09C8)
Wait 3600 seconds for event notification. BgbAgent 8/5/2014 1:26:05 AM 3076 (0x0C04)
Wait 3600 seconds for event notification. BgbAgent 8/5/2014 2:26:05 AM 3076 (0x0C04)
Any help is appreciated and with kind regards,
Willem-Jan

Hello all,
I modified the TS, but the problem is still there.
smsts.log:
==============================[ OSDSetupHook.exe ]============================== OSDSetupHook 8/5/2014 4:51:30 PM 856 (0x0358)
Executing task sequence OSDSetupHook 8/5/2014 4:51:30 PM 856 (0x0358)
Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat". OSDSetupHook 8/5/2014 4:51:30 PM 856 (0x0358)
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912} OSDSetupHook 8/5/2014 4:51:30 PM 856 (0x0358)
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03} OSDSetupHook 8/5/2014 4:51:30 PM 856 (0x0358)
Debug shell is enabled OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
Successfully enabled debug command shell support. OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
Configuring local administrator account OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
Re-assign all drive letters... OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
Could not open drive Q:\ (80070005) OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
Ignoring inaccessible volume 'Q:' with error 0x80070005 OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
No partition needs to be udpated. OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
Installing SMS client OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
Client already installed. OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
Moving logs to SMS client directory OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
Successfully moved logs to SMS client log directory: C:\Windows\CCM\Logs\SMSTSLog OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
Executing task sequence manager bootstrap OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
Executing command line: "C:\Windows\CCM\TSMBootstrap.exe" /env:Gina /configpath:C:\_SMSTaskSequence /bootcount:5 OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
Command line: "C:\Windows\CCM\TSMBootstrap.exe" /env:Gina /configpath:C:\_SMSTaskSequence /bootcount:5 TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
Current OS version is 6.1.7601.1 TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
Logging successfully initialized. TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
Resuming Task Sequence in Full OS TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
We are going in GINA and potentially need to set the authenticator TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
setting the authenticator TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
Executing command line: "C:\Windows\CCM\TsProgressUI.exe" /Register:WinPE TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
==========[ TsProgressUI started in process 2196 ]========== TsProgressUI 8/5/2014 4:51:39 PM 2200 (0x0898)
Command line: "C:\Windows\CCM\TsProgressUI.exe" /Register:WinPE TsProgressUI 8/5/2014 4:51:39 PM 2200 (0x0898)
Registering COM classes TsProgressUI 8/5/2014 4:51:39 PM 2200 (0x0898)
sbModulePath = C:\Windows\CCM\TsProgressUI.exe TsProgressUI 8/5/2014 4:51:39 PM 2200 (0x0898)
Unregistering class objects TsProgressUI 8/5/2014 4:51:39 PM 2200 (0x0898)
Shutdown complete. TsProgressUI 8/5/2014 4:51:39 PM 2200 (0x0898)
Process completed with exit code 0 TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
Successfully registered TS Progress UI. TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
Found network adapter "Intel 21140-Based PCI Fast Ethernet Adapter (Emulated)" with IP Address 5.5.5.101. TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
Starting Task Sequence Manager. TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
executing TS Manager not in full media TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
executing TS Manager in c:\windows\ccm TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
Executing command line: "TsManager.exe" TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
Successfully intialized Logging for TS Manager. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Commandline: "TsManager.exe" TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
/service parameter found at index: -1 TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
/standalone parameter found at index: -1 TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
/noclient parameter found at index: -1 TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Successfully registered Task Sequencing COM Interface. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Executing as a standalone exe TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Initializing TS Environment TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Opening Task Sequencing Environment TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
pwszPath && *pwszPath, HRESULT=80070057 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,228) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
pwszPath && *pwszPath, HRESULT=80070057 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,228) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
pwszPath && *pwszPath, HRESULT=80070057 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,228) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
pwszPath && *pwszPath, HRESULT=80070057 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,228) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
NOT executing in WinPE TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Compiling Config policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Compiling config policies... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Compiling SysHealthConfig policy... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Retrieving value from TSEnv for '_SMSTSSysHealthClientConfig' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
::DecompressBuffer(65536) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Decompression (zlib) succeeded: original size 684, uncompressed size 4652. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Instance path = 'CCM_SystemHealthClientConfig.SiteSettingsKey="1"' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Compiling SoftUpdConfig policy... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Retrieving value from TSEnv for '_SMSTSSWUpdateClientConfig' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
::DecompressBuffer(65536) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Decompression (zlib) succeeded: original size 1922, uncompressed size 19242. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Instance path = 'CCM_SoftwareUpdatesClientConfig.SiteSettingsKey="1"' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Compiling SoftDistClientConfig policy... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Retrieving value from TSEnv for '_SMSTSSoftDistClientConfig' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
::DecompressBuffer(65536) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Decompression (zlib) succeeded: original size 1327, uncompressed size 13740. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Instance path = 'CCM_SoftwareDistributionClientConfig.SiteSettingsKey="1"' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Compiling NAAConfig policy... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Retrieving value from TSEnv for '_SMSTSNAAConfigPolicy' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
::DecompressBuffer(65536) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Decompression (zlib) succeeded: original size 1022, uncompressed size 6494. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Instance path = 'CCM_NetworkAccessAccount.SiteSettingsKey="1"' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Instance path = 'CCM_NetworkAccessAccount.SiteSettingsKey="1"' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Compiling RebootSettingsConfig policy... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Retrieving value from TSEnv for '_SMSTSRebootSettingsConfigPolicy' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
::DecompressBuffer(65536) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Decompression (zlib) succeeded: original size 433, uncompressed size 1556. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Instance path = 'CCM_RebootSettings.SiteSettingsKey="1"' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Compiling AppManClientConfig policy... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Retrieving value from TSEnv for '_SMSTSAppManClientConfigPolicy' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
::DecompressBuffer(65536) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Decompression (zlib) succeeded: original size 982, uncompressed size 6358. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Instance path = 'CCM_ApplicationManagementClientConfig.SiteSettingsKey="1"' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Failed to find property 'AutoApplyDeployment' in 'CCM_ApplicationManagementClientConfig' class defintion. Error 0x80041002. Default value will be used for this property TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Get Install Directory for SMS Client TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
Updating settings in \\.\root\ccm\policy\machine\actualconfig TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
RequestedConfig policy instance(s) : 435 TSManager 8/5/2014 4:51:49 PM 2244 (0x08C4)
Locked \\.\ROOT\ccm\policy\machine\RequestedConfig for source SMS:Client:Default:{BFDADC41-FDCD-4B9C-B446-8A818D01BEA3} successfully TSManager 8/5/2014 4:51:49 PM 2244 (0x08C4)
Namespace: \\.\ROOT\ccm\policy\machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "SMS:Client:Default:{BFDADC41-FDCD-4B9C-B446-8A818D01BEA3}") AND (PolicyState
= "Active") AND (PolicyType = "Machine") TSManager 8/5/2014 4:51:49 PM 2244 (0x08C4)
There is no ccm_policy_policy instance, skipping addition to realinst map TSManager 8/5/2014 4:51:49 PM 2244 (0x08C4)
Unlocked \\.\ROOT\ccm\policy\machine\RequestedConfig for source SMS:Client:Default:{BFDADC41-FDCD-4B9C-B446-8A818D01BEA3} successfully TSManager 8/5/2014 4:51:49 PM 2244 (0x08C4)
RequestedConfig policy instance(s) : 0 TSManager 8/5/2014 4:51:50 PM 2244 (0x08C4)
Locked \\.\ROOT\ccm\policy\machine\RequestedConfig for source SMS:TDS successfully TSManager 8/5/2014 4:51:50 PM 2244 (0x08C4)
Namespace: \\.\ROOT\ccm\policy\machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "SMS:TDS") AND (PolicyState = "Active") AND (PolicyType = "Machine") TSManager 8/5/2014
4:51:50 PM 2244 (0x08C4)
There is no ccm_policy_policy instance, skipping addition to realinst map TSManager 8/5/2014 4:51:50 PM 2244 (0x08C4)
Unlocked \\.\ROOT\ccm\policy\machine\RequestedConfig for source SMS:TDS successfully TSManager 8/5/2014 4:51:50 PM 2244 (0x08C4)
RequestedConfig policy instance(s) : 0 TSManager 8/5/2014 4:51:51 PM 2244 (0x08C4)
Locked \\.\ROOT\ccm\policy\machine\RequestedConfig for source CcmPortal successfully TSManager 8/5/2014 4:51:51 PM 2244 (0x08C4)
Namespace: \\.\ROOT\ccm\policy\machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "CcmPortal") AND (PolicyState = "Active") AND (PolicyType = "Machine") TSManager 8/5/2014
4:51:51 PM 2244 (0x08C4)
There is no ccm_policy_policy instance, skipping addition to realinst map TSManager 8/5/2014 4:51:51 PM 2244 (0x08C4)
Unlocked \\.\ROOT\ccm\policy\machine\RequestedConfig for source CcmPortal successfully TSManager 8/5/2014 4:51:51 PM 2244 (0x08C4)
RequestedConfig policy instance(s) : 0 TSManager 8/5/2014 4:51:53 PM 2244 (0x08C4)
Locked \\.\ROOT\ccm\policy\machine\RequestedConfig for source Local successfully TSManager 8/5/2014 4:51:53 PM 2244 (0x08C4)
RequestedConfig policy instance(s) : 9 TSManager 8/5/2014 4:51:53 PM 2244 (0x08C4)
Unlocked \\.\ROOT\ccm\policy\machine\RequestedConfig for source Local successfully TSManager 8/5/2014 4:51:53 PM 2244 (0x08C4)
RequestedConfig policy instance(s) : 11943 TSManager 8/5/2014 4:51:57 PM 2244 (0x08C4)
Locked \\.\ROOT\ccm\policy\machine\RequestedConfig for source CcmTaskSequence successfully TSManager 8/5/2014 4:51:57 PM 2244 (0x08C4)
Namespace: \\.\ROOT\ccm\policy\machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "CcmTaskSequence") AND (PolicyState = "Active") AND (PolicyType = "Machine") TSManager 8/5/2014
4:51:57 PM 2244 (0x08C4)
There is no ccm_policy_policy instance, skipping addition to realinst map TSManager 8/5/2014 4:51:57 PM 2244 (0x08C4)
Unlocked \\.\ROOT\ccm\policy\machine\RequestedConfig for source CcmTaskSequence successfully TSManager 8/5/2014 4:51:57 PM 2244 (0x08C4)
Total RequestedConfig policy instance(s) : 12387 TSManager 8/5/2014 4:52:00 PM 2244 (0x08C4)
New/Changed ActualConfig policy instance(s) : 0 TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
Policy evaluation initiated TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
Waiting for policy to be compiled in 'root\ccm\policy\machine' namespace TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
Query = 'CCM_SystemHealthClientConfig.SiteSettingsKey="1"' TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
Verified policy for instance path 'CCM_SystemHealthClientConfig.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
Query = 'CCM_SoftwareUpdatesClientConfig.SiteSettingsKey="1"' TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
Verified policy for instance path 'CCM_SoftwareUpdatesClientConfig.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
Query = 'CCM_SoftwareDistributionClientConfig.SiteSettingsKey="1"' TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
Verified policy for instance path 'CCM_SoftwareDistributionClientConfig.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine'
The Powershell command as described by NPerson give the output:
C:\Windows\system32>powershell Invoke-WmiMethod -Namespace root\CCM -Class SMS_C
lient -Name SetClientProvisioningMode -ArgumentList $false
__GENUS          : 1
__CLASS          : __PARAMETERS
__SUPERCLASS     :
__DYNASTY        : __PARAMETERS
__RELPATH        : __PARAMETERS
__PROPERTY_COUNT : 1
__DERIVATION     : {}
__SERVER         : DEMO-CAPTURE
__NAMESPACE      : ROOT\ccm
__PATH           :
\\DEMO-CAPTURE\ROOT\ccm:__PARAMETERS
ReturnValue      :
PSComputerName   : DEMO-CAPTURE
It is about the PSComputerName: that is the name of the machine on which the capture was made. So I suppose the problem is already in the image. Is my statement correct or is it not relevant?
With kind regards,
Willem-Jan

Email notifications stuck in Mail status

Hi,
The notification mailer is up and running and we receive emails when we run the test. However, when a user goes through the application, lets say the Purchase requisition process, the process completes successfully, we see the notification in his worklist, we see the notification in the wf_notifications table with status of MAIL, but the user does not get the email notification. The email address is defined both on the employee record and on the user record. The background process is running but it doesn't pick up the notification. After a while the notification gets expired.
does anyone have any clue as to why the test notification from the mailer works but we don't get an email when we go thru the requisition process although it completes successfully ?
Any help is appreciated.
Regards
Preeti

There are various aspects to troubleshooting this issue.
Let me explain the mailer architecture in a nutshell and then troubleshooting tips.
1. Notification activity in a workflow process is executed by the engine. The activity makes an entry in WF_NOTIFICATIONS table with appropriate values for RECIPIENT_ROLE, SUBJECT and MAIL_STATUS based on recipient's notification preference.
2. At the same time, an business event is raised for that notification and enqueued on to the WF_DEFERRED queue.
3. The Workflow Deferred Agent Listener dequeues the event, builds a XML message for that notification and enqueues it again to WF_NOTIFICATION_OUT queue.
4. Workflow Notification Mailer polls the WF_NOTIFICATION_OUT queue and when a message arrives, it dequeues it, parses the XML for that notification and builds a MIME message. Sends the MIME message to the intended recipient_role's e-mail address.
In summary the message for e-mail goes like this...
Ntf Activity -> WF_DEFERRED -> WF_NOTIFICATION_OUT -> Notification Mailer Now things to check.
1. Is the Deferred Agent Listener or Deferred Notification Agent Listener running?
2. Is the Notification Mailer running with Correlation ID parameter set to null? Because the mailer could be configured to only process e-mail notifications from a specific Item Type.
3. Is the intended RECIPIENT_ROLE's e-mail address and notification_preference values in WF_ROLES view correct? The email address should be valid and notification preference should be MAIL%.
There is a debug script $FND_TOP/sql/wfmlrdbg.sql. Run this for the given notification id and you will be able to see in which queue the message is stuck.
Hope this helps.

How to find through back end workflow Agent Listener is runnning or not

Hi all,
How to find through backend workflow Agent Listener is runnning or not.
Thanks

Reddy,
Simple way to find if it is running or not can be done by below
SQL> select COMPONENT_NAME,COMPONENT_STATUS from fnd_svc_components;
COMPONENT_NAME COMPONENT_STATUS
ECX Inbound Agent Listener STOPPED
ECX Transaction Agent Listener STOPPED
Workflow Deferred Agent Listener DEACTIVATED_SYSTEM
Workflow Deferred Notification Agent Listener DEACTIVATED_SYSTEM
Workflow Error Agent Listener RUNNING
Workflow Inbound Notifications Agent Listener RUNNING
Workflow Notification Mailer DEACTIVATED_SYSTEM
Thanks,
baskar.l

WORKFLOW AGENT LISTENER SERVICE 기동되지 않을때

제품 : AOL
작성날짜 : 2005-11-28
WORKFLOW AGENT LISTENER SERVICE 기동되지 않을때
========================================
PURPOSE
신규설치 및 Clonning후 WORKFLOW AGENT LISTENER SERVICE 기동되지 않을때가 있습니다. 이에 대한 조치사항을 기술하고 있습니다.
Problem Description
증상
1. Workflow Agent Listener Service 와 Workflow Mailer Service 기동되지 않습니다.
2. 기동될때 "Activating" status 로 남아 있습니다.
3. 위와 같은 증상은 아래와 같은 원인에 발생할수 있습니다.
(a) The WF_JMS_IN 와 WF_JMS_OUT queues 가 invalid 일때
(b) 아래 workflow listeners 와 mailer 들이 'STOPPED_ERROR' status일때
Workflow Deferred Agent Listener
Workflow Deferred Notification Agent Listener
Workflow Error Agent Listener
Workflow Inbound Notifications Agent Listener
Workflow Notification Mailer
(c) Af_CLASSPATH 가 JDK 1.3.1을 가리키지 않을때
Solution Description
이런 증상이 발견될경우 아래와 같은 조치를 취해주세요.
1. missing/corrupt queues 가 있는지 확인하고 이를 재성성 해주세요.
sqlplus apps/apps @$FND_TOP/patch/115/sql/wfjmsqc.sql applsys apps
위 sql이 먹지 않을때
다음 command들을 copy/paste해서 작업해주세요(APPLSYS user로 하셔야 합니다.)
Exec dbms_aqadm.stop_queue( queue_name => ' WF_JMS_IN', wait => FALSE);
Exec dbms_aqadm.drop_queue(queue_name=> ' WF_JMS_IN');
exec dbms_aqadm.drop_queue_table( queue_table => ' WF_JMS_IN', force => TRUE);
Exec dbms_aqadm.stop_queue( queue_name => ' WF_JMS_OUT', wait => FALSE);
Exec dbms_aqadm.drop_queue(queue_name=> ' WF_JMS_OUT');
exec dbms_aqadm.drop_queue_table( queue_table => ' WF_JMS_OUT', force => TRUE);
위 queue들이 drop되면 아래 sql을 다시 실행해 주세요.
sqlplus apps/apps @$FND_TOP/patch/115/sql/wfjmsqc.sql applsys apps
그리고 확인차 wfver.sql를 돌려주세요.
(Note: The file wfjmsqc.sql has been replaced in 9.2.0.4 with wfjmsqc2.sql.)
2. 11.5. 7 이전 버전은 JDK 1.3을 CM node에 설치해야 하고 patch 2356331 를 적용해야 합니다.
Please reference:
Note:242941.1 (How To Troubleshoot Java-based Workflow Notification Mailer In 11.5.9 and OWF.G)
Note:130091.1 (Upgrading Oracle Applications 11i to use JDK 1.3)
3. 환경변수 AF_JRE_TOP, AF_CLASSPATH, and AFJVAPRG 가 $APPL_TOP/admin/adovars.env에 제대로 설정되었는지 확인해 주세요. 그리고 이들이 JDK 1.3.1을 가리키고 있는지 확인해 주세요.
Reference Documents
Note 278428.1

제품 : AOL
작성날짜 : 2005-11-28
WORKFLOW AGENT LISTENER SERVICE 기동되지 않을때
========================================
PURPOSE
신규설치 및 Clonning후 WORKFLOW AGENT LISTENER SERVICE 기동되지 않을때가 있습니다. 이에 대한 조치사항을 기술하고 있습니다.
Problem Description
증상
1. Workflow Agent Listener Service 와 Workflow Mailer Service 기동되지 않습니다.
2. 기동될때 "Activating" status 로 남아 있습니다.
3. 위와 같은 증상은 아래와 같은 원인에 발생할수 있습니다.
(a) The WF_JMS_IN 와 WF_JMS_OUT queues 가 invalid 일때
(b) 아래 workflow listeners 와 mailer 들이 'STOPPED_ERROR' status일때
Workflow Deferred Agent Listener
Workflow Deferred Notification Agent Listener
Workflow Error Agent Listener
Workflow Inbound Notifications Agent Listener
Workflow Notification Mailer
(c) Af_CLASSPATH 가 JDK 1.3.1을 가리키지 않을때
Solution Description
이런 증상이 발견될경우 아래와 같은 조치를 취해주세요.
1. missing/corrupt queues 가 있는지 확인하고 이를 재성성 해주세요.
sqlplus apps/apps @$FND_TOP/patch/115/sql/wfjmsqc.sql applsys apps
위 sql이 먹지 않을때
다음 command들을 copy/paste해서 작업해주세요(APPLSYS user로 하셔야 합니다.)
Exec dbms_aqadm.stop_queue( queue_name => ' WF_JMS_IN', wait => FALSE);
Exec dbms_aqadm.drop_queue(queue_name=> ' WF_JMS_IN');
exec dbms_aqadm.drop_queue_table( queue_table => ' WF_JMS_IN', force => TRUE);
Exec dbms_aqadm.stop_queue( queue_name => ' WF_JMS_OUT', wait => FALSE);
Exec dbms_aqadm.drop_queue(queue_name=> ' WF_JMS_OUT');
exec dbms_aqadm.drop_queue_table( queue_table => ' WF_JMS_OUT', force => TRUE);
위 queue들이 drop되면 아래 sql을 다시 실행해 주세요.
sqlplus apps/apps @$FND_TOP/patch/115/sql/wfjmsqc.sql applsys apps
그리고 확인차 wfver.sql를 돌려주세요.
(Note: The file wfjmsqc.sql has been replaced in 9.2.0.4 with wfjmsqc2.sql.)
2. 11.5. 7 이전 버전은 JDK 1.3을 CM node에 설치해야 하고 patch 2356331 를 적용해야 합니다.
Please reference:
Note:242941.1 (How To Troubleshoot Java-based Workflow Notification Mailer In 11.5.9 and OWF.G)
Note:130091.1 (Upgrading Oracle Applications 11i to use JDK 1.3)
3. 환경변수 AF_JRE_TOP, AF_CLASSPATH, and AFJVAPRG 가 $APPL_TOP/admin/adovars.env에 제대로 설정되었는지 확인해 주세요. 그리고 이들이 JDK 1.3.1을 가리키고 있는지 확인해 주세요.
Reference Documents
Note 278428.1

Error in notification mail in po release

Hi all,
         i encounter a problem in notification mail activity. actually my wflow gets trigerred wen a po is created. It has four levels of approval, in the activity i have given the notification agent as the po creator the wen the first approver releases the po and saves the workitem status is set to be inprocess itself it doesnt get the status as completed.but the po reaches the second approvers inbox and he also effects the release but there also the workitem status is set to inprocess .
            like wise it happens with the remaining users but the document is released but the notification is not sent to the po creator.
           When i view the technical details of that workitem there is an error stating
Terminating event recieved : notification of completion cannot be generated
problems occures during generation of mail
if_swf_utl_mail~send   error 9 when calling service so_object_send
please do help me with this error.

Please check whether there is any terminating event that is triggered inside the Workflow. U can check through wflow Log. You can also check whether the User Id to whom you are sending the mail if it is SAP User Id and you are using Container element in agent determination to be always Concatenated with US for SAP User Id.
<b>Reward points if useful</b>

Workflow Deferred Agent Listener IMPACTS on EBS

What is the impact of Workflow Deferred Agent Listener on Notification mailer , if it is down.
Just want to tell you , when I bring down both the listeners (Workflow Deferred Agent Listener and Workflow Deferred Notification Agent Listener manually) , No Notifications (mails) are going.
If I brought up any of the listener , mails are going . So basically what is the difference ? and what is impact on the system .
Workflow Deferred Agent Listener - Handles messages on WF_DEFERRED to support deferred subscription processing. This service component is started automatically by its container.
Workflow Deferred Notification Agent Listener - Handles notification messages on WF_DEFERRED to support outbound notification processing. This service component is started automatically by its container.
Note able to understand above definitions.
What is meant by deferred subscription processing ?

In one of my project, I have noticed that whenever Workflow Deferred Agent Listener goes down , User Start Complaining about that there transactions( related to GL) are not appearing whenever they are checking in EBS(12.0.6) and DB (10.2.0.4). OS : RHEL 5.2
Even I have noticed that when I bring down both Workflow Deferred Agent Listener and Workflow Deferred Notification Agent Listener , even the test mails are not going. If any of the component is up mails are going. As I mentioned above Workflow Deferred Listener "support deferred subscription processing" , what is mean by this. What are business system events ?Please see (How to Manually Process the Events from Workflow Queues When The Deferred Agent Listener Won't Start [ID 953103.1]).
Thanks,
Hussein

Client Notification Issue

Hoping someone can point me in the right direction here.
Infrastructure:
SCCM 2012 R2 CU1:
Single Primary Site Server (Server 2012 R2 Update), With MP Role
Remote SQL 2012 Server (Server 2012 R2 Update)
Second Standalone MP (Server 2012 R2 Update)
HTTPS with PKI Certificate deployed for DP and MP roles
We have been testing client rollout to pilot machine over the past couple of weeks and everything (appears) to be working fine. OSD, Application deployments, etc. all working as expected.
The default ports for Client communication are select (80/443 and 10123)
Client Notification is not working however. I can go through the motions to create a "Download Machine Policy" notification, but the policy doesn't make it to the machine and all status messages for the notification stay at "unknown".
*Side note, the online tests to keep the client active appears to be working fine.
The BGBSetup logs show successful installation for both servers.
I get lots of messages similar to this in the BGBServer.log (on both MP's):
ERROR: Client ID is not 41 length. 8478e00c-d07b-4d93-b0f4-e01f4c78cc3b
SMS_NOTIFICATION_SERVER 6/27/2014 1:50:02 PM
4000 (0x0FA0)
ERROR: Client ID is not 41 length. 8478e00c-d07b-4d93-b0f4-e01f4c78cc3b
SMS_NOTIFICATION_SERVER 6/27/2014 1:50:02 PM
4000 (0x0FA0)
ERROR: Client ID is not 41 length. 8478e00c-d07b-4d93-b0f4-e01f4c78cc3b
SMS_NOTIFICATION_SERVER 6/27/2014 1:50:02 PM
4000 (0x0FA0)
ERROR: The message body is invalid. <BgbSignInMessage TimeStamp="2014-06-27T18:50:02Z"><ClientType>SCCM</ClientType><ClientVersion>5.00.7958.1203</ClientVersion><ClientID>8478e00c-d07b-4d93-b0f4-e01f4c78cc3b</ClientID></BgbSignInMessage>
SMS_NOTIFICATION_SERVER 6/27/2014 1:50:02 PM
4000 (0x0FA0)
ERROR: The message body is invalid. <BgbSignInMessage TimeStamp="2014-06-27T18:50:02Z"><ClientType>SCCM</ClientType><ClientVersion>5.00.7958.1203</ClientVersion><ClientID>8478e00c-d07b-4d93-b0f4-e01f4c78cc3b</ClientID></BgbSignInMessage>
SMS_NOTIFICATION_SERVER 6/27/2014 1:50:02 PM
4000 (0x0FA0)
ERROR: The message body is invalid. <BgbSignInMessage TimeStamp="2014-06-27T18:50:02Z"><ClientType>SCCM</ClientType><ClientVersion>5.00.7958.1203</ClientVersion><ClientID>8478e00c-d07b-4d93-b0f4-e01f4c78cc3b</ClientID></BgbSignInMessage>
SMS_NOTIFICATION_SERVER 6/27/2014 1:50:02 PM
4000 (0x0FA0)
Failed to process SignIn message from client [::ffff:10.100.122.71]:56195.
SMS_NOTIFICATION_SERVER 6/27/2014 1:50:02 PM
4000 (0x0FA0)
Failed to process SignIn message from client [::ffff:10.100.122.71]:56195.
SMS_NOTIFICATION_SERVER 6/27/2014 1:50:02 PM
4000 (0x0FA0)
Failed to process SignIn message from client [::ffff:10.100.122.71]:56195.
SMS_NOTIFICATION_SERVER 6/27/2014 1:50:02 PM
4000 (0x0FA0)
BGBmgr.log shows no errors:
Begin to handle file Bgbi1v41.BOS SMS_NOTIFICATION_MANAGER
6/27/2014 2:00:26 PM 6892 (0x1AEC)
Begin to process file C:\Program Files\Microsoft Configuration Manager\inboxes\bgb.box\Bgbi1v41.BOS
SMS_NOTIFICATION_MANAGER 6/27/2014 2:00:26 PM
6892 (0x1AEC)
Server Name: MP.DOMAIN.COM, Version: 704
SMS_NOTIFICATION_MANAGER 6/27/2014 2:00:26 PM
6892 (0x1AEC)
No records need to be BCPed SMS_NOTIFICATION_MANAGER
6/27/2014 2:00:26 PM 6892 (0x1AEC)
Successfully processed file C:\Program Files\Microsoft Configuration Manager\inboxes\bgb.box\Bgbi1v41.BOS
SMS_NOTIFICATION_MANAGER 6/27/2014 2:00:26 PM
6892 (0x1AEC)
Successfully processed file Bgbi1v41.BOS, clean it.
SMS_NOTIFICATION_MANAGER 6/27/2014 2:00:26 PM
6892 (0x1AEC)
BgbManager is waiting for file and registry change notification or timeout after 60 seconds
SMS_NOTIFICATION_MANAGER 6/27/2014 2:00:26 PM
6892 (0x1AEC)
CcmNotificationAgent.log on a client:
Access point is MP.DOMAIN.COM. (SSLEnabled = 0)
BgbAgent 6/27/2014 12:52:29 PM
5544 (0x15A8)
CRL Checking is Enabled. BgbAgent
6/27/2014 12:52:29 PM 5544 (0x15A8)
Both TCP and http are enabled, let's try TCP connection first.
BgbAgent 6/27/2014 12:52:29 PM
5544 (0x15A8)
Connecting to server with IP: 10.32.8.135 Port: 10123
BgbAgent
6/27/2014 12:52:29 PM 5544 (0x15A8)
Handshake was successful
BgbAgent
6/27/2014 12:52:29 PM 5544 (0x15A8)
Pass verification on server certificate.
BgbAgent 6/27/2014 12:52:29 PM
5544 (0x15A8)
Update the timeout to 900 second(s)
BgbAgent 6/27/2014 12:52:29 PM
5544 (0x15A8)
Receive signin confirmation message from server, client is signed in.
BgbAgent 6/27/2014 12:52:31 PM
5544 (0x15A8)
Successfully sent keep-alive message.
BgbAgent 6/27/2014 1:07:32 PM
5544 (0x15A8)
Successfully sent keep-alive message.
BgbAgent 6/27/2014 1:22:33 PM
5544 (0x15A8)
IIS log shows 200's across the board.
Any ideas on where to look next?

You can check to see if Firewall is the issue.
You can also use the following log files to help you troubleshoot client notification problems.
Component
Log
Notification Manager
<smssiteserver setup dir>\logs\bgbmgr.log
Notification Server
<mp setup dir>\logs\BGBServer.log
<sms_ccm dir or client setup dir>\logs\BgbHttpProxy.log
For installation issues:
<mp setup dir>\logs\BgbSetup.log
<mp setup dir>\logs\bgbisapiMSI.log
Notification Agent
<client setup dir>\logs\CcmNotificationAgent.log
Refer to the blog posted by Yvette...
http://blogs.technet.com/b/configmgrteam/archive/2012/09/27/fast-channel-for-system-management.aspx
Krishna Santosh Maadasu Please remember to click “Mark as Answer” on the post that helps you, and click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

User can not receive mail, there are many mail notification pending (WF)

Hi All ,
In Production environment user can not receive mail, there are many mail notification pending (WF)..
can anybody help me on this?
Thanks.

Hi ,
This is my initial investigation...
SQL> SQL> select fsc.COMPONENT_NAME,fsc.STARTUP_MODE,fsc.COMPONENT_STATUS,fcq.last_update_date
2 from APPS.FND_CONCURRENT_QUEUES_VL fcq, fnd_svc_components fsc
3 where fsc.concurrent_queue_id = fcq.concurrent_queue_id(+)
4 order by COMPONENT_STATUS , STARTUP_MODE , COMPONENT_NAME;
COMPONENT_NAME STARTUP_MODE COMPONENT_STATU LAST_UPDATE_DAT
ECX Inbound Agent Listener AUTOMATIC RUNNING 12-DEC-10
ECX Transaction Agent Listener AUTOMATIC RUNNING 12-DEC-10
WF_JMS_IN Listener(M4U) AUTOMATIC RUNNING 12-DEC-10
Web Services IN Agent AUTOMATIC RUNNING 12-DEC-10
Web Services OUT Agent AUTOMATIC RUNNING 12-DEC-10
Workflow Deferred Agent Listener AUTOMATIC RUNNING 12-DEC-10
Workflow Deferred Notification Agent Listener AUTOMATIC RUNNING 12-DEC-10
Workflow Error Agent Listener AUTOMATIC RUNNING 12-DEC-10
Workflow Inbound JMS Agent Listener AUTOMATIC RUNNING 12-DEC-10
Workflow Inbound Notifications Agent Listener AUTOMATIC RUNNING 12-DEC-10
Workflow Java Deferred Agent Listener AUTOMATIC RUNNING 12-DEC-10
Workflow Java Error Agent Listener AUTOMATIC RUNNING 12-DEC-10
Workflow Notification Mailer AUTOMATIC RUNNING 12-DEC-10
13 rows selected.
SQL> SELECT message_type, COUNT(1)
FROM apps.wf_notifications
WHERE 1 = 1 AND mail_status = 'FAILED' AND status = 'OPEN'
GROUP BY message_type;
2 3 4
MESSAGE_ COUNT(1)
UMXUPWD 2
POERROR 4
POAPPRV 2
APEXP 8
IBEALERT 1
REQAPPRV 2
PORPOCHA 1
APPEWF 1
8 rows selected.
SQL> select mail_status, count(*) from apps.wf_notifications
where status = 'OPEN'
and mail_status in ('MAIL','ERROR')
group by mail_status;
2 3 4
MAIL_STA COUNT(*)
ERROR 798
MAIL 2578
SQL> select tab.msg_state, count(*) from applsys.aq$wf_notification_out tab group by tab.msg_state ;
MSG_STATE COUNT(*)
EXPIRED 207
READY 9063

Agent is unreachable

Hi!
I'm using EM12cR2 on Solaris SPARC. EM agent 12.1.0.2.0 became to crash after 2 days network subnet was changed.
How occurs the problem:
1. I started agent
2. After few hours i got a notification
Message=Agent is Unreachable (REASON = unable to connect to http server at https://DSSINVDB01:3872/emd/main/. [peer not authenticated]). Host is unreachable (REASON = Unknown Error pinging the host of URL https://DSSINVDB01:3872/emd/main/.1).
3. After 10..30 mins i got notification that agent became up again.
4. steps 2-3 occured few times per day.
5. After few hours or days agent became unreachable for keeps and didn't restart
./emctl status agent gets the following:
Status agent Failure:unable to connect to http server at https://dssinvdb01:3872/emd/lifecycle/main/. [peer not authenticated]
Agent is Not Running
$ps -ef | grep agent
oracle 21236 1 0 окт. 25 ? 0:53 /u01/app/oracle/agent12c/core/12.1.0.2.0/perl/bin/perl /u01/app/oracle/agent12c
oracle 24472 21236 0 окт. 28 ? 11:34 /u01/app/oracle/agent12c/core/12.1.0.2.0/jdk/bin/sparcv9/java -Xmx128M -XX:MaxP
Others agents on other hosts don't have such issue.
I checked logs of EM agent and didn't found any essential errors.
I totally cleared (deinstalled & removed all files) and installed fresh agent binaries on that host. But it also didn't help.
Ntp clients configured...

On the one server with patch cluster + 10_Recomended problem was solved, but on another one - still exists.
I've got notifications
Agent is Unreachable (REASON = unable to connect to http server at https://dssinvdb01:3872/emd/main/. [peer not authenticated]). Host is unreachable (REASON = Unknown Error pinging the host of URL https://dssinvdb01:3872/emd/main/.1).
3 times per day. Agent is restarted ( emctl status agent > Started at is refreshed regulary )
This server has also Solaris 10 update 10 installed but i'm not sure that latest 10_recommended was aplied as on the first host.

Email notifications getting stuck in WF_Deferred

Things we tried…
1.Refresh-
Workflow Deferred Notification Agent Listener
Workflow Deferred Agent Listener
Workflow Java Deferred Agent Listener
Workflow Agent Listener Service
Workflow mailer
Workflow mailer service
And
2.Run the workflow background process for AP REMITTANCE ADVICE
After running these the WF_DEFERRED table started to release stuck records.
However the when the new PAYMENT were created. The supplier is sent e mail notification ..the lines got stuck again.
Any ideas why its getting stuck ?
EBS 11.5.10.2

Hi,
You must schedule "workflow background process" to run at regular intervals for your EBS to work properly.
Performance Degradation when the Workflow Background Process is Running [ID 743338.1]
How To Handle AP Business Events In The Wf_Deferred Queue When Using Email Remittance Advice ? [ID 273147.1]
E-Mail Payment Remittance To Supplier Does Not Work? [ID 261478.1]
Thanks

Notification Mailer R12 - Does not send emails

Dear All,
we are trying to set up the Standard Oracle Notification Mailer in R12.
We believe we have pretty much covered all aspects of the configuration but it looks like something is either missing or not working...
Here what has been done so far:
1. We purged the Workflow Queue to avoid unwanted emails to be sent out, updating the WF_NOTIFICATIONS setting MAIL_STATUS to SENT; the WF_NOTIFICATION_OUT is empty.
2. We created an Ad-Hoc Workflow Mailer for a single item_type (UMXUPWD, for changing OA Password):
Outbound eMail Account (SMTP) set up (just the server name not the UserName and PWD)
Inbound eMail Account (IMAP) set up (ServerName, UserName, PWD and Replay-To)
Correlation_ID has been set to UMXUPWD
on the Message Generation tab we filled up the From and Reply-To-Address fields
3. Override Address has been set (so that all emails will be sent to a Test Account) and works fine (We did get the email and we confirmed the code).
4. we changed at Global Level (from the Workflow Administration page) the "Do Not Send me Emails" to "Send me HTML mails"
5. Workflow deferred agent listener has been set (default values)
6. Workflow deferred notification agent listener has been set (default values)
7. Workflow error agent listener has been set (default values)
8. Workflow inbound notification agent listener has been set (default values)
We started the Workflow Notification Mailer (for UMXUPWD). We selected a User which has "Send me email" as preference, we requested a password change for this user. We see the notifications in the WF_NOTIFICATIONS table ready (mail_status = MAIL) to be sent but the WF_NOTIFICATION_OUT remains empty and no mails are sent out. We also tried to change the Correlation_ID to the Message_Type (instead of the Item_Type) and to leave it blank...no results = no emails.
Note: neither the TEST Mail for the Notification Mailer worked, so far the only email which has been sent out was the one for the Overriding.
Any ideas why?
Thank You, Pier Paolo.

So the message got 'lost' from the deferred agent listener and the mailer: it was successfully dequeued and processesed from wf_deferred but not enqueued into wf_notification_out.
Check the log file for the deferred agent listener on the middle tier under $APPLCSF/$APPLLOG. The file name will be FNDCPGSC#####.txt (there will be about three of them, you will have to find the one with internal tag WFALSNRSVC). Reproduce the problem and see if there are any errors here.
Check if the persitance time for queue wf_notification_out is zero. If it is then you could be mislead: if it is zero then the message will be immediately removed by the AQ system, suggesting the message was never enqueued.
Also, run $FND_TOP/sql/wfmlrdbg.sql <notif ID> and get the HTML it produces... usually it is able to tell what could have happened.
I hope this helps,
Alejandro

Notification Agent

Similar Messages

Maybe you are looking for