AD IDM Gateway problem

There is another post to this same error but with no reply.

I have:

IDM 7.0 in a Solaris 10 Zone

Web Server is Sun Web Server 7.0

Gateway installed in a Windows 2003 server

I have an LDAP, FlatFile and OS400 resource adapter working ok, but when

creating and instance of Active Directory, I try to test it and get:

Test connection failed for resource(s):

AD: ==> java.lang.SecurityException: The agent protocol does not match a supported server protocol. Check the agent version.\n

Can anyone help me or give some orientation?

Thank you in advance.

[618 byte] By [hj2633a] at [2007-11-27 6:17:00]
# 1
please check the portnumber and the parameters when connecting to AD.HTH.G
G_identitya at 2007-7-12 17:29:21 > top of Java-index,Web & Directory Servers,Directory Servers...
# 2
Port and parameters are ok, if not I get a connection error, where can I find information on this "agent protocol" error.
hj2633a at 2007-7-12 17:29:21 > top of Java-index,Web & Directory Servers,Directory Servers...
# 3
Can you check the compatible version's for IDM with the resource. Check the gateway version also. If there is any older version running, the remove it.
G_identitya at 2007-7-12 17:29:21 > top of Java-index,Web & Directory Servers,Directory Servers...
# 4

Thank you for your responses. IDM Gateway was installed from the IDM 7.0 Media,

the Windows 2003 server is a fresh install.

I have just been informed that the Windows 2003 Server si installed within a Microsoft

Vitual Server I don't know if this can be a problem, don't see why, I have Mac OS (macbook laptop) running windows 2003 server in a virtual server and I can

connect from an IDM installation in my host OS.

Customer says it does not have a firewall in between and does not have

a firewall installed into windows 2003 server.

I did a telnet to port 9278 from IDM server and I got a successfull

connection on that port.

Do you know of any document, post or link that details this gateway error so as

to determine the cause of the problem and know where else to look?

hj2633a at 2007-7-12 17:29:21 > top of Java-index,Web & Directory Servers,Directory Servers...
# 5

I believe the IDM Gateway communicates with AD via ADSI - you may have to check to see if your server admins can talk via ADSI (can do this through a Windows Script) from you gateway server to the AD box, also The encryption protocol can cause issues (Kerberos may want your servers to be time synchronized)

--Calum

calumsma at 2007-7-12 17:29:21 > top of Java-index,Web & Directory Servers,Directory Servers...
# 6

I have checked both IDM server date and Windows 2003 server gateway date and are the same.

I have re-installed IDM to use version 7.1, removeed gateway 7.0 and re-installed 7.1 gateway.

I started the gateway with -d option and I see a Error reading encrpytion key from registry. Using default. That is the only error I see

Just need to access ActiveDirectory (not lotus or any other resource - not installed anyway)

Can any one help?

06/14/2007 13.57.12.919000 [3680] (../../../../src/wps/agent/logging/WSTrace.cpp,150): trace active, level: 4, file: c:\idm\gateway.log, maxSiz

e: 10000 KB

06/14/2007 13.57.12.939000 [3680] (../../../../src/wps/agent/logging/WSTrace.cpp,108): In WSTrace::init()

06/14/2007 13.57.12.939000 [3680] (../../../../src/wps/agent/logging/WSTrace.cpp,109): Gateway version: 'Sun Java System Identity Manager 7.1'

06/14/2007 13.57.12.949000 [3680] (../../../../src/wps/agent/logging/WSTrace.cpp,110): OS version: 'Windows Server 2003 Family (Build 3790)'

06/14/2007 13.57.12.979000 [3356] (../../../../src/wps/agent/util/ThreadRunner.cpp,61): Waiting for request event

06/14/2007 13.57.12.999000 [3680] (../../../../src/wps/agent/logging/WSTrace.cpp,182): Setting trace file to 'c:\idm\gateway.log'

06/14/2007 13.57.13.090000 [3680] (../../../../src/wps/agent/logging/WSTrace.cpp,150): trace active, level: 4, file: c:\idm\gateway.log, maxSiz

e: 10000 KB

