July 19, 2005 at 9:23 am
Hello!!
Our company recently moved to a corporate Windows 2000 Network and AD from Novell and all our servers were moved from our little domain. We are seeing a wierd problem with SQLSever since our move. The sever that has SQL Server is working fine and we are able to register the server in Enterprise Manager. However, it sits and hangs when trying to browse the Databases or Management nodes (all other nodes are ok). We can also get to Query Analyzer and queries against any of the the database tables work just fine .. UNLESS Query Analyzer tries to browse for the databases (to populate that database dropdown or display the Object browser) .. in that case, it sits and hangs.
We have installed Service Pack 4 and this did not resolve the problem. The hotfix for RAM over 2 gig on the server does not apply in our case. Has anyone experienced this problem before? We rebooted SQL Server yesterday and after a couple of reboots, it worked (the Query Analyzer issue remained), but we are now back to the same issue.
Any clues, suggestions, and of course fixes would be much appreciated!
Thank you!
Artie
July 22, 2005 at 8:00 am
This was removed by the editor as SPAM
July 23, 2005 at 10:52 pm
Artie - you may want to look at this other post to see if there are any solutions to your problem...
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=9&messageid=140147
**ASCII stupid question, get a stupid ANSI !!!**
July 24, 2005 at 7:54 pm
Hi Arti,
I have the same problem i tried but at last i have to end up with re-installing of OS.
Pls read this can describe u better.
Kernel mode is a privileged processor mode in which a thread has access to system-wide memory (including that of all user-mode processes) and to hardware. By contrast, user mode is a nonprivileged processor mode in which a thread can only access system resources by calling system services.
A user mode process cannot access kernel mode memory, or access memory of another user mode process. This is enforced by processor hardware, in conjunction with kernel mode data structures such as Page Tables.
As a result of this protection system, a user mode application generally cannot stop responding, cause a blue screen, or otherwise cause a failure in the Windows NT operating system. Such problems should be pursued primarily at the system layer as an operating system, device-driver, or hardware issue.
While an application error cannot cause a failure in the operating system, an operating system error can cause an application to stop responding. This is because of the general rule: applications must call inward (to kernel mode), but the operating system can reference outward to user mode freely at any time. A microkernel-influenced architecture such as Windows NT may in turn dispatch certain work to a user-mode system process rather than perform the work in kernel mode. However, the overall principle remains the same: Processor hardware enforces process context isolation, which prevents one process from causing a failure in another, whether one or both are in user mode.
If a user mode application passes an invalid parameter in a Win32® API call, it is the responsibility of the operating system to validate this parameter. In very rare cases, passing an invalid parameter may cause a Windows NT blue screen error. However, this is an operating system issue, and should be debugged and pursued as such.
Hope this helps u.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply