Re: Windows Completely Locks Up!! FREEZE



You've got a combination of errors. Some would appear to be Service
related and probably dependency issues. Not sure why your system is
failing to start/run the Distributed Transaction Coordinator. The ASPI
( Application Specific Program Interface ) isn't usually required and is
sometimes installed with a CD-Burning application. I would probably
start diagnostics by checking the Services and locate any items that are
disabled or starting manually instead of Automatic. There isn't a fixed
list to reference as it depends on what your system is running. Also I'm
not clear on why your system ( Office 2007 ) is running SQLServer.

"ottagothen (Joe)" <ottagothenJoe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:E17AAB41-40E6-4A3E-9137-AAC8A47BC4B6@xxxxxxxxxxxxxxxx
Everyday my computer will completely lock up. Freeze. Nothing will
respond.
Ctrl Alt Delete dose not even work. I have to turn off the computer and re
start it. I can't pin point the program if that is what is causing the
freezing of the computer.
I am using Windows XP Professional with SP2. I have downloaded SP3. The
freezing is happening on both SP2 and SP3.
It seem to happen when I have a window open in a program and I try to
close
it. It will happen in Outlook 2007, or even in my Peathtree accounting
program 2007.
The Event Viewer Application shows these Errors:
Source = COM+
The run-time environment was unable to initialize for transactions
required
to support transactional components. Make sure that MS-DTC is running.
(DtcGetTransactionManagerEx(): hr = 0x8004d027)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp. No information Here.
Source = MSTDC Client
Failed to initialize the needed name objects. Error Specifics:
d:\xpsp\com\com1x\dtc\dtc\msdtcprx\src\dtcinit.cpp:215, Pid: 3892
No Callstack,
CmdLine: C:\WINDOWS\system32\dllhost.exe
/Processid:{02D4B3F1-FD88-11D1-960D-00805FC79235}

The Event Viewer System shows these Errors:
Source = Service control Manager for all or them
The Business Contact Manager SQL Server Startup Service service terminated
with the following error:
The service did not respond to the start or control request in a timely
fashion.

The SQL Server (MSSMLBIZ) service failed to start due to the following
error:
The service did not respond to the start or control request in a timely
fashion.

Timeout (30000 milliseconds) waiting for the SQL Server (MSSMLBIZ) service
to connect.

The following boot-start or system-start driver(s) failed to load:
Aspi32
And Finally
The HP Pci Information service failed to start due to the following error:
The system cannot find the path specified.




.



Relevant Pages

  • Re: Windows Completely Locks Up!! FREEZE
    ... Error Specifics: ... Source = Service control Manager for all or them ... The Business Contact Manager SQL Server Startup Service service terminated ... The service did not respond to the start or control request in a timely ...
    (microsoft.public.windowsxp.general)
  • Re: Transaction Isolation Level
    ... This means that while I initiate a transaction selecting all new orders it ... My query is executed on a SQL server 2005. ... the isolation level you should use is snapshot isolation. ...
    (comp.databases.ms-sqlserver)
  • Re: Asynchronous Stored Procedure Never Returns - Help?
    ... If you have the Sql Server 2000 or 2005 docs they are thorough and can be ... for Transaction SQL Reference from the drop-down or select a keyword from ... your query in Query Analyzer or Sql Server Management Studio, ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Transaction Abort in a trigger SQL 2008, writing to event log
    ... transaction could still be doomed at some point, ... With the current functionality in SQL Server ... you should roll back the transaction in your error handler. ... global cursor in a stored procedure. ...
    (microsoft.public.sqlserver.programming)
  • Re: Replication solution?
    ... Replication is your solution for distributed transaction processing...but ... some cases replication makes changes to the schema. ... identical SQL Server in the Ottawa would make it faster for the Ottawa ... I don't think log shipping would do us any good since we need two active ...
    (microsoft.public.sqlserver.replication)

Loading