Is this product still in active development?

Its perfect for the code to hit the common partition because you wont know which one they have access too, just no need for the error. In fact you can use the error as a trigger to disable certain parts of the client functionality accordingly, eg the calls you know will not work in when they dont have access to common partition, or adjust those calls to be read only instead. You could even use it to trigger the code which asks the F5 what you do have access too, if it can provide that information.

 

 

The F5's in this case are 6800's running 10.0.1 code. I have manager access to only one partition. The environment is authenticated proxy which appears to be handled via NTLM authentication as I dont have to enter a login. If I turn off the proxy pac script I hit something that asks me for basic auth. I guess your app is not using the existing proxy authentication and hitting that basic auth which is making it throw an exception. Probably the best thing to do is handle the exception quietly and throw it in application event log. The initial startup error only appears to occur once, seems the daily update check the first time you run it and then it triggers the update code after it. The second time you start the app you dont get the first error above.

 

 

Regards

 

 

Jarvil