Destiny Amana
asked on
Server throws an error on file script object in ASP
I have an application that uploads a file and then reads the file into an address book.
It has been recently moved from a windows 2003 server to a windows 2008 server and since the move, the server throws an error when ever we try to make it read a file
' Instantiate the FileSystemObject
Set objFSO = Server.CreateObject("Scrip ting.FileS ystemObjec t")
' use Opentextfile Method to Open the text File
Set TS = objFSO.OpenTextFile(strFil eName, ForReading, Create)
What could be the problem?
It has been recently moved from a windows 2003 server to a windows 2008 server and since the move, the server throws an error when ever we try to make it read a file
' Instantiate the FileSystemObject
Set objFSO = Server.CreateObject("Scrip
' use Opentextfile Method to Open the text File
Set TS = objFSO.OpenTextFile(strFil
What could be the problem?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will upload the script for checking now.
uploadprocess2.txt
uploadprocess2.txt
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok, We installed ASPupload 32bit vesion on our 64bit Windows 2008 Server.
But when I just tried the test script provided, we get this error message
So, how do we get IIS to execute this 32bit software
Screen-Shot-2014-01-29-at-6.06.3.png
Screen-Shot-2014-01-29-at-6.10.0.png
But when I just tried the test script provided, we get this error message
So, how do we get IIS to execute this 32bit software
Screen-Shot-2014-01-29-at-6.06.3.png
Screen-Shot-2014-01-29-at-6.10.0.png
http://www.aspupload.com/faq.html
Microsoft VBScript runtime error '800a01ad'
ActiveX component can't create object
A. It is a permission problem. Make sure Everyone has Full Control over AspUpload.dll.
Microsoft VBScript runtime error '800a01ad'
ActiveX component can't create object
A. It is a permission problem. Make sure Everyone has Full Control over AspUpload.dll.
ASKER
The Problem was in the App pool management, enabling 32 bit applications to run on a virtual directory on a 64 bit installation of IIS. In the end, we installed both 32 and 64 bit license of ASPUpload and checked all permissions again
Chris