I have been pulling my hair out trying to figure out where the disconnect is in my configuration between WiRNS and Schedules Direct. I got the issues with port 80 resolved by turning off IIS in windows 10. When I installed WiRNS the port 80 test passes and the WiRNS server went Green. I have confirmed my current subscription to Schedules Direct is good and I can log in with my id and password. When I try to force a guide update it appears to go out and try to get a guide update but eventually comes back as GUIDE UPDATE COMPLETED: FAILED. The following is the log file generated from the attempt to update the guide. It looks like WiRNS is successful in logging into Schedules Direct but then fails to put the guide. I have tried turning off my firewall and I get the same results. I have tried uninstalling WiRNS and re-installing and I get the same failures to update the guide. WiRNS is picking up my 1 ReplayTV system on my local subnet. Any additional pointers would be greatly appreciated:

Thanks rmeden, I can get to the website you listed below and I can logon using my account. I have validated that I have the same information in the WiRNS configuration for Schedules Direct. I am at a loss to find what is causing the guide update to fail. Is there another way to test the connection from WiRNS to Schedules Direct?

Thanks Glen1963 that was my issue. I finally got a successful guide update. I had not added a channel lineup to my Schedules Direct account. For the benefit of others seeing this same errors in their log files. That is what it looks like when WiRNS is successfully logging into Schedules Direct but you have not added a channel lineup to your profile. The simple user's guides should be updated to add instructions to explain how to add channel lineups. The SD user interface is not that obvious and this is obviously an easy step to miss. I was focused on getting WiRNS running and that was not my issue. Some times the simple question of "is the on/off button in the on position" is all that is needed.