Data Agent in Windows Vista

[wbosher]

I recently subscribred to Data Agent to download EOD data for the NZX. I installed it on my home PC which runs WinXP, and it works fine (after some initial teething problems).

I tried to install it on my laptop which run Windows Vista (I really dont like Vista) and I keep getting Runtime error '53': File not found. This normally means there is a missing .DLL file somewhere, which is easy to solve, but the error message doesn't specify which file can't be found.

I'm just wondering if this program is incompatible with Windows Vista, does anyone else have this successfully working on a Vista machine?? I tried running it in compatibility mode for WinXP but this didn't work either.

Any suggestions??

[kiwiwim]

Suggest you contact Findata. Either by phone or email.
I have found them always very helpful in sorting out my problems.

[wbosher]

Have you had similar problems? I did contact them after I posted this, they have given me something to try tonight as I don't have my laptop with me.

[kiwiwim]

No, I did not have similar problems but original problems with folder arangments. I had stuffed up reloading a crashed disk. The guy at Findata had great patience with me and after a lot of emails to and fro I got everything running.

[wbosher]

He's made a few suggestions but nothing has worked. I'm going to go through to make sure all the system files are intact and working correctly, hopefully that is the issue. WinXP is so much easier to troubleshoot, I really don't like Vista. :(

[absolut-advance]

He's made a few suggestions but nothing has worked. I'm going to go through to make sure all the system files are intact and working correctly, hopefully that is the issue. WinXP is so much easier to troubleshoot, I really don't like Vista. :(

I use it on Vista, have had no problems.

Check that windows update hasn't downloaded anything in the background awaiting a install and reboot, this sometimes causes problems with applications in vista as I think vista is running itself in safe mode until the process has been completed.

[wbosher]

Nope, updated all Windows updates and has been rebooted several times. Coming from an IT background, that's the first thing we ask our customers - "have you rebooted your PC?". Probably the most spoken words in IT history. ;)

When I get a chance I'll take a good look at it, works well on my XP machine so don't really care too much at the moment. I was just wondering if anyone else had experienced the same problem to save myself some digging.

Thanks for the replies though. :)

[Jay]

Just a thought - nothing to do with the UAC?? I had this problem with a programme similar to the the Data Agent.
On the properties - select to run the programme as administrator (or similar)- worked for me, though I was getting a different run-time error (44)

[wbosher]

Tried that too Jay, it was the first thing I tried. I'm logged in as an admin anyway so it shouldn't matter. I also tried running it in compatibility mode for WinXP and it spat out a different error, which I might also look into.

I think I may have some missing or corrupted .DLL files or something similar (Windows is good like that), my friend Google will help. :D

[absolut-advance]

You have received the "Runtime error '53': file not found" error message and have no idea how to fix it. In order to fight the enemy, you have to first understand it. Runtime error 53 is commonly faced by programs like Visual C++ and Visual Basic. In serious cases, it can affect you drastically as your computer system starts to hang longer than normal and once the runtime error 53 message appears, clicking "Ok" would make your PC reboot.
There are three ways you can go about solving this error -
1. Uninstall the previous program you have installed.
If the error started occurring out of the blue, you should uninstall any programs that you may have recently added. There might be a conflict with the program(s) and your operating system.
2. Reformat your PC
This definitely does the trick but it is troublesome. Also, error messages such as runtime error 53 happens commonly and it is not a solution to reformat your computer everytime you encounter such errors.
3. Registry cleaner
As runtime error 53 is caused by a conflict in software, it boils down to the registry integrity. The chain of processes to launch the program is hindered by missing files, inert files, or corrupted file names. Therefore, using a registry cleaner is free and offers a chance to restore your PC to optimal performance. A highly recommended registry scan is RegCure and it is specifically designed to constitute the industry's leading error scanning and repair technology. The easy-to-use interface makes the process of cleaning your registry both elegant and efficient. Certified to run on every Windows platform, RegCure can detect the programs causing runtime error 53 and remove detected registry errors automatically.
Use a good registry cleaner to rectify runtime error 53 and clean out junk data, redundant files, invalid shortcuts and outdated help files.


