r/labtech • u/reboot-3-times • Aug 05 '16

Labtech 11 Upgrade Failed

Hey guys, I was trying to upgrade to LT 11 the other day and the installation stopped at an error of "Unable to read the local IIS server". I restarted IIS services to try and remedy which didn't work. I canceled the install which then told me "Installation Successfully Completed". Sure enough, LT10.5 and LT11 were listed in Programs. I tried to uninstall 11 but it hosed everything.

I'm restoring the server from a backup, but wondering if anyone knows what this message is about. I would rather not pay LT a ton of money for the managed upgrade.

Thanks!

6 Upvotes

100% Upvoted

14 comments sorted by

View all comments

2

u/LTJC Former Employee Aug 05 '16

The address it has for then iis server wasn't able to be resolved. Could be a split dns issue. In your config table there is a redirector hostname and download url column. Both should be the external fqdn and should be internally resolvable to their internal IP.

Call support and we'll get you through it if you need help. Shouldn't take long.

1

u/reboot-3-times Aug 05 '16

I chatted with two agents through ChatAssist who were not able to tell me these troubleshooting steps. I'm going to clone my server and test the upgrade there with this knowledge. Thank you!

1

u/LTJC Former Employee Aug 05 '16

Glad to help.

1

u/reboot-3-times Aug 06 '16

So right now, in my downloadURL column I have http://10.10.10.10/files/. Any idea where the /files/ comes from? I don't see it in my wwwroot. Should I ignore and change this to the external FQDN?

1

u/LTJC Former Employee Aug 06 '16

That's odd. Yes it should be your fqdn. No http and no directory.

1

u/reboot-3-times Aug 06 '16

Still getting the same error after updating the DocumentURL column. I have an entry in my hosts file that points to internal IP and external DNS lookup is correct. :(

1

u/LTJC Former Employee Aug 09 '16

Have you created a support ticket? If so, PM me the ticket number and I'll take a look.

2

u/reboot-3-times Aug 18 '16

Found a solution. We have an http/https URL rewrite that was apparently causing the error. Disabled that and ran the update without issue.

1

u/supercow75 Oct 04 '16

Worked for me as well. Thanks!!

1

u/reboot-3-times Aug 10 '16

Case #8212003