Trouble with TS on Server 2003

[Andy \(Andrew\)]

We have a Server 2003 machine that was put into Application mode.
After that, we installed a few programs using the Control Panel's
Add/Remove procedure (presumably placing it temporarily into "install"
mode) and we've discovered some intractable problems.

For example, one of the applications is Time Matters. Among other
things, it keeps track of documents. If one user opens one of these
PDF's from within Time Matters, it properly opens Acrobat Reader
(which was also installed in "install" mode) and the document is
displayed. However, if another user tries the same thing (not at the
same time,) they get an AcroRd32 crash saying "memory cannot be
written."

Another problem is mail merge using Word. Some users have no
trouble, others get a locked up session.

These issues are consistent. In other words, certain users can
perform these functions repeatedly without trouble while other users
consistently get the same errors. It doesn't "come and go."

I've spent a lot of time looking at regmon and filemon dumps,
checking permissions, file locations, etc., but can't find any disparities
between trouble-free users and problem users. Of course, there has
to be something there. I just haven't been able to locate it yet.

How do I proceed to resolve this? Should I just wipe the server, install
fresh, and install all the applications first before switching it to
application
mode?

Any suggestions will be appreciated.

 

[Cláudio Rodrigues [MVP]]

GAndy (Andrew) wrote:
> We have a Server 2003 machine that was put into Application mode.
> After that, we installed a few programs using the Control Panel's
> Add/Remove procedure (presumably placing it temporarily into "install"
> mode) and we've discovered some intractable problems.
>
> For example, one of the applications is Time Matters. Among other
> things, it keeps track of documents. If one user opens one of these
> PDF's from within Time Matters, it properly opens Acrobat Reader
> (which was also installed in "install" mode) and the document is
> displayed. However, if another user tries the same thing (not at the
> same time,) they get an AcroRd32 crash saying "memory cannot be
> written."
>
> Another problem is mail merge using Word. Some users have no
> trouble, others get a locked up session.
>
> These issues are consistent. In other words, certain users can
> perform these functions repeatedly without trouble while other users
> consistently get the same errors. It doesn't "come and go."
>
> I've spent a lot of time looking at regmon and filemon dumps,
> checking permissions, file locations, etc., but can't find any disparities
> between trouble-free users and problem users. Of course, there has
> to be something there. I just haven't been able to locate it yet.
>
> How do I proceed to resolve this? Should I just wipe the server, install
> fresh, and install all the applications first before switching it to
> application
> mode?
>
> Any suggestions will be appreciated.
>
>
Given the intermittent nature of the issue I would simply reinstall the
server from scratch. In less than an hour you can have the TS up and
running.
I assume you meant Windows Server 2003 with Terminal Services installed
as there is no such thing as 'Application Server' under 2003. This is a
Windows 2000 Server feature.
After installing 2003 add Terminal Services using Control Panel |
Add/Remove Programs | Windows Components. You will be asked to reboot.
Once you reboot, then proceed with the apps installation, always using
Control Panel | Add/Remove Programs.

--
Cláudio Rodrigues
CEO, TSFactory Inc.

Microsoft MVP
Windows Server - Terminal Services
http://www.tsfactory.com

 

[Andy \(Andrew\)]

""Cláudio Rodrigues [MVP]"" <CR@NOSPAM-TSFactory.ca> wrote in message news:%

> Given the intermittent nature of the issue I would simply reinstall the
> server from scratch. In less than an hour you can have the TS up and
> running.

It isn't intermittent at all. User 'A' will get the errors consistently
while user 'B' won't.

Nevertheless, would there be anything wrong with installing all the
applications
prior to installing Terminal Services? Or would all the applications
require
reinstallation after installing Terminal Services anyway?

Thanks.

 

[Vera Noest [MVP]]

comments inline.

"Andy \(Andrew\)" <andrew@somewhere.net> wrote on 24 jul 2007 in
microsoft.public.windows.terminal_services:

> ""Cláudio Rodrigues [MVP]"" <CR@NOSPAM-TSFactory.ca> wrote in
> message news:%
>
>> Given the intermittent nature of the issue I would simply
>> reinstall the server from scratch. In less than an hour you can
>> have the TS up and running.
>
> It isn't intermittent at all. User 'A' will get the errors
> consistently while user 'B' won't.

Have you tried giving these users a new profile? Does it work OK
for a newly created test account?

> Nevertheless, would there be anything wrong with installing all
> the applications prior to installing Terminal Services?

Yes. Terminal Services must be installed *before* you install user
applications. You receive a warning about this when you install TS.

> Or would all the applications require
> reinstallation after installing Terminal Services anyway?

Yes. And that's because the server must be in "install mode" when
you install user applications, to be able to provide multi-user
functionality. You cannot put a server in install mode if it
doesn't run Terminal Services.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___