Welcome to Pandora FMS Community › Forums › Community support › Is Windows Agent 3.0 W2k8R2 x64 ready?
-
Is Windows Agent 3.0 W2k8R2 x64 ready?
Posted by benni on December 30, 2009 at 14:28I’ve two questions.
1.is the Final Release of Pandora Windows Agent 3.0 W2k8R2 x64 ready? Because the Pandora Service won’t start. When I turn on DebugLog in Pandora Agent, no error is Logging. Windows Logs:
Faulting application name: PandoraAgent.exe, version: 0.0.0.0, time stamp: 0x4b2b7f60
Faulting module name: msvcrt.dll, version: 7.0.7600.16385, time stamp: 0x4a5bda6f
Exception code: 0xc0000005
Fault offset: 0x000143f9
Faulting process id: 0x8c0
Faulting application start time: 0x01ca89354ff04236
Faulting application path: C:Program Files (x86)pandora_agentPandoraAgent.exe
Faulting module path: C:Windowssyswow64msvcrt.dll2. How can I get the Migration tool to Upgrade Pandora DB 2.1 to 3.0.
Thanks for your Help.
RegardsReitermaniac replied 15 years, 1 month ago 4 Members · 13 Replies -
13 Replies
-
::
We have severals agents running on Windows 64Bit, but seems sometimes they have this problem, can you post here the pandora_agent.conf you’re running ?.
The migration tool is downloadable from pandorafms.com, if you don’t want to give any information, just let all data in blank, we don’t force anyone 🙂
I’ve two questions.
1.is the Final Release of Pandora Windows Agent 3.0 W2k8R2 x64 ready? Because the Pandora Service won’t start. When I turn on DebugLog in Pandora Agent, no error is Logging. Windows Logs:
Faulting application name: PandoraAgent.exe, version: 0.0.0.0, time stamp: 0x4b2b7f60
Faulting module name: msvcrt.dll, version: 7.0.7600.16385, time stamp: 0x4a5bda6f
Exception code: 0xc0000005
Fault offset: 0x000143f9
Faulting process id: 0x8c0
Faulting application start time: 0x01ca89354ff04236
Faulting application path: C:Program Files (x86)pandora_agentPandoraAgent.exe
Faulting module path: C:Windowssyswow64msvcrt.dll2. How can I get the Migration tool to Upgrade Pandora DB 2.1 to 3.0.
Thanks for your Help.
Regards -
-
::
Disable (comment or delete it fron the .conf) the module_logevent. I think its because a missing library in your system (the old pdh.dll library used to get messages from logevent directly, bypassing WMI, much slower).
If works without the logevent module, try to search PDH*.* in your system and post here the results.
-
-
-
-
::
try this.
make a file c:test.txt with a word “test”
Disable all modules except for this
module_begin
module_name test string
module_type generic_data_string
module_exec type c:test.txt
module_endso, if it continues crashing, it’s a problem of the agent compilation x86 nor x86_64, if it run the problem is in how the agent handle the wmi quieries.
anyway, try svc /scannow and reboot.
-
-
-
-
-
::
I’m experiencing exactly the same issues here.
The agent fails after processing the modules on systems with Windows 7 32bit and 64bit as well as on systems with Server 2k8 R2. I tried making them run by changing compatibility settings of the .exe and running it from the commandline but there seems to be no way.I found another thread to this problem but no solution.
The question is: Has anybody definetely made the agent run on the new windows versions? Is there probabely a dependency of any installed windows feature?My Agents on Vista and Server 2k8 were working flawlessly.
Best Regards
-
::
Hmmm…
It seems I was a bit too fast with my post.Here is another thread saying it wont work with the current version
http://openideas.info/smf/index.php/topic,1107.0.html