Re: [IMail Forum] Imail 2006 upgrade nightmare!

Sun, 04 Dec 2005 13:28:53 -0800

This is the code where the admin is determining what products are installed on the box and is using files from the ig_common virtual directory.  That's why I asked if this virtual directory showed up in your IIS.
 
Tripp
 
----- Original Message -----
Sent: Sunday, December 04, 2005 3:54 PM
Subject: Re: [IMail Forum] Imail 2006 upgrade nightmare!

OK, translate that into something even I can understand. 
 
What are you saying might be the problem? 
 
Thanks,
-Joe
----- Original Message -----
Sent: Sunday, December 04, 2005 2:04 PM
Subject: RE: [IMail Forum] Imail 2006 upgrade nightmare!

 
Looking at the file and the line from the error message below I can see
 
  oProducts = Server.CreateObject("IpsGlobal.IpswitchProductCollection.1");
 
So it shouldn't be a problem with MDAC, the Filesystemobject or anything else what is part of your OS.
Looks more like it's not possible to create an instance of Ipswitch's component.
 
Markus
 
 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Wolf / Internet Specialists
Sent: Saturday, December 03, 2005 5:35 PM
To: [email protected]
Subject: [IMail Forum] Imail 2006 upgrade nightmare!

I decided to try and go forward with the 2006 upgrade today.  Nothing has worked as planned (of course).
 
First problem is that Imail won't activate my license.  Even the manual process doesn't work.  But this is not my major problem.
 
Big problem is trying to run Iadmin.  The Iclient runs fine, but when I try and run Iadmin I get the following error:
 
Server object error 'ASP 0177 : 800401f3'
 
Server.CreateObject Failed
 
/iadmin/includes/ApplicationContext.asp, line 173
 
800401f3
 
Server is running Windows 2003 Server.  Very stable box. 
 
I can log on to the web client just fine and everything seems to work, but I really need to access iadmin to configure the system!
 
Any help or suggestions would be greatly appreciated.  I've run the setup at least 4 times with varying results.
 
-Joe

Reply via email to