[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2534
  • Last Modified:

Failed to load resources from resource file. Please check your setup.

We've got a bespoke .Net 1.1 database (SQL server) application that we've had developed by a third party. The server is running on SBS 2003 R2 Premium and all the clients are XP SP3.

Recently we a had a bit of a nightmare with trying to uninstall Syamantec Endpoint Security and since then, whenever the application tries to open up Word 2003 for a mailmerge, an error pops up "failed to load resources from resource file. please check your setup" and then after one or two seconds crashes.

The application was working fine before we uninstalled SEP. I've asked the developers for help but they're insisting the problem is not theirs and that the issue must be related to the server itself (or the software on it) as it was all working fine previously. They're suggesting it might be a permissions issue, a corruption or some other misconfiguration.

Does anyone know what sort of permissions they're talking about? We're using AD U&G policies for user access to the database but they seem to allow us to log into the system correctly. I've already tried uninstalling .NET 1.1 and reinstalling it but without success.
Are there any other applications/dependent files I should reinstall or any other things I need to check to see if it's all configured properly? Are there any tools to test if .NET is working properly?

The App Event Viewer Error comes up with a lot of identical errors including the following text....

caught exception in Logger.AppendFile - The given path's format is not supported.
   at System.Security.Util.StringExpressionSet.CanonicalizePath(String path, Boolean needFullPath)
   at System.Security.Util.StringExpressionSet.AddExpressions(String[] str, Boolean checkForDuplicates, Boolean needFullPath)
   at System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess access, String[] pathListOrig, Boolean checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
   at System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean useAsync, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access)
   at MMSv2.Logger.AppendFile(ELevel level, String msg, Exception ex)
log filepath: C:/Program Files/OurDB/C:/Program Files/OurDB/log/logfile20090219.log2

I've tried running procmon on the client pc and can spot a lot of issues relating to the application getting the pathnames to dependent dlls all wrong (all being appended to the path of the application instead of from the correct path) but other than that I have no clue how to interpret the errors.

I have absolutely no clue about programming .NET or SQL server for that matter and don't have access to their source code but I want to make sure the server and clients are all in tip top condition before putting the ball back in the application developers court.

Also, if there's anythnig I should be asking them, please let us know.
0
Dale303
Asked:
Dale303
  • 3
  • 2
2 Solutions
 
Perry_IDITCCommented:
Hi,

I would try some basic cleaning on a PC. Symantec products don't always gracefully uninstall.

Try:
1. Download and run Ccleaner. It will remove temp files and also has a registery cleaner. I would run both.
http://www.ccleaner.com/download

2. Put a Win XP cd in the drive and run SFC / SCANNOW from the run box (start --> run) This will check all system files and make sure they are in their orginal versions.

3. In Word 2003 run the Detect and Repair wizard from the Tools menu or the Help I forget where it is. If this dosn't work uninstall Office 2003, restart, install Office 2003, install all updates and service packs.

4. Uninstall and reinstall your application.

What are you using for Anti-Virus software? I would recommend Avast! It works great in all enviroments.

Cheers,
Perry


0
 
Perry_IDITCCommented:
One more thing.

Is there any security software running on your computer? Firewalls, ant-spyware, anti-virus, anything? Is your windows firewall disabled?

Cheers,
Perry
0
 
Dale303Author Commented:
Well the server is SBS 2003 Premium R2 with ISA 2004 for firewall duties, however the problem still occurs even if ISA is disabled.

We're currently using no AVp on the server itself whilst I'm triyng to sort this issue out (it's isolated and the only access is via client PC with AVp's installed) and a variety of AVp products on the clients (going through some trials to see which one seems to work best). I've been quite happy with Kaspersky for Servers/Workstations on other setups but Kaspersky has issues with procmon and a few other legitimate tools and hasn't been updated in years so looking into possible alternatives.

It was the Symantec Cleanwipe utility that caused all the issues in the first place. I get the feeling it simply removed all references to Symantec entries wthout restoring certain settings back to their defaults (therefore knobbling RRAS and bits of ISA). In fact I had to reinstall ISA to get RRAS to work again. Through my various attempts. I'm now at the point where I've completely uninstalled all of the Premium parts of SBS 2003 R2 and reinstalled them. (plus SPs and updates, etc).

sfc /scannow runs smoothly,

The problem is def not Office 2003 as I recently did a nuke/refurbishment of one of the clients which  still has the same issues (even for the brief moment it had no AVp).

I've yet to give CCleaner a go though. watch this space...
0
 
Perry_IDITCCommented:
After the reinstall of all of the premium components it's still not working? Also can you post the contents of this log file? C:/Program Files/OurDB/log/logfile20090219.log2

Theres a Reg cleaner in CCleaner you might want to run also, make a backup first.
0
 
Dale303Author Commented:
Finally fixed it.

On my part, I managed to screw up the order of my Firewall settings when I reinstalled ISA. It was only entry, one level out but it made a huge difference. On the app developers side, they managed to mistype some login details that were required for access to certain DLL files they needed when they were investigating the problem from their end. The app developers still needed to tinker some code but I was never party to what they did to fix the problem.

Thanks for the CCleaner tip. It wasn't really of any use in this situation but boy has it been great in others.
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now