APAR status
Closed as program error.
Error description
When running the Exchange2007Sensor from a Windows 64 bit TADDM gateway, the sensor gives the message, "Discovered 0 exchange servers". The DiscoverManager.log contains the following message indicating that the Get-ExchangeServer PowerShell cmdlet could not be found: 2011-01-05 15:43:25,417 DiscoverManager [DiscoverWorker-27] Exchange2007Sensor-10.18.153.20-6001 DEBUG util.OsCommand - execute(cmd.exe /C cmd.exe /c C:/WINDOWS/temp/taddm.1oygy5/TaddmTool.exe -DTADDM_ID=1oygy5 -DTADDM_USERNAME="domain\userid" -DTADDM_PASSWORD=XXXXXXXX -DTADDM_TIMEOUT=480 PSCommand @10.18.153.20 Get-ExchangeServer ): output= !?! 20101029083319 [domain\userid/********@10.18.153.20] PSCommand(Get-ExchangeServer) !?! 20101029083319 AutoDeploy=False RestartWmiOnAutoDeploy=False RestartWmiOnFailure=False InstallLocalProvider=False WmiQueryExactCount=False CommandOutputStanderdedCommandOutput!$!Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Admin; Get-ExchangeServer!$!StanderededErrorOutput!$!Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Admin; Get-ExchangeServer!$!Add-PSSnapin : No snap-ins have been registered for Windows PowerShell version 2. At line:1 char:13 + Add-PSSnapin <<<< Microsoft.Exchange.Management.PowerShell.Admin; Get-ExchangeServer|Format-List + CategoryInfo : InvalidArgument: (Microsoft.Excha...owerShell.Admin:String) [Add-PSSnapin], PSArgumentException + FullyQualifiedErrorId : AddPSSnapInRead,Microsoft.PowerShell.Commands.AddPSSnapinCommand The term 'Get-ExchangeServer' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:80 + Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Admin; Get-ExchangeServer <<<< |Format-List + CategoryInfo : ObjectNotFound: (Get-ExchangeServer:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException The error is due to the fact that TaddmTool.exe runs as a 32 bit application, and accesses the 32 bit PowerShell on the Windows 64 bit gateway. The 32 bit PowerShell cannot access Exchange Management tools installed and registered on Windows 64 bit PowerShell. Additional Search Keywords: 64b 64-bit
Local fix
Problem summary
When running the Exchange2007 Sensor from a Windows 64 bit TADDM gateway, the sensor gives the message, "Discovered 0 exchange servers". This occurs due to the fact that TaddmTool.exe runs as a 32 bitapplication, and accesses the 32 bit PowerShell on the Windows 64 bit gateway. The 32 bit PowerShell cannot access Exchange Management tools installed and registered on Windows 64 bit PowerShell.
Problem conclusion
The fix for this APAR is contained in the following maintenance packages: | Fix Pack | 7.2.0.0-TIV-ITADDM-FP0005
Temporary fix
Comments
APAR Information
APAR number
IZ92488
Reported component name
APP DEPENDENCY
Reported component ID
5724N5500
Reported release
720
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-01-18
Closed date
2011-03-23
Last modified date
2011-03-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
APP DEPENDENCY
Fixed component ID
5724N5500
Applicable component levels
R720 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"720","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 March 2011