Metrics requiring credentials are failing when the RMS is located off-box

Article:TECH140837  |  Created: 2010-09-28  |  Updated: 2010-10-09  |  Article URL
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


If the Remote Monitoring Server (RMS) has been relocated to another machine other than the Notification Server, all agentless metrics requiring credentials are failing. Ping, port, and HTTP metrics may succeed, but WMI and SNMP do not.



[2680] RuntimeCPDataAdapter.cpp(Line: 243)  PPA::RuntimeCPDataAdapter::Handle_ProcessRuntimeCredentials(): Either Handler and/or Method values in the runtime credentials are not defined or wrong type.
[2680] PPA: ProfileManager::GetConnectionProfile: Throwing exception

[1548] GetRuntimeCredentials:> Exception while invoking Altiris.OOB.OOBSCEntry, Altiris.OOB, Version=, Culture=Neutral, PublicKeyToken=38721dad2e6c10f9.FindConnectionSettings: 
[1548] System.IO.FileNotFoundException: Could not load file or assembly 'Altiris.OOB, Version=, Culture=neutral, PublicKeyToken=38721dad2e6c10f9' or one of its dependencies. The system cannot find the file specified.  
[1548] File name: 'Altiris.OOB, Version=, Culture=neutral, PublicKeyToken=38721dad2e6c10f9'  
[1548]    at System.RuntimeTypeHandle._GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, Boolean loadTypeFromPartialName)  
[1548]    at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark)  
[1548]    at System.RuntimeType.PrivateGetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark)  
[1548]    at System.Type.GetType(String typeName, Boolean throwOnError)  
[1548]    at PPA.?A0x46355a8e.GetRuntimeCredentials(basic_string<wchar_t\,std::char_traits<wchar_t>\,std::allocator<wchar_t> >* , basic_string<wchar_t\,std::char_traits<wchar_t>\,std::allocator<wchar_t> >* handlerName, basic_string<wchar_t\,std::char_traits<wchar_t>\,std::allocator<wchar_t> >* methodName, basic_string<wchar_t\,std::char_traits<wchar_t>\,std::allocator<wchar_t> >* deviceId, basic_string<wchar_t\,std::char_traits<wchar_t>\,std::allocator<wchar_t> >* protocolId)  



  • Pluggable Protocols Architecture SP4 HF1  7.0.7417


This behavior occurs if the associated Connection Profile with the resource has runtime credentials specified for any protocol.

This is a known issue and has been submitted to development.



There is no direct resolution to this issue at this time. The workaround is to change all protocols within the Connection Profiles to use specific credentials:

  1. In the Console, access Settings > All Settings > Monitoring and Alerting > Protocol Management > Manage Connection Profiles
  2. Modify each Connection Profile's protocol configuration to use specific credentials instead of runtime credentials

This article will be updated once this issue is addressed in a future release.

Supplemental Materials


Protocols requiring credentials fail with runtime credentials being used by any protocol with RMS installed off-box

Article URL

Terms of use for this information are found in Legal Notices