Utility: Vista Sidebar Gadget

[cncb]

Originally Posted by wayner

I see that the sage.js file has variables for the Sage Install Dir, Sage EXE, Client EXE, Sage reg settings, etc.

These are only for the action taken when clicking on the SageTV logo and have no effect on the gadget's connection to the server.

[JerryB]

I just installed the Internet Explorer 9 beta and now the SageTV gadget appears to have permanently lost it's connection to the server. It's stuck on NA-Check network connection, server, and settings.

I don't know what is causing the failure of the gadget to see the server. I can ping the server from the machine and can load the SageTV WebServer in IE 9 without any problems.

Just to be clear, I'm not complaining or asking for support. I don't expect your or anyone else's software to necessarily work with beta software and currently have IE 9 installed on a test machine, not my production computer, so this issue doesn't really affect me at the moment. I just wanted to let you know about the potential for an incompatibility issue as IE 9 progresses through beta to release.

[wayner]

I am having a similar problem. Everything works fine to connect to my Sage6 server but when I change the settings to my Sage7 server I keep getting the error. I have turned off the password requirement with the SageWeb server so I am pretty sure it is not an authentication problem.

Is there any log I can check to troubleshoot this? I see the request coming in to the jetty log but it doesn't really tell anything useful except that I see that a HTTP GET request (or something like tthat) was received.

[gplasky]

Do you have the Sage 7 Web server running on your SageTV 7 install? And can you log into it? If that works then the gadget should work. I have mine working on Sage 7 on a Win 7 client both with and without SageTV 7 client installed on it. If you're using the correct password it should just work. Also make sure all the .NET prerequisites are installed on that PC.

Gerry

[JerryB]

Originally Posted by gplasky

Do you have the Sage 7 Web server running on your SageTV 7 install? And can you log into it? If that works then the gadget should work. I have mine working on Sage 7 on a Win 7 client both with and without SageTV 7 client installed on it. If you're using the correct password it should just work. Also make sure all the .NET prerequisites are installed on that PC.

I don't know if this comment was directed at me or not but, in case it was, I do have Sage 7 Web server running on my SageTV 7 install, I can log into it without difficulty, and all .NET prerequisites are installed. I've had a version of the SageTV gadget running on my test computer since v1.0 (currently v1.4) and it was working perfectly right up until the moment I installed the IE 9 beta. It stopped working upon rebooting the computer at the conclusion of the IE9 beta install and has not worked since which leads me to believe that what I'm seeing is somehow an incompatibility or conflict between the IE 9 beta and the SageTV gadget. I can't say whether it is an issue with the gadget or the IE 9 beta.

[wayner]

Originally Posted by gplasky

Do you have the Sage 7 Web server running on your SageTV 7 install? And can you log into it? If that works then the gadget should work. I have mine working on Sage 7 on a Win 7 client both with and without SageTV 7 client installed on it. If you're using the correct password it should just work. Also make sure all the .NET prerequisites are installed on that PC.

Yes, I have the Sage7 Web server installed, the Jetty version installed using the plugin manager, and I use that all of the time. And when I click on the Sage logo in the Gadget it takes me to the Sage web page which would seem to indicate that the server and port properties must be correct.

I am not sure about all of the .NET prereqs. I am assuming you mean on the server? This server is running XP SP3 and was up to date with updates as of a month or so ago so I think it should be good. The client, or PCs running the gadget, are running Win7 and are pretty much up to date although they may be missing the updates from the last couple of weeks.

[cncb]

Close the gadget and unzip the attached sage.js file to the gadget 'js' directory overwriting the original. Add the gadget again, set the server and port, and the text in the gadget should show any basic error messages if there are any. If there aren't any we will have to try to do some additional error checking.

[JerryB]

Originally Posted by cncb

Close the gadget and unzip the attached sage.js file to the gadget 'js' directory overwriting the original. Add the gadget again, set the server and port, and the text in the gadget should show any basic error messages if there are any. If there aren't any we will have to try to do some additional error checking.

I followed your instructions. Unfortunate, there are no error messages. The display just continues to read "NA - Check network connection, server, and settings"

