Asked By
mattewgems
1300 points
N/A
Posted on - 06/26/2011
Hi all,
When i was installing Visual Studio 2005 after I installed SQL, I meet an error that I posted below for complete reference.
Sybase DataWindow Designer 2.5 Error
Error 1904.Module C: Program FilesSybaseDataWindow Designer
2.5DWPainter.dll failed to register. HRESULT -2147220473. Contact
your support personnel.
What I was doing before I meet this error is, I installed DataWindow .NET 2.5 with Visual Studio 2005, DataWindow .NET 2.5 with Visual Studio 2008. The installation process went without any errors and the status message tells that, it is now registering Datawindow .net components. This process proceeds to finish without any error. After the installation of the module DataWindow .NET 2.5 with Visual Studio 2005 registering components, the above mentioned error appears.
I am now wondering on where this error came, does it from my installation package or somewhere else. Please share some ideas for those who have faced this error.
Thanks.
Answered By
rpesado
0 points
N/A
#122895
Sybase DataWindow Designer 2.5 Error
Hi Mattew!
You can try either of the following. By the way, you did the right thing by installing the SQL Server 2005 first before installing the Visual Studio 2005.
Â
Use an SSL certificate for SQL Server 2005 and Reporting Services and also the following:
-
Run the Windows Service under NT AUTHORITYSYSTEM (XP & 2000)
-
Run the Windows Service under NT AUTHORITYNETWORK SERVICE (2003)
-
Use a Domain Account for the services to access SQL Report Database
-
Internet Information Services (IIS) must be installed first, set to automatic and running before installing the reporting services portion of Visual Studio 2005. Â It will be grayed out and not selectable if IIS is not present
If you're using XP for IIS Connections, it might be limited to 10 only. Do not go beyond 40, it will go back to the default which is 10. Here's how to do it:
Â
Go to command prompt > type CScript.Exe C:InetpubAdminScriptsadsutil.vbs set w3svc/MaxConnections 40
Â
Note: Adjust your path also if IIS was installed in another location.
Â
Hope you'll find this useful in solving your problem.
