Reply to thread

Message

<blockquote data-quote="craigparris1" data-source="post: 387278" data-attributes="member: 75254">Hi clarkey,Did you get around to checking the actual SQL Server itself?&nbsp; Your best bet would be to install the SQL Server Express Management Studio - you can get it <a href="http://www.microsoft.com/downloads/details.aspx?displaylang=en&amp;FamilyID=c243a5ae-4bd1-4e3d-94b8-5a0f62bf7796" target="_blank">here</a> (Microsoft downloads site).You'll need to try and connect to your local SQL Server instance (usually this will be called (local)\SQLExpress).&nbsp; The username will be &quot;sa&quot; and the password should be &quot;MediaPortal&quot; (don't include the double-quotes, and the password is case-sensitive).&nbsp; Obvioulsly, if you know you've changed the sa password to something else, then you'll need to use that).You should also take a look in your Windows Event Viewer - check the &quot;Application&quot; and &quot;System&quot; logs and see if there are any errors/messages logged in there by SQL Server that might indicate why it's having problems.I do work with SQL Server, so I'll be happy to assist, but there's not quite enough info from you at the moment to work out exactly what the problem is.Cheers,Craig</blockquote>

[QUOTE="craigparris1, post: 387278, member: 75254"] Hi clarkey, Did you get around to checking the actual SQL Server itself? Your best bet would be to install the SQL Server Express Management Studio - you can get it [URL="http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c243a5ae-4bd1-4e3d-94b8-5a0f62bf7796"]here[/URL] (Microsoft downloads site). You'll need to try and connect to your local SQL Server instance (usually this will be called (local)\SQLExpress). The username will be "sa" and the password should be "MediaPortal" (don't include the double-quotes, and the password is case-sensitive). Obvioulsly, if you know you've changed the sa password to something else, then you'll need to use that). You should also take a look in your Windows Event Viewer - check the "Application" and "System" logs and see if there are any errors/messages logged in there by SQL Server that might indicate why it's having problems. I do work with SQL Server, so I'll be happy to assist, but there's not quite enough info from you at the moment to work out exactly what the problem is. Cheers, Craig [/QUOTE]

Verification