Of note, when I attempt to refresh the connection by clicking on Recording/Schedule nothing happens, i.e. I don't get the usual Connecting... message.

[cncb]

I'll attempt to put something together this weekend with more extensive error checking.

[jorton]

Originally Posted by wayner

That's what I guessed so I can't figure out why it won't work for me. I have now tried three PCs and it is not working on any of the three. They are all running Win7. My old Sage6 server is still running and if I change my server, port and user it runs fine connecting to my Sage6 server. But for some reason nada to Sage7.

Are you using username "sage" to connect to the v7 server?

If I use "Sage" I can't connect but with "sage" I can...

I just tested this on my win7 64 client as I recalled having the same issue a few months ago with the widget/applet.

Good luck,

Jeremy

[Taddeusz]

Ditto on IE9 incompatibility. After restarting All CPU Meter and SageTV gadgets no longer worked. Had to download an update for All CPU Meter and it's now working.

[wayner]

Originally Posted by jorton

Are you using username "sage" to connect to the v7 server?

No, I am using my own username and password. But I am guessing that my problem is related to user/password authentication.

[jorton]

Originally Posted by wayner

No, I am using my own username and password. But I am guessing that my problem is related to user/password authentication.

I was just trying to point out that the username seems to be case sensitive whether or not you are using the default sage/frey or your own user/pass combo.

The tool defaulted to "Sage" and I had to change to "sage" for it to work.

Cheers,

Jeremy

[cncb]

Originally Posted by cncb

Close the gadget and unzip the attached sage.js file to the gadget 'js' directory overwriting the original. Add the gadget again, set the server and port, and the text in the gadget should show any basic error messages if there are any. If there aren't any we will have to try to do some additional error checking.

Try this one. This will give the most detailed error messages that we can get along with an error code. Just use this temporarily to see if you can get an useful error message.

[JerryB]

Originally Posted by cncb

Try this one. This will give the most detailed error messages that we can get along with an error code. Just use this temporarily to see if you can get an useful error message.

Success, at least from the stand point of getting a error messages that may help figure out what's changed in IE 9 that causing the problem.

"The system cannot locate the resource specified (-2146697211)" is the first message. This message appeared as soon as I installed the gadget before I even got a chance to enter setup information and persisted after entering the setup information. If I then click on Recording Schedule to update the connection after entering the setup information I get the following error message "Access is denied (-2147024891).

Hope this helps.

Jerry

[cncb]

Originally Posted by JerryB

If I then click on Recording Schedule to update the connection after entering the setup information I get the following error message "Access is denied (-2147024891).

Unfortunately, we don't have much to go on. I get this same error if I deliberately use the wrong user name or password. Maybe there is a new default security setting in IE9 that is causing problems but I really don't know.

[JerryB]

Do you have any thoughts on the first error message? I may be wrong but I suspect that the missing resource may be the reason that the login to the WebServer fails. Especially considering the fact, that I have no problem accessing the Weberver from within IE 9.

I checked the security options and they appear to be the same as IE 8. Of course, just because the choices are the same doesn't mean that their implemenation hasn't changed. As a test,I reduced the security settings in IE 9. Unfortunately, this did not resolve the problem.

[cncb]

Originally Posted by JerryB

Do you have any thoughts on the first error message? I may be wrong but I suspect that the missing resource may be the reason that the login to the WebServer fails.

The first error message is somewhat misleading and just means that it fails to connect with the initial default server and port (in the Options). You will get the same error if you change these back to invalid values.

[JerryB]

What's strange is that if I click on SageTV in the gadget, it logs into and launches the WebServer with the same parameters that, for some reason, don't seem to be able to connect directly from within the gadget.

I don't understand what's going on but, unless you have something else you'd like me to test, I think we've taken this about as far as we can at this point.

Sorry I couldn't be more help.

[cncb]

Originally Posted by JerryB

I don't understand what's going on but, unless you have something else you'd like me to test, I think we've taken this about as far as we can at this point.

No, thanks. We'll just have to hope this somehow "resolves itself" by the time they release IE9 .

It is strange, though, that launching the browser with login credentials works since I'm pretty sure this didn't work with IE8 which is why I added just the plain "Web Server" (without login) launch type for IE specifically.