Server object error \'ASP 0178 : 80070005\'
Hele fejlen ---------------------------------------Server object error \'ASP 0178 : 80070005\'
Server.CreateObject Access Error
The call to Server.CreateObject failed while checking permissions. Access is denied to this object.
---------------------------------------------------
I MSDN fand jeg den som bug. Der var sagt at hvis man har installeret servispack 4 så har den lavet om på permissions instillingerne men jeg kan ikke læse mig ud af det(Hvordan man løser det) ,så jeg poster lige msdn\'s løsning.
SP. Er der en der har haft samme problem eller kan løse problemet med disse vejl.
SYMPTOMS
When you instantiate a Visual Basic component from an Active Server Pages (ASP) page, you may receive the following error:
Server object error \'ASP 0178 : 80070005\'
Server.CreateObject Access Error
The call to Server.CreateObject failed while checking permissions. Access is denied to this object.
This error may occur after you install a new Visual Basic component on your Web server using a Standard Setup Package that was created on a computer with Microsoft Visual Studio 6.0 Service Pack 4.
CAUSE
The authenticated user for the Visual Basic (VB) Runtime file (Msvbvm60.dll) does not have sufficient permissions. The authenticated user is the IUSR_computername account when you use anonymous access or the user that is authenticated with the Web page.
RESOLUTION
To resolve this problem, assign Windows NT File System (NTFS) Read and Execute file permissions to the Everyone group (or to the appropriate users) for VB Runtime (Msvbvm60.dll). VB Runtime is usually located in the Winnt\\System32 folder.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.
MORE INFORMATION
When you use the Standard Setup Package to update VB Runtime on the Web server, the setup application replaces the existing VB Runtime with the updated version when you restart your computer. In addition, the setup application replaces the NTFS file permissions for the Everyone group with the user who installs the new application. Because a Visual Basic component depends on VB Runtime, when you try to create your component, the CreateObject method fails due to insufficient permissions to VB Runtime.
