• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

problem in WIN NT

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
After installation,
when fortune application checked its giving
"GX Error(GX2GX)" and unable to open the deployment tool"
For GX Error, i have tried all this activities
(i)Checked kjs engine is up & running(Checked in the admin tool whether kjs engine is running or not)
(ii)tried the URL as http://<host>.<domain>:88/NASApp/fortune/fortune (include domain also) --
(iii)checked fortune application in admin tool. The fortune application is not registered in the admin tool. I am thinking to deploy the fortune application but deployment tool is not working.
(iv) I know that problem in plugin, but how to solve it
 
Ranch Hand
Posts: 144
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This is a strange problem Gx2GX error comes if ur request doesnt goes to kjs.
1. the problem could be Plugin not able to contact kxs
2. KXS not able to contact KJS.
I donno the logic but it works if you restart the plugin and iAS using iascontrol or Kivaes.sh
Let me know if problem still persists.
--sridhar
 
Author
Posts: 66
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What is showing up in the KXS and KAS logs? Can you get iasdeploy to run, or is it only the GUI that won't start? What error does the deploy tool give when you try to start it?
My first guess wass that your directory server be having problems, but I would have expected the admin tool to throw errors if that was happening. I don't suspect that the plug-in is the problem. (At least not yet.) The plug-in wouldn't have anything to do with whether the deployement tool would start.
 
Ranch Hand
Posts: 117
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Its been long that I installed iAS but I think the deploy tool is an optional component. Check if it has been intalled right or your best best is to re-install if you dont have much information.
The 'GX' problem occurs anytime it does not find the class that you are trying to access. Given the situation, I think the plug-in is fine.
Depending on the version that have installed, you may try to deploy without using the GUI tool.Refer to admin guide.
Raj
 
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I too face problem while using iasdeploy tool
It throws the below exception when i tried to use the iasdeploy.bat.Same error is thrown for ksvradmin.bat and iascontrol.bat.
What will be the reason and how to solve the issue
GXBindInit: GXBindBasic failed
GXContextInit: GXBindInit failed 2
[11/Oct/2002 12:21:13:8] error: ENGINE-context_init_failed: EngineClassSpace Con
textModule.createContextInit failed:
 
Ranch Hand
Posts: 79
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
You will see this error if the LDAP Server didnt respond to the Application Server. So the Application server has throwed this message after re-trying the connection to LDAP.
Verify that that the LDAP Server is restarted .
Check the KXS log for :
ldap_result failed: Bad parameter to an ldap routine...retrying
Hope this helps,
Thanks,
Raj
 
Legend has it that if you rub the right tiny ad, a genie comes out.
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic