I'm getting
Error Type:
Server object, ASP 0177 (0x800401F3)
Invalid class string
/ErrorProcess.asp, line 64
error while I try to run my project in ASP.NET. I've registered all the necessary DLLs but it is not working.
Do I have to restart my machine after registration? or is there any other problem?
In the asp.net you need not to register dll. You can add reference of dll and use it. Right click on asp.net project and click on "Add Reference" and add the dll reference. Then you can use it.
Related
I have an old site that I was tasked with fixing after it broke. We are getting the following error:
ActiveX component can't create object for aBRR.Generato`r
The code on that line is:
set taMaker = createObject("aBRR.Generator")
I found the DLL aBRR.dll on an old machine. I believe it needs to go in:
e$\components\COM+\theAppName\
To install it in the COM+ folder do I just drop it in there? Is there anything else?
Do I just add the IUSR with what permissions to the DLL?
I think that was done but it's still giving the error.
If it's a classic COM DLL, you simply need to register it with regsvr32.
However, if the library depends on COM+, you need to place it inside a COM+ application. That way, any call to createObject() gets intercepted by the COM+ catalog manager, which ensures that that the object receives additional services.
See this link for further details.
I am facing a peculiar issue where my deployed code works as expected on IIS10 on my machine. However on a separate server with IIS6 it produces an error .
Parser Error Message: Could not load type 'Namespace.Global'
So far I have done the following checks
Ensured that the Namespace in the Global.asax is the same as the Project Namespace
Global.asax properties set to "Build Action : Content" and Copy to Output
Directory: always
I have also tried the suggestions from the following posts but I havent found any successs
Parser Load Error
Could not Load Type from Global.asax
Could Not Load Type 'MyNameSpace.Global
Global.asax contents
<%# Application Codebehind="Global.asax.vb" Inherits="Namespace.Global" %>
Any suggestions ?
Resolved it , the application was compiled on .NET framework 4.0 on my machine and the website on IIS 6 was configured on .NET Framework 1.xx .
After setting the configuration in the Website to .NET 4.0, the issue no longer appeared.
Hope this helps someone :)
I'm using Classic ASP.
Set theForm = Server.CreateObject("Persits.Upload")
theForm.OverwriteFiles = True
Running the above code produces the error:
Server object error 'ASP 0177 : 800401f3' Server.CreateObject Failed
How can I solve this?
Unregister the Persits Upload DLL and re-register it by using regsvr32. below are the steps to register and unregister the DLL
Registering a DLL
regsvr32 <filename>.dll
or
regsvr32 <path>\<filename>.dll
where is the path to the file, and is the name of the file.
Unregistering a DLL
regsvr32 -u <filename>.dll
or
regsvr32 -u <path>\<filename>.dll
In Classic ASP I was getting this error when the code was moved to a new server. From my little experience with Classic ASP it looked like another DLL registration issue. In my case was the DLL was missing, so it couldn't have been registered. Once it was registered it fixed the problem.
Here is a list of items to check:
You really didn't run regsvr32 on the server after all.
You ran regsvr32 but it reported an error.
Someone modified security on part of the registry that's preventing the OLE subsystem from reading all or part of the HKEY_CLASSES_ROOT tree.
The name of the object you are trying to create was mispelled or is incorrect.
Determine if it's a permissions problem
Here are is a link for more information:
Using the correct version of MSXML
Comprehensive Check-list I posted here
Error ASP 0177: 8007007e Server.CreateObject fails for COM DLL
Deals with the issues of registering DLLs for use in Classic ASP for both 32 and 64 bit and common problems encountered.
Would post it here but don't want to duplicate the answer.
I have big trouble deploying my webservice. It is the basic helloWorld start webservice.
At my localhost everything os ok. But when I copy the service to my server in my virtual directory i recieve this error:
Server Error in '/' Application.
Parser Error Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not create type 'Service'.
Source Error: Line 1: <%# WebService Language="vb" CodeBehind="~/App_Code/Service.vb" Class="Service" %>
Source File: /customers/iv_webservice/Service.asmx Line: 1
Version Information: Microsoft .NET Framework Version:2.0.50727.4952; ASP.NET Version:2.0.50727.4955
Now I have tried almost everything. Including scanning the web for the past 9 hours for an answer.
I know my virtual directory in the web.config is ok, since I have other virtual websites on my server. I even manage to have aspx. files in the same directory and they are ok.
Now, what am I missing?
Does your web service use a 3rd party assembly or unmanaged Dll that is not deployed to the server? In my experience "cannot create object of type" errors are missing unmanaged Dlls. In the case of missing managed assemblies, the error will usually tell you which assembly is missing.
Can you try compiling the service.vb as an standalone assembly? That might help understand any dependencies you might not be satisfying.. You might also see additional information in Event viewer or if you set the debug mode to true in web.config to see if there are any errors reported compiling service.vb.
I'm receiving the following error when deploying a feature containing ASP.NET pages to our development SharePoint servers:
System.InvalidOperationException: The type specified in the TypeName property of ObjectDataSource 'odsYears' could not be found.
Our .dll is being deployed to the GAC and our pages are being deployed to the the respective Features directory in the 12 hive. We are not receiving this error on our Sandbox SharePoint server. I disassembled the .dll to be sure the class was being deployed and everything looked ok.
Does anyone have any ideas on why this would not work on one of our SharePoint environments?
Thanks.
Found the error, I needed to add a reference to our .dll in the "assemblies" node of the SharePoint web.config file - in case anyone else comes across this.
ObjectDataSource is by default disabled in the SafeControls section of the web.config.