Connection Errors via NFuse 1.7 Classic 1

[birchsl]

Until recently we have been running NFuse Classic with no problems.

We have a dedicated web server and 2 load balanced terminal servers running several applications. A user can log into NFuse and their apps are displayed for them. However, occasionally they will get 3 different errors when trying to launch an application.

These errors are intermittent.

1. "ICA file not found" (although the ICA files are on both servers)

2. "[Application Servers] section not found in ICA file"

3. "Remote Application Runtime Error"

These errors seem pretty straight forward except for the fact that they don't occur every time a user tries to launch an application. The clients are a mixture of W2K and 95 and all have downloaded the latest client files.

I can't understand why sometimes they can work ok and other times they have these errors.

Any help will be greatly appreciated.

 

[rezinz28]

How is the setup? Is NFuse on a Citrix server? Also are you using a port other than 80 for Citrix XML.

Steve Thank You,
Steve

 

[birchsl]

Our Nfuse server is not a citrix server. Users connect to the NFuse server in the first instance and then run applications that are load balanced between the 2 citrix servers. As far as I am aware we only use port 80.

Thanks

 

[gbiello]

Here's an idea. It does pertain to NFuse. Try clearing the Internet cache on some of the local machines.

From CTX395275:
"On Windows computers with large hard drives, the Temporary Internet Files folder used by Internet Explorer can become excessively large, causing too much of a delay in the time required to save the launch.ica file and then retrieve it for use by the ICA client."

-gbiello

 

[rezinz28]

When you get to the page that has your published apps in NFuse right click on the published app and save as. what is the file that it is saving. Is it launch.ica?

Steve Thank You,
Steve

 

[birchsl]

Thanks gbeillo - I'll try that.

And yes Steve, the save file is 'launch.ica'.

 

[birchsl]

Tell a lie - it's 'launch.asp'.

 

[birchsl]

Thanks gbiello - your suggestion seems to have rectified this problem.