Search results for query: *

Thanks for your reply, but I just verified the Path settings and they are correct in accordance with that KB article. Any more help would be greatly appreciated, I've been beating my head against the wall for a week over this one.

I have a Windows Server 2008 Standard system configured as a terminal server. The installation is several months old and it has taken me forever to get all of the apps installed and working. Now all of a sudden when starting Server Manager (as well as various other Admin tools) I get this...

If anyone is interested I think I solved the problem. I called MS to get the hotfix referenced in kb951954 . Even though I wasn't actually getting a stop error, it was behaving as if it were. It sounded close enough and I was getting desperate, and now the SQL install goes through just fine...

I looked for any log I could think of, it's not even creating a memory.dmp file when it reboots. I am using the standard install wizard, no switches. It seems like I'm experiencing this problem with SQL and at other random times when working on the server via RDP. So it looks like a remote...

Thanks for the help but that post revolves around firewall and SQL connectivity issues (post-installation and setup). My issue is SQL will not even begin to install, and brings the server down instead. It doesn't seem like a configuration issue.

This is really making me angry, but a fresh clean install of Server 2008 Standard 64-bit on a brand spakin' new ML350 G5 is giving me all kinds of problems. The main one is the SQL Server 2005 Express install keeps crashing the server. The install package unpacks then all of a sudden the start...

I have an 80GB WD hard drive... funny thing is now going into Disk Manager it shows the drive as "unreadable".. and it also shows the drive as having 1.32 TERABYTES free! The drive took a bit of a shock but nothing other drives wouldnt be able to handle. What would be a good tool to try to...

We are currently using Novell's ZenWorks and are looking for a MS-based replacement. SMS is overkill for us and ZenWorks requires too many Novell components. I like the idea of creating apps and associating them with users and groups along with specifying settings such as force run and run...