Re: SBS2003 STD SP1 - "failed to create empty document"

MMC: Failed to Create Empty Document
http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/c0dc941318274ea/3bfae73dfe4f3c23?hl=en&lnk=st&q=sbs+Failed+to+create+empty+document#3bfae73dfe4f3c23
--------------------------------------------------
**** Resolved ****

I called Product Support today/tonight. It took me and a few Microsoft
Techs about 3.5 hours to find the solution.

The problem lies with a registry key for Terminal Services.

HKLM\System\CurrentControlSet\Control\Terminal Server\TSAppCompat. If
this key is a 1, change it to a 0 and reboot.

I asked about how this key could have been changed. The tech told me
possibly a third party app related to Terminal Services. He also said
it could have been caused by someone trying to change the SBS server
over to a TS server.
--------------------------------------------------

--
Merv Porter [SBS-MVP]
============================


"SolveIT" <SolveIT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F2CE472E-B08A-46EF-A402-790F498AE717@xxxxxxxxxxxxxxxx
The first line of my post got all screwed up (fingercheck!). It should
read:
We have SBS 2003 SP1. We get "failed to create empty document when we try
to
launch Server Management, Event Viewer, Services, or any other Window
program
and the server performance is awful.

"SolveIT" wrote:

Server Management and getWe have a SBS 2003 Std. SP1 server. We have
several
symptoms of problems:
1) We launch Server Management or Event Viewer, Services or any Windows
program and get "Failed to create empty document" errors in a Microsoft
Management Console error box.
2) We use a dot matrix printer in the directory for printing from an
Access
database located on the server. We can print to the printer from Windows
(test page and Word) but get only lines when printing from the Access.
3) The server takes an extremely long time to shutdown - we wait 35 Min.
then power it off, and 30 minutes to start.
This is what we've tried so far: Booted Last Known Good - got network
functions working again. 1) tried to reinstall the management console
from
SBS CD1 - got a message that "You Are trying to install a version that is
earlier than the current version". SP1 is not on the CD. We tried to add
the
SBS administrative components to the DEP exception list - no change. 2)
Tried
to reinstall the dot matrix printer - still N.G.
This is the only production server we've got. We can only scrap it and
reinstall everything in an emergeny situation where the server crashes
completely. Wiping it and installing new is not going to happen unless it
crashes.
Any help is TRULY appreciated - Aidan


.

Relevant Pages

  • Re: Time zone redirection
    ... Administration and full-blown Terminal Services. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... client connections:-O. ... Well - obviously that does not work in Remote Desktop Admin mode ...
    (microsoft.public.windows.terminal_services)
  • RE: Terminal Services
    ... I understand that you want to have staff log ... we cannot make SBS to work as terminal server. ... why you cannot find Terminal Services in Add/Remove Windows Components. ...
    (microsoft.public.windows.server.sbs)
  • Re: can someone help clear this up?
    ... Terminal Services Client Access Licenses are assigned to the client, ... The Terminal Services License Server ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Storing Username/Password problem
    ... double click the RDP-Tcp connection and look at the Logon ... MCSE, CCEA, Microsoft MVP - Terminal Server ... logged on with the credentials specified in Terminal Services ... Do you want each user to have their own account on the server, ...
    (microsoft.public.windows.terminal_services)
  • Re: Storing Username/Password problem
    ... terminal server and then several client machines. ... have their own account on the server, or do you want all of your users to ... Terminal Services Developer ... someone from using your RDP file and being able to log into a Terminal ...
    (microsoft.public.windows.terminal_services)
Loading