August 2005 Entries
Target: %windir%\system32\rundll32.exe user32.dll,LockWorkStation Start in: %windir%
This error occurs when you try to use a db login within a connection string on a server that has not been set up for mixed-mode (SQL Server and Windows security), ie when it is set to 'Windows only' authentication. To fix this: Start Enterprise Manager, Right-click on the server and select Properties Select the Security tab. Select 'SQL Server and Windows' as the authentication mode. Click OK. HTH Tim
Sick of the 'simple' file sharing and security functionality that are the default (recommended) setting for XP? You can turn it off and take full control yourself.... To Turn on Advanced File Sharing 1. In Windows Explorer, click Tools, then click Folder Options. 2. On the View tab, in the Advanced Settings area, click to clear the Use Simple File Sharing (Recommended) check box. ...
This feature was working - and for some reason stopped working/showing what I'm listening to. Had a hunt around and found this: "In Windows Media Player, go to Tools > Plugins, and check that MSN Messenger Music Plugin is checked." Works like a charm ;-) Thanks a million Martin Bradley for posting this: http://www.bigblueball.com/... HTH Tim...
Upon clicking on the SQL Server Enterprise Manager shortcut the following error occurs: MMC cannot open the file C:\Program Files\Microsoft SQL Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.This may be because the file does not exist, is not an MMC console, or was created by a later version of MMC. This may also be because you do not have sufficient access rights to the file. The msc file did exist and I definately has permissions to it. So I can only assume it some how got corrupt. The...
This error occurred when installing two ASP.NET (C#) web service on a new server (win2k3 ent + SP1). IIS had only just been installed immediately prior to this. After copying the WS dirs into c:\inetput\wwwroot, and within IIS manager registered them as a web app, changed the anon user to a specific AD account, then did an iisreset. When trying to verify they were accessible (just entering the urls into IE) - both produced the error (401-1). I spend the next couple of hours adding & changing...