After not using ShowCenter for a few months, I now can't get the unit to communicate with the PC running the streaming server process--the unit doesn't even see the PC on the wired network at all.  I have made no changes to the WinXP software firewall (that I remember anyway) where I'm running the streaming server processs.  After starting the Startup and Setup tool, I can add folders to the folder browser fine.  When I select the Media Server and click on the Restricted Access menu item, I get a blank page on the right that just says "Acess code" and nothing else.  I'm not even sure why this is the case.  I seem to remember that by default the access code is something like 0000 and I doubt I would have changed it.

When I try and start up the Media Manager app, I get an error dialogue box that says "Could not init the database!"  I've uninstalled and reinstalled the apps twice with the same results.

Can anyone point me in the right direction?  Is there some way to do a full hardware reset of the ShowCenter unit itself also?

Thanks a lot!

Steve

Chicago, IL USA

I resolved this issue myself after getting no help from tech support and in this case, I would have felt even worse if I wasted their time, so I'm glad I got no help!  This is a lesson in stupidity on my part.  I found a knowledge base article that led me to the solution based on the error message I was getting when I started up Media Manager.

Basically in my overzealousness to conserve CPU cycles on wasted processes running in the background, months ago I had turned off several processes from the "Services" list in WinXP that I either couldn't identify as necessary or that I thought weren't necessary.  Unfortunately, one of them was the Pinnacle process for the media manager which then also starts up other MS SQL Server processes when it starts, so none of them were running on my computer!

Naturally the ShowCenter 200 couldn't communicate with the PC nor could the Media Server software communicate with the underlying database, which is an MS SQL Server database.

After setting the appropriate services back to "Automatic" all problems resolved.

A good lesson learned on my part!