| :: CreateObject Error :: (10) | Post a New Message | Post a Reply |
 CreateObject Error | Post a Reply |
from: Kenosha, WI
Here is the error
Server object error 'ASP 0177 : 800401f3'
Server.CreateObject Failed
/reportwriter/default.asp, line 17
800401f3
 Re: CreateObject Error | Post a Reply |
from: Washington, DC
Windows 2003 has ASP disabled by default - make sure you enable it. Also make sure that you give the necesary rights to IIS for AWSReportWizard2.dll. because by default, almost no user has permission/rights to access components on Win2k3
-------------------------
Ghost
| Re: CreateObject Error | Post a Reply |
from: Kenosha, WI
<%
'TODO: Change the constants below to reflect your database settings
Const SERVER_NAME = "BENDER"
Const DATABASE_NAME = "hcs"
Const USER_NAME = "hcs"
Const PASSWORD = "client"
'declare your variables
Dim objWiz, strConnectionString
'initialize your variables
strConnectionString = "Provider=MSDASQL;Driver={SQL Server};"& _
"Server= "& SERVER_NAME & ";Database= "& DATABASE_NAME & ";"& _
"User ID= "& USER_NAME & ";Password= "& PASSWORD & ";"
Set objWiz = Server.CreateObject("AspWebSolution.ReportWizard2")
'Make sure you initialize before adding any HTML text
objWiz.Init(strConnectionString)
'put this where you want your reports
objWiz.DisplayReports
Set objWiz = Nothing
%>
| Re: CreateObject Error | Post a Reply |
from: Laurel, MD
If you belive that you should have access rights to using this object, then try reinstalling the Report Wizard again. Sometimes a simple rebooting of server can solve the problem
-------------------------
Master of the Game
| Re: CreateObject Error | Post a Reply |
from: Kenosha, WI
Thanks
| Re: CreateObject Error | Post a Reply |
from: Kenosha, WI
 Re: CreateObject Error | Post a Reply |
from: Washington, DC
Have you tried installing it on another server?
-------------------------
Ghost
| Re: CreateObject Error | Post a Reply |
from: Kenosha, WI
| Re: CreateObject Error | Post a Reply |
from: Washington, DC
1. Uninstal the AspReport Wizard v2 completely.
2. Make sure that you do not have the AWSReportWizard2.dll file anywhere on your computer
3. Make sure that the following registry keys have been deleted
HKEY_CLASSES_ROOT\AspWebSolution.ReportWizard2
HKEY_CLASSES_ROOT\AspWebSolution.SimpleGraph
HKEY_CLASSES_ROOT\AspWebSolution.StringBuffer
HKEY_CLASSES_ROOT\AspWebSolution.DataGrid
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AspWebSolution.DataGrid
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AspWebSolution.SimpleGraph
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AspWebSolution.StringBuffer
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AspWebSolution.DataGrid 4. Restart your server and login as an administrator.
5. Install the latest copy of the report wizard v2.4.62
6. Restart your server and try running your reports.
-------------------------
Ghost
| Re: CreateObject Error | Post a Reply |
from: Laurel, MD
CreateObject Error means "Invalid class string" -- in other words the call to CreateObject failed because the name object cannot be found by the OLE sub-system. Causes include:
- 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
Add the anonymous user (used by IIS) to the Administrators group. The test page then worked, proving it was a permissions problem. Do not forget to remove the anonymous IIS user from the Admin group!
- Determine if it is a file permissions problem:
After removing the Anonymous user from the Admin group, add failure auditing to the file (smtpsvg.dll), which will determine if the file was ever accessed (by the lack of the failure event). If it isn't, this makes it clear that the failure is prior to file access but go ahead and check file/directory permissions to make sure the anonymous IIS user can access the file.
- Check registry permissions
Using Regedt32, do find on smtpsvg.dll. Check the permissions for the key (and sub keys), and make sure that the anonymous user has read rights. Do a find on the class-id, which contains the location value, and version, and check those permissions as well.
-------------------------
Master of the Game