The runtime error 53 message given below is displayed when an exported DLL (Dynamic Link Library) function is called from an MTS (Microsoft Transaction Server) component that is opened as a Server Package:
Runtime error '53': File not found (DLL_File_Name.dll).
In the error message, DLL_File_Name is the name of the DLL file that is being called.
Cause Of the Error
Runtime error 53 is known to occur if the DLL file mentioned in the error message is not mentioned in the search path.
Resolution Method
When an MTS component is opened, one of the following packages can be selected:


Library Package: These components are opened in the creator process.
Server Package: These components are opened in dedicated server process.


Ideally, the DLL files must exist in the same directory as the registered MTS component. When this happens, the search order is expected to be the current folder and then the default search path. This search order is followed by an EXE application that is not instantiated in an MTS environment when it calls a COM (Component Object Model) component. This also happens if both the COM component and the DLL file exist in the same folder. Additionally, this order holds true for an MTS instantiated COM component that is configured to open as a Library object.
The runtime error 53 that we are discussing here occurs when a particular MTS component is opened as a Server Package. When this happens, the COM component is created in an isolated process space, Mts.exe. Now, the default location for the Mts.exe file is %SystemRoot%\System32. This is the reason why Mts.exe fails to find the required DLL file when it does not exist in the search path.
So, to prevent this error message and also to resolve this particular issue, you need to deploy the DLL file that is to be called on from an MTS component and opened as a Server Package in the %SystemRoot%\System32 folder.
In order to resolve this issue, perform the following tasks:


Use the Windows Search feature to find out the current location of the DLL file given in the error message.
When you find the file, right-click on it and then select Copy.
Next, open Start menu, select Run, type %SystemRoot%\System32 in the Open box and then press Enter.
In the %SystemRoot%\System32 folder that opens in Windows Explorer, right-click on the right pane, and then select Paste.

Doing this will paste a copy of the DLL file in the system32 folder and resolve the error.
Runtime errors may also occur due to the existence of invalid registry entries and malware infections. To prevent runtime errors due to registry problems, you must regularly scan and clean your registry. To do this, you may use an efficient and simple-to-use registry tool, such as RegGenie (http://www.instant-registry-fixes.org/go/reggenie_site/). To prevent and remove malware infections, you need to perform regular full system scans using reliable antivirus and antispyware tools to detect and remove any malicious data. XoftSpy SE (http://www.instant-registry-fixes.org/go/xoftspy_site/) and Anti-Virus Plus (http://www.instant-registry-fixes.org/go/antivirus_site/) are two excellent antimalware tools that you can use to perform these tasks

[wbosher]

1. Uninstall the previous program you have installed.

Tried that.


2. Reformat your PC

Absolutely not an option. I have a working copy of this program on another PC so I'm not blowing away everything on my laptop for one app.


3. Registry cleaner

This was going to be the next thing I try. I've got a good reg cleaner that I trust, some cause more problems than they solve!!


In the error message, DLL_File_Name is the name of the DLL file that is being called.

This is my main problem, the error message doesn't state what .DLL file is missing, they couldn't possibly make this easy for me. :rolleyes:


Runtime errors may also occur due to the existence of invalid registry entries and malware infections.

Have already run a quick spyware and virus scan but nothing was found. Will run a deeper scan over night some time this weekend.

I suspect that a registry scan may throw up some clues but I have to get my wife off of the damn thing first. ;)

Thanks for the suggestions guys, I'll let you know how I get on when I get a chance to have a play with it.

[wbosher]

Went to have a play with the laptop today but the bloody battery charger has just died on me...Grrrrrr. Oh well, it'll just have to wait. :mad::mad::mad:

[wbosher]

Oops, there's nothing wrong with charger...it was a blown fuse for the power point. :o

The good news is I got the laptop sorted. A good clean out of the registry did the trick. A bit of advice for anyone else planning a registry clean, ALWAYS back up your registry first. It can really mess up your PC, I learned that the hard way a few years back.

Anyway, I'm happy now. All is good in the world. :D:D:D