New posts

Reply to thread

Message: <blockquote data-quote="tiradoj" data-source="post: 140467" data-attributes="member: 869">Hello AllI am trying to run multi-foundation with 89721 (Production) on one port 6014 on Prod Server and 89820 on a different port 6114 on Test Server and when I start up services on the Test Server the jde logs complain about not being able to find the Security Server====================================================1944/5240 MAIN_THREAD                           Sun Nov 08 17:34:12.988000    jdecsec.c2113    JDENET Error = eConnectionFailed1944/5240 MAIN_THREAD                           Sun Nov 08 17:34:12.988001    jdecsec.c2546    Failed to communicate with security server: Unable to locate Security Server1944/5240 MAIN_THREAD                           Sun Nov 08 17:34:12.988002    jdecsec.c262    Failed to validate user JDE by password1944/5240 MAIN_THREAD                           Sun Nov 08 17:34:12.988003    Jdb_ctl.c4147    JDB1100015 - Failed to complete Security check by Pwd1944/5240 MAIN_THREAD                           Sun Nov 08 17:34:12.988004    Jdb_omp1.c639    JDB9900246 - Failed to find existence of default OMAP for environment STARTUP=====================================================The SecurityServer is the PROD server at port 6014 and I assume the Test Server service is trying to validate against port 6014 on the PROD server for Security Server and since I have set the connect and listen port on TEST server to be 6114 per the instructions of many Multiple Foundation documents, it is not able to connect.Of course when I change the CONNECT port number to 6014 on the TEST Server, the JDE Service comes up fine and logs are clean.I have looked at 3 or 4 documents on "Multi Foundation" to refresh and see what I am missing but none of the documents address this aspect.Has anyone run into this?In the interest of full disclosure I did build a new full client package with new service pack but not a server package (thus I did not deploy one either) because in my mind it seems I need to get the new service pack to start up clean with different port before I can expect to connect and build a clean server package.Also, I did not MOVE the DV812 pathcode directory over - I copied it to new service pack level and I RENAMED the DV812 pathcode to "DV812OFF" so it should not be interfering with anything. I should also mentioned I tried changing port reference in F96511 table which none of the "Multiple Foundation" docs I reviewed talked about specifically as to how to how it may or may not relate to security server.Before commenting <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" /> (and no egotistical, insincere, presumptuous j*** off responses either) ideally, I would like to say I do NOT want to turn SecurityServer off anywhere, I do not want to designate/define a second security server, add another OCM/system database nor do I want to change any other aspect of my E1 system configuration except within the Test Server JDE.INI file. I am trying to make this work within what the known documents say but it doesn't seem possible. I know I have had multi foundation work before so I assume I must have forgotten a simple config option.Is there a way to make this work WITHOUT doing any of the above?As always, I am fully willing to admit I forgot something, and I will withold comments on the product or opening a SAR until I hear from colleagues. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />Thank you all in advance.Also, has anyone noticed you have to use WINDOWS NT Authentication for 89820 service pack to connect via ODBC on the Deployment Server? I am working that call with Oracle now. I proved that out because I can use SQL Server login account with 89721 but not 89820.Joe TiradoSenior CNC Consultant</blockquote>

Verification