/bbs/bbs/test.asp, 第 4 行 是什么
Inability to Create Components
Common Symptoms
Server.CreateObject fails with an ASP 0177: Server.CreateObject Failed error.
The component works fine on the same machine from Visual Basic or from some other tool.
The component works fine with ASP on other machines.
Description
Other permission problems occur when ASP tries to create server-side components. The causes, symptoms, and debugging techniques are very similar to the previous discussion. The problems arise because the authenticated user does not have permission to invoke the COM object. In the simplest scenario, the authenticated user doesn't have access to the component's .dll or .exe file. In many cases, however, the component depends on other DLLs which the authenticated user does not have access to. Debugging Techniques
Although giving the IUSR_MACHINE account administrative permissions is useful in this scenario, a better first step is to invoke the component from some other tool such as Visual Basic. This approach is preferred because it checks for permission problems, as well as verifying that the component is registered properly on the server. If the component cannot be created from Visual Basic, you are probably not dealing with a permissions problem at all.
If you believe you are dealing with a permissions problem, check permissions on the component and any dependent files such as other DLLs.
If you still are unable to track down the problem, you may need to resort to other means such as a systematic permissions search, or Windows NT File and Object Auditing.
While the previous sections only touch on the most common permissions issues, I hope that you have gained an appreciation for the types of problems that are caused by permissions and other security settings. With an understanding of authentication and a few debugging tools at your disposal, you should be able to work through any permissions problem that comes your way.
Inability to Create Components
Common Symptoms
Server.CreateObject fails with an ASP 0177: Server.CreateObject Failed error.
The component works fine on the same machine from Visual Basic or from some other tool.
The component works fine with ASP on other machines.
Description
Other permission problems occur when ASP tries to create server-side components. The causes, symptoms, and debugging techniques are very similar to the previous discussion. The problems arise because the authenticated user does not have permission to invoke the COM object. In the simplest scenario, the authenticated user doesn't have access to the component's .dll or .exe file. In many cases, however, the component depends on other DLLs which the authenticated user does not have access to. Debugging Techniques
Although giving the IUSR_MACHINE account administrative permissions is useful in this scenario, a better first step is to invoke the component from some other tool such as Visual Basic. This approach is preferred because it checks for permission problems, as well as verifying that the component is registered properly on the server. If the component cannot be created from Visual Basic, you are probably not dealing with a permissions problem at all.
If you believe you are dealing with a permissions problem, check permissions on the component and any dependent files such as other DLLs.
If you still are unable to track down the problem, you may need to resort to other means such as a systematic permissions search, or Windows NT File and Object Auditing.
While the previous sections only touch on the most common permissions issues, I hope that you have gained an appreciation for the types of problems that are caused by permissions and other security settings. With an understanding of authentication and a few debugging tools at your disposal, you should be able to work through any permissions problem that comes your way.
解决方案 »
免费领取超大流量手机卡，每月29元包185G流量+100分钟通话, 中国电信官方发货