just switched to 2003 server... can't deploy

I get this message when trying to run one of my apps that has worked fine on 2000 pro (iis 5.0). Do I need to locate/download or do something with the adodb.dll file?

Quote:

---

Server Error in '/cpthandler/procUpload' Application.
--------------------------------------------------------------------------------

File or assembly name ADODB, or one of its dependencies, was not found.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: File or assembly name ADODB, or one of its dependencies, was not found.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'ADODB' could not be loaded.


=== Pre-bind state information ===
LOG: DisplayName = ADODB, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
(Fully-specified)
LOG: Appbase = file:///D:/WebServer/cpthandler/procUpload
LOG: Initial PrivatePath = bin
Calling assembly : procUpload, Version=1.0.1987.26433, Culture=neutral, PublicKeyToken=null.
===

LOG: Publisher policy file is not found.
LOG: No redirect found in host configuration file (C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet.config).
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\config\machine.config.
LOG: Post-policy reference: ADODB, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/cpthandler_procupload/01435d9f/5c1484da/ADODB.DLL.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/cpthandler_procupload/01435d9f/5c1484da/ADODB/ADODB.DLL.
LOG: Attempting download of new URL file:///D:/WebServer/cpthandler/procUpload/bin/ADODB.DLL.
LOG: Attempting download of new URL file:///D:/WebServer/cpthandler/procUpload/bin/ADODB/ADODB.DLL.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/cpthandler_procupload/01435d9f/5c1484da/ADODB.EXE.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/cpthandler_procupload/01435d9f/5c1484da/ADODB/ADODB.EXE.
LOG: Attempting download of new URL file:///D:/WebServer/cpthandler/procUpload/bin/ADODB.EXE.
LOG: Attempting download of new URL file:///D:/WebServer/cpthandler/procUpload/bin/ADODB/ADODB.EXE.



Stack Trace:


[FileNotFoundException: File or assembly name ADODB, or one of its dependencies, was not found.]
procUpload.procUpload.Page_Load(Object sender, EventArgs e) +0
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +731

---

It was very important to upgrade to the latest release of MDAC before Win 2003...

If not problems arise...

Look at this thread - there are links to MSDB KB articles about this.

http://www.vbforums.com/showthread.p...ight=2003+mdac

HTH

Install MDAC on the deployment machine.

Quote:

---

Originally Posted by mendhak

Install MDAC on the deployment machine.

---

If MDAC was installed already, there are KB articles to help unravel the registry error...

So be careful...

Thanks guys! I wish I woulda thought of that stuff yesterday. :(

I'll get on that right away!

thanks thanks thanks :wave:

So... it seems it would probably be easiest for me to update MDAC on my 2000 and 2003 systems and then "re-migrate" my apps from the 2000 system...

How does that sound?

It's a problem with the registry on the win2003 machine - if you did not upgrade to MDAC 2.8 prior to the win2003 upgrade.

So a re-install of MDAC might not take care of it.

The win2003 install was a full installation, not an upgrade... it was installed in a freshly formatted drive. But, the applications I need to bring over are from a 2000 system.

So, you're right, re-installing MDAC didn't take care of it, I'll keep reading ms docs for now... :confused:

Ok... I haven't really gotten anywhere with this. I don't get it... does this mean that my applications that were developed on a win2000 Pro system CANNOT be deployed to a win2003 server system???

This MS TechNet site has helped me before with complex problems...

Give them a try:

http://www.microsoft.com/sql/communi...lserver.server

[edit] new url...

http://www.microsoft.com/technet/com...lserver.server

Ok, through many combinations of reinstalling MDAC and such on my win2000 pro and win2003 systems, the adodb.dll error has ceased :thumb:

Now I'm getting new message that isn't particularly helpful (no line numbers)...

This seems to be a step in the right direction though. I guess I need some guidance when it comes to deploying .NET web applications. In the past, I had VS .NET installed on my deployment server and would simply copy my web app over to the server and compile it in VS .NET. Unfortunately since VS .NET cannot be installed on win2003 (that's what the installer told me anyway), I can't do that. Does anyone have any good tips or links for me?

current error:

Quote:

---

Server Error in '/cpthandler/procUpload' Application.
--------------------------------------------------------------------------------

Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[NullReferenceException: Object reference not set to an instance of an object.]
procUpload.procUpload.Page_Load(Object sender, EventArgs e) +12181
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +750




--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300

---

I know that "Object reference..." error is sort of a newb error but, I'm having a lot of trouble tracking it down. Anyone know how I can pinpoint a line number or get help from the stack trace?

thanks