06/14/2007 13.57.13.160000 [3680] (../../../../src/wps/agent/logging/WSTrace.cpp,205): Trace file set to 'c:\idm\gateway.log'

06/14/2007 13.57.13.260000 [3680] (../../../../src/wps/agent/logging/WSTrace.cpp,253): Trace level set to '4'

06/14/2007 13.57.13.340000 [3680] (../../../../src/wps/agent/connect/main.cpp,247): Enter: doDominoInitialization

06/14/2007 13.57.13.430000 [3680] (../../../../src/wps/agent/connect/main.cpp,285): Problem getting notesini dir

06/14/2007 13.57.13.550000 [3680] (../../../../src/wps/agent/connect/main.cpp,327): Exit: doDominoInitialization

06/14/2007 13.57.13.630000 [3680] (../../../../src/wps/agent/connect/ntsvc.cpp,95): Service::svc

06/14/2007 13.57.14.091000 [3680] (../../../../src/wps/agent/connect/server.cpp,269): starting up server daemon PORT 9278

06/14/2007 13.57.43.383000 [3680] (../../../../src/wps/agent/connect/RAEncryptor.cpp,128): Error reading encrpytion key from registry. Using de

fault.

06/14/2007 13.57.43.473000 [3680] (../../../../src/wps/agent/connect/RASecureConnection.cpp,64): RASecureConnection: new connection handler

06/14/2007 13.57.43.573000 [2392] (../../../../src/wps/agent/connect/client_handler.cpp,344): got 44 bytes

06/14/2007 13.57.43.684000 [2392] (../../../../src/wps/agent/connect/RASecureConnection.cpp,264): ReceivePrivate: count: 24, 40 wrapped up rawl

ength 40

06/14/2007 13.57.43.764000 [2392] (../../../../src/wps/agent/connect/RASecureConnection.cpp,273): Rightbefore decrypt:

06/14/2007 13.57.43.854000 [2392] (../../../../src/wps/agent/connect/RAEncryptor.cpp,69): RAEncryptor::Decrypt3DES: input length (32) moded to

4

06/14/2007 13.57.43.934000 [2392] (../../../../src/wps/agent/connect/RASecureConnection.cpp,114): SendPrivate: count: 0 pad: 4

06/14/2007 13.57.44.034000 [2392] (../../../../src/wps/agent/connect/RASecureConnection.cpp,422): Enter: MakeChallengeResponse

06/14/2007 13.57.44.164000 [2392] (../../../../src/wps/agent/connect/RASecureConnection.cpp,474): MakeChallengeResponse(in,out):

(47,F2) (71,E1)

06/14/2007 13.57.44.304000 [2392] (../../../../src/wps/agent/connect/RASecureConnection.cpp,476): (FB,ED) (41,B0)

06/14/2007 13.57.44.355000 [2392] (../../../../src/wps/agent/connect/RAEncryptor.cpp,128): Error reading encrpytion key from registry. Using de

fault.

06/14/2007 13.57.44.415000 [2392] (../../../../src/wps/agent/connect/RASecureConnection.cpp,497): MakeChallengeResponse Key:

06/14/2007 13.57.44.495000 [2392] (../../../../src/wps/agent/connect/RASecureConnection.cpp,507): Exit: MakeChallengeResponse

06/14/2007 13.57.44.595000 [2392] (../../../../src/wps/agent/connect/RASecureConnection.cpp,114): SendPrivate: count: 16 pad: 4

06/14/2007 13.59.16.858000 [3680] (../../../../src/wps/agent/connect/server.cpp,301): shutting down server daemon

06/14/2007 13.59.16.908000 [3680] (../../../../src/wps/agent/connect/ntsvc.cpp,117): Shutting down

hj2633a at 2007-7-12 17:29:21 > top of Java-index,Web & Directory Servers,Directory Servers...
# 7

I had the same problem and it seemed an incompatibility with Access Manager product. I had IdM running on the same application server than the portal server. I could not solve the problem, but when I deploy IdM in a new application server instance the problem was solved.

Are you running IdM with AM?

Hope this helps. Bye

Mariano

Mariano.Capurroa at 2007-7-12 17:29:21 > top of Java-index,Web & Directory Servers,Directory Servers...