Error with Policy Agent 2.2
Hi,
I've seen this problem listed here a while ago without any solution.
1- I install my Java Web Server 6.1 under C:\Sun\WebServer6.1
2- I start the server, no problem.
3- I install the proper Policy Agent, installation seems fine.
4- In order to see the changes, I stop the server and then it won't restart. Here is the message in the error log:
failure ( 3592): CORE3170: Configuration initialization failed: Error running init function load-modules: dlopen of c:/Agents/2.2/es6/bin/ames6.dll failed
This file (ames6.dll) is there btw...
If I uninstall the agent, the server starts.
Thanks for you help,
[669 byte] By [
benb99a] at [2007-11-26 12:26:23]

# 4
Hi,
I've posted a solution to this in the other thread that deals with exactly the same problem, namely:
In short: yes, it's the dependencies. No, you can't register ames6.dll. Enjoy! ;-)
http://forum.java.sun.com/thread.jspa?threadID=5114812&messageID=9633682
- Felix Gaehtgens
# 5
Hi.
I also have a problem with Policy Agent, although it's different...
I'm using Web Server 7.0 and just got a copy of PA 2.2for WS 7.0, but when I run agentadmin --install it shows an Exception:
java.lang.NoClassDefFoundError: de.
I'm currently using Windows XP Prof.
Am I doing something wrong in any way?
Any help would be greatly appreciated.
Thanks.
# 7
The complete error stack is
"Exception in thread "main" java.lang.NoClassDefFoundError: de ". It doesn't give me more messages.
The files in the lib directory are:
ames6.dll
amsdk.dll
freebl3.chk
freebl3.dll
libnspr4.dll
ilibplc4.dll
libplds.dll
libxml2.dll
msvcp71.dll
msvcr71.dll
nss3.dll
opensso-installtools.jar
opensso-installtools-launcher.jar
sjsws_agent.jar
smime3.dll
softokn3.chk
softokn3.dll
ssl3.dll
Those are the files I found when unzipped the download, and I haven't manipulated them or anything.
Thanks for your answer.
# 11
Hello...
I found the problem... turns out that the installer doesn't work if the path where you have the installer has spaces.
Can't believe I spent days on this... I'd like to know if this "problem" shows up in any other product of the Identity Management Group.
Anyway, Subba, thanks for your (much needed) help.