Jump to content

Error opening xml file (Searches brought nothing)


Recommended Posts

When executing this code

;______________________________Get the xml file

InetGet("http://etiportal.suntrust.com/sites/CTS/Non%20Branch%20Server%20Backup%20Verification%20Log/FL032F39.xml", "FL032F39.xml", 1, 1)

I get this error twice

AutoIt3.exe - Entry Point Not Found

The procedure entry point GetProcessImageFileNameW could not be located in the dynamic link library PSAPI.DLL.

The XML file does download but I need to get past these errors.

Thanks

Edited by dcjohnston
Link to comment
Share on other sites

From: http://pointerx.net/blogs/glozano/archive/...-PSAPI.DLL.aspx

"This usually indicates that there are several versions of the PSAPI.dll installed on your system and that the application that you are trying to run uses an old PSAPI.dll that if found somehwere in one of the reference paths. To make sure that the application uses the latest installed PSAPI.dll you should delete all PSAPI.dll files on your system EXCEPT for the latest version which should reside in the SYSTEM32 folder of your WINDOWS dir."

[font="Fixedsys"][list][*]All of my AutoIt Example Scripts[*]http://saneasylum.com[/list][/font]

Link to comment
Share on other sites

From: http://pointerx.net/blogs/glozano/archive/...-PSAPI.DLL.aspx

"This usually indicates that there are several versions of the PSAPI.dll installed on your system and that the application that you are trying to run uses an old PSAPI.dll that if found somehwere in one of the reference paths. To make sure that the application uses the latest installed PSAPI.dll you should delete all PSAPI.dll files on your system EXCEPT for the latest version which should reside in the SYSTEM32 folder of your WINDOWS dir."

You are correct. The version in the Autoit3 directory was an older version than the one found in Winnt. I replaced the Autoit3 with the new one and all is well.

Thanks for the assist.

Link to comment
Share on other sites

Why bother replacing PSAPI.dll? Windows will search along the path for it, will it not? Simply erase all other copies ... only leaving the one in the System folder.

Oh, and that was a definate case of "DLL Hell"

Edited by Blue_Drache

Lofting the cyberwinds on teknoleather wings, I am...The Blue Drache

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...