S
Seth Darr
I'm working on migrating an Classic ASP/VB6 COM application from an NT
Server with IIS<6 to an virtual machine running Windows Server 2003 and
IIS 6. I've worked through most of the obvious problems resulting from
IIS 6 prohibiting ASP and SSI etc, but I've hit a peculiar wall.
One ASP page uses a VB6 COM object that basically reads from an .INI
file and uses it to open another file. The existing code uses this line
(in VB6) to do this:
Open "UpLoad.ini" For Input As #1
This works fine in the existing setup, but on the new box it returns a
"File Not Found" error at this line. If I hard code a path in there
(i.e. "C:\temp\Upload.ini") it will work, but I don't want to do that.
So my question is, why isn't this working? It should be trying to read
UpLoad.ini from the same directory that the .dll file is registered in,
right? (in this case, C:\WINDOWS\System32) Is it a permissions issue?
I've tried giving IUSR_* and SYSTEM accounts read/write access to that
folder (against my better judgement) as well as to the folder the code
is ultimately going to write to (that's a whole other, but perhaps
similar, ball of wax).
So does this ring bells for anyone? Any help would be greatly appreciated.
-Seth
Server with IIS<6 to an virtual machine running Windows Server 2003 and
IIS 6. I've worked through most of the obvious problems resulting from
IIS 6 prohibiting ASP and SSI etc, but I've hit a peculiar wall.
One ASP page uses a VB6 COM object that basically reads from an .INI
file and uses it to open another file. The existing code uses this line
(in VB6) to do this:
Open "UpLoad.ini" For Input As #1
This works fine in the existing setup, but on the new box it returns a
"File Not Found" error at this line. If I hard code a path in there
(i.e. "C:\temp\Upload.ini") it will work, but I don't want to do that.
So my question is, why isn't this working? It should be trying to read
UpLoad.ini from the same directory that the .dll file is registered in,
right? (in this case, C:\WINDOWS\System32) Is it a permissions issue?
I've tried giving IUSR_* and SYSTEM accounts read/write access to that
folder (against my better judgement) as well as to the folder the code
is ultimately going to write to (that's a whole other, but perhaps
similar, ball of wax).
So does this ring bells for anyone? Any help would be greatly appreciated.
-Seth