Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 728
  • Last Modified:

ACT! 2008 for Web - Server Fails To Login Remote Users - LAN Users are Working Ok

Hello eveyone,

I upgraded ACT! 2006 to 2008 for some folks that I do some side work for every now and then.  I got the software updated and working.  They have about 6 LAN users that have ACT! 2008 Premiere full version and they share the Database on their server named "Server2003"

On Server2003, I installed ACT! 2008 Premium for Web that would allow users to access the CRM software from their IE from outside of the office.  I got it up and running and it worked fine for about an hour.

After that, it started to not allow users to log in from the web GUI.  I uninstalled everything...SQL 2005, IIS 6, .NET 2, 3, ACT itself, and eveything else that I could think of.

I cleaned up the registry and got the server back to a perfect clean slate.

I reinstalled ACT! 2008 Premium for Web and the error is still happening.  Users can get to the login screen, but it errors stating that users should seek assistance from their network administrator.  We'll that's me and I don't need them calling me all day at my full time job...they don't like moonlighting (o;

So I know the following.  I set the ACT! for Web to use the default website in IIS 6.  ACT! installs a virtual directory called APFW, so I set a redirect so when the users enter http://remote.theirdomain.com it forwards the users to http://remote.theirdomain.com/APFW.

Now the users have the login GUI.  If they enter a username that isn't valid, it does check it and returns that they have entered an invalid username or password.  If they enter a valid username and password it fails with the "contact your administrator...bla bla bla."

Okay...so the Application Log on the SBS 2003 states the following 3 entries when a user attempts to log in via the web GUI.
1) Information     Date and Time            Source = AFW               Event ID = 9999        Task Category = None
2) Error               Date and Time             Source = AFW              Event ID = 1               Task Category = None
3) Warning          Date and Time             ASP.NET 2.0.50727.0   Event ID = 1309         Task Category = 3

Error #2 includes:
The following information was included with the event:
error occured on pageAct.Web Message:Method not found: 'UInt32 Act.ProtexisProvider.ProtexisProvider.GetAllowedRedstoneUserCount()'.


Error 3 includes:
3005
An unhandled exception has occurred.
12/2/2007 10:15:55 PM
12/3/2007 3:15:55 AM
91aa81eb965546a99969ecd3263e4c6c
9
6
0
/LM/W3SVC/1/Root/APFW-4-128411248036250000
Full
/APFW
C:\Program Files\ACT\Act for Web\APFW\
SERVER2003
3432
w3wp.exe
NT AUTHORITY\NETWORK SERVICE
MissingMethodException
Method not found: 'UInt32 Act.ProtexisProvider.ProtexisProvider.GetAllowedRedstoneUserCount()'.
http://remote.theirdomain.com/apfw/default.aspx?error=true
/apfw/default.aspx
65.12.148.35
False
TheirDomain\Administrator
5
TheirDomain\Administrator
False
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Act.Web.Licensing.ConcurrentLicensing.AddUser(String user, String db)
   at Act.Web.loginPage.logonButton_ServerClick(Object sender, EventArgs e)
   at System.Web.UI.HtmlControls.HtmlButton.OnServerClick(EventArgs e)
   at System.Web.UI.HtmlControls.HtmlButton.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.HtmlControls.HtmlButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)



PLEASEEEEEEEEEEEE shed some light on this so I can fix it!!!
You guys are the best and I think we can do it.

inverted
0
inverted_2000
Asked:
inverted_2000
  • 3
  • 3
  • 2
  • +1
1 Solution
 
surajgupthaCommented:
Here's a guess. When you installed your new software, it tweaked ur IIS server and even though u uninstalled it, the tweal continues to be. Try uninstalling the IIS if it doesnt host any other applications. and make sure you remove all the details that may exist about the IIS that may remain even after removing it and then my guess is that it should work fine....
0
 
inverted_2000Author Commented:
I figured that there is something that is remaining...but I did uninstall IIS completely..along with ASP.NET versions, installer files, common files, everything that I could think of.

Now that I'm looking at these log files, in error #3...it states "w3wp.exe" which is something that was popping up after the server rebooted and the users started to not be able to log in.  The error stated that there was something wrong with "w3wp.exe" worker process.  After uninstalling everything...I do not see that error any longer...but it is in the log file.  This has something to do with the virtual directory that it created...and the application pool that it's using...but I don't really know where to start working at it.

I do have a 30 day free support for new installs.  I'll call them at lunch and post back.

Thanks,
inverted
0
 
surajgupthaCommented:
yeah #3 clearly suggests that IIS has been tampered with. Talk to the support guys and let us know...
0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
inverted_2000Author Commented:
Yup...error #3 had the error:

"ProtexisProvider" was looking at the old licensing assembly that wasn't cleared out with the upgrade from 2006 to 2008.  

The old version on the server was the full desktop version, and not the Web server version...but it messed it up anyway.

I have to uninstall, clear the assemblies from the server...and delete the registry entries to the assembly.  Even though I cleared the registry before my last attempt to fix...the old assemblies were still available.

This is basically a licensing issue where ASP isn't calling the correct licesning assembly version.

Thanks for trying any way surajquptha.

inverted
0
 
surajgupthaCommented:
you are welcome.. Best of luck :)
0
 
Mike LazarusAct! Evangelist - CRM ConsultantCommented:
Protexis is the licensing module.

Have you got it working?

If not, what happens if you log in from the full ACT! client... either on the server or on a LAN workstation pointing to the server?
0
 
inverted_2000Author Commented:
Thanks GLC...I did like I stated I had to do above and it worked:

"I have to uninstall, clear the assemblies from the server...and delete the registry entries to the assembly.  Even though I cleared the registry before my last attempt to fix...the old assemblies were still available."


0
 
Mike LazarusAct! Evangelist - CRM ConsultantCommented:
No probs... glad you got it working
0
 
modus_operandiCommented:
Closed, 500 points refunded.
modus_operandi
EE Moderator
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now