This sounds very similar to another thread post several weeks ago (amusingly titled "Embedded Web Determinations spewing FileNotFoundExceptions like a teen binge drinker on emetics"). The issue is that the embedded Apache Tomcat server is writing to the C:\Program Files directory, which is usually a protected location. This would not be a problem on a server which usually installs Tomcat in a different location. We are not sure why this happens on some user's machines, however it could be related to your security policy.
1 person found this helpful
That's the direction we'll look in then, hopefully it's an easy fix.
We've had a closer look into the problem mentioned above and it's not looking as simple as we'd hoped.
The issue, though currently ill-defined, could definitely be due to a problem with permissions where the rulebase
is attempting to write to the (restricted) C: Drive for the embedded Tomcat server (as the error message would appear to indicate).
This theory doesn't quite line up with the other information we have, however, as:
- All of the virtual desktops in the organisation are standard built
- All standard users have the same permissions
- All other rulebases are still working on my virtual desktop
- This particular rulebase works correctly on a different author’s virtual desktop
Our IT consultant has checked the Java memory allocation and advised that it looked fine. He theorised that it could be do with the space in the working area for the rulebase – and is currently trying to ascertain where that working area is.
Do you have any other ideas as to possible solutions?
Thanks in advance,