J
Jack Wright
Dear All,
At some customers we are facing a problem when the user tries to
launch any aspx page from IE. We are getting "Compiler failed with
error code 2000". Is this bcos of some missing resource?
I read in the newgroup that said:
1. Re-install IIS ( I applied Windows 2000 SP3 after that)
2. Register Aspnet_isapi.dll as described in Q306005. (this is
actually not needed)
One more Observation I made was that the length of the Virtual Name
of the directory where the deployment is should not exceed more than 8
characters. What is the maximum length of the Virtual name in IIS?
I changed <NtfsDisable8dot3NameCreation> in the registry to <1>
but I still get the compliation error if the length is greater than 8.
Is there some other solution? Has something changed in the registry?
Can we use the <Compile> tag in Web.Config to overcome this error?
Please help
TALIA
Many Regards
Jack
At some customers we are facing a problem when the user tries to
launch any aspx page from IE. We are getting "Compiler failed with
error code 2000". Is this bcos of some missing resource?
I read in the newgroup that said:
1. Re-install IIS ( I applied Windows 2000 SP3 after that)
2. Register Aspnet_isapi.dll as described in Q306005. (this is
actually not needed)
One more Observation I made was that the length of the Virtual Name
of the directory where the deployment is should not exceed more than 8
characters. What is the maximum length of the Virtual name in IIS?
I changed <NtfsDisable8dot3NameCreation> in the registry to <1>
but I still get the compliation error if the length is greater than 8.
Is there some other solution? Has something changed in the registry?
Can we use the <Compile> tag in Web.Config to overcome this error?
Please help
TALIA
Many Regards
Jack