SmarterTrack as IIS Server

[Guardall]

Can anyone help with a persistant problem? I am trying to change my SmarterTrack installation to operate under Port-80 on the domain, rather than the default Port-9996.

I have followed the instructions in SmarterTools.Com Knowledge Base on setting the package up as an IIS instance, to work directly on the domain. It does not seem to work, I get tons of errors relating to scripts, security settings, pages not available etc...

I would normally be happy to just leave SmarterTrack running on Port-9996, but my corporate Firewall blocks it and cannot be changed.

My actions:

1. Login to my VPS using Remote Desktop
2. Using the Control Panel for IIS, create a new Application Pool
3. Create a New Website, using this newly added Application Pool
4. Modify the website settings, to point to SmarterTrack default directory
5. Disable (Stop) the existing Web and Application Pool.

I cannot see where I am going wrong. One obvious question: Could I just un-install SmarterTrack and re-install? Does the installation Wizard allow for settings to create as an IIS instance, on Port-80. Or am I going to have to figure this one out the hard way?

I am totally new to all of this, and would appreciate any help you can give.

Thanks in advance.

Kevin

[Rock]

Hi Kevin,

To allow SmarterTrack to run on port 80, IIS needs to be stopped/disabled completely. Only one service runs on a port at a time & these are two different services. SmarterTrack uses its own web server hence if you try to run IIS & SmarterTrack webserver simultaneously, they'd conflict for sure..

[Guardall]

Just to update this post for anyone with similar issues. I managed to stop the IIS applications, and get SmarterTrack to operate on Port 80. However I was then getting Runtime Errors when accessing the Domain.

The issue here was the version of ASP.NET that was defaulted to v1 when a new Website is linked to an Application Pool. Needs to be changed to at least v2, then the error goes away.

Thank you for your support this this however, as always prompt and efficient.

Kevin

[Rock]

Just to update this post for anyone with similar issues. I managed to stop the IIS applications, and get SmarterTrack to operate on Port 80. However I was then getting Runtime Errors when accessing the Domain.

The issue here was the version of ASP.NET that was defaulted to v1 when a new Website is linked to an Application Pool. Needs to be changed to at least v2, then the error goes away.

Thank you for your support this this however, as always prompt and efficient.

Kevin

You're most welcome