NSAPI Plugin

Hi All
  I am getting the following exception on my UI

"Message from the NSAPI plugin: Internal Server failure, NASPI Plugin.  Cannot Continue."

I could not see any logs.

Any hints?
technokraftAsked:
Who is Participating?
 
for_yanConnect With a Mentor Commented:

Well, it could be some condition on the network, but if you increase this timeout parameter it should
not make anything worse, but maybe this user will not see these mnessages.
Also in one of the references they recommend to make this time 600 instead of 300 and
parameter is WLIOTimeOutSecs needed to be mentioned in explicitly in obj.conf

It seems to e it would be not bad idae to try - given several different people recommed the same remedy

0
 
for_yanCommented:
What is it you are running, when you get this  error?


http://answers.yahoo.com/question/index?qid=1006053024512
0
 
technokraftAuthor Commented:
Hi Yan
  Thanks for the link. But it does not say anything about the issues. Any link which says about the common problems for NSAPI?. Or anything related to the log message i posted?
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
for_yanCommented:
I guess it has something to do with Weblogic, do you connnect to weblogic?

http://objectmix.com/weblogic/578976-internal-server-failure-nsapi-plugin.html
0
 
for_yanCommented:




Does this say anything to you:




to debug: add "Debug=3DALL" in iisproxy.ini and look at c:\temp\wlproxy.log=
..

Also run the isapi with the option of:
"Cached ISAPI applicaiton" and set the isolation level to "HIGH"

This is from:

http://objectmix.com/weblogic/551829-internal-server-failure-isapi-plugin.html



0
 
for_yanCommented:


One more recommendation at the end of the same web page,
but no info if that helped:

You need to add a WLIOTimeoutSecs paramater to your iisproxy.ini file. The =
default
value is 300 seconds :-) See http://e-docs.bea.com/wls/docs81/plugins/plugi=
n_params.html#1143055.
0
 
for_yanCommented:

More of the same idea:

http://forums.oracle.com/forums/thread.jspa?messageID=3383617

Is it all something which tells you anything useful, do you have access to Weblogic installation,
or you are from the user side of WL?

If so, you need to contact with WL administrators.
0
 
technokraftAuthor Commented:
HI
  The problem is only one live user is facing such problem...Can this sun one proxy error come due to time problem between browser and proxy only?
0
 
for_yanCommented:
It could probably help if you could post more details about your configuration and about
what you are trying to do when you exprience this error.
0
 
technokraftAuthor Commented:
Hi
  The thing is i dont have direct access to logs..But the config guy told me there was no error on the console...Just on the browser...The user was trying to login and get to home page...But the tricky part is only that guy is facing such problem...we tried from same area, etc but we could not get a proxy timeout issue...SO was thinking whether a client network affect connection between our sun one proxy  server and our app ?
0
 
for_yanCommented:
Yes, it looks in all cases this error has to do with some timeout and the remedy was
to increase the timeout time in somewhere in configuration.
I guess, most commonly this problem is associated with Weblogic plugin, but
I guess there may be different NSAPI plugins.  

What means - I could not see any logs ?  
0
 
technokraftAuthor Commented:
Hi
  I agree it is connection error and most probably between client network to proxy network.
  IS there any way to tell the weblogic plugin to stop printing the error i.e., to be silent ? :)
0
 
for_yanCommented:
So you do have Weblogic plugin?
Did you try those recommendstions which they have in that links  which I sent earlier?

You need to add a WLIOTimeoutSecs paramater to your iisproxy.ini file. The =
default
value is 300 seconds :-) See http://e-docs.bea.com/wls/docs81/plugins/plugi=
n_params.html#1143055.

Increase this timeout number,
Then they aslo wrote how to add debugging output
0
 
for_yanCommented:

That's what they write about debugging:
to debug: add "Debug=3DALL" in iisproxy.ini and look at c:\temp\wlproxy.log=
0
 
technokraftAuthor Commented:
Thanks for all the info..But the problem is only a specific user is getting this error.
So i was just thinking whether it can be due to his network problems
0
 
technokraftAuthor Commented:
Thanks for the tip
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.