TS 2003 and Tivoli Storage Manager problem

[Guest Michael Huettich]

Windows Server 2003 Standard with SP2 Terminal server with Office 2003,

SAVCE 10.1.7.7000 and Tivoli Storage Manager 5.5 installed.

 

The problem started some time back in February, with users unable to log

on to the terminal server, with profile errors.

 

 

Applog Event ID 1500 errors;

 

Event Type: Error

Event Source: Userenv

Event Category: None

Event ID: 1500

Date: 8/25/2008

Time: 10:31:18 AM

User: DTNT\kdotuser

Computer: DT00MX55

Description:

Windows cannot log you on because your profile cannot be loaded. Check

that you are connected to the network, or that your network is

functioning correctly. If this problem persists, contact your network

administrator.

 

DETAIL - Insufficient system resources exist to complete the requested

service.

 

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

 

 

Applog Event ID 1508 errors;

 

Event Type: Error

Event Source: Userenv

Event Category: None

Event ID: 1508

Date: 8/13/2008

Time: 11:04:51 AM

User: NT AUTHORITY\SYSTEM

Computer: DT00MX55

Description:

Windows was unable to load the registry. This is often caused by

insufficient memory or insufficient security rights.

 

DETAIL - Insufficient system resources exist to complete the requested

service. for C:\Documents and Settings\kdotuser\ntuser.dat

 

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

 

 

Applog Event ID 1058 errors;

 

Event Type: Error

Event Source: Userenv

Event Category: None

Event ID: 1058

Date: 8/25/2008

Time: 10:47:05 AM

User: DTNT\kdotuser

Computer: DT00MX55

Description:

Windows cannot access the file gpt.ini for GPO cn={31B2F340-016D-11D2-

945F-00C04FB984F9},cn=policies,cn=system,DC=ksdot,DC=org. The file must

be present at the location <\\ksdot.org\sysvol\ksdot.org\Policies

\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Configuration

information could not be read from the domain controller, either because

the machine is unavailable, or access has been denied. ). Group Policy

processing aborted.

 

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

 

IT COULDN'T READ the Default Domain Policy!?!?!?!

 

and the killer, Applog event 1219 errors;

 

Event Type: Error

Event Source: Winlogon

Event Category: None

Event ID: 1219

Date: 8/13/2008

Time: 11:06:50 AM

User: N/A

Computer: DT00MX55

Description:

Logon rejected for DTNT\kdotuser. Unable to obtain Terminal Server User

Configuration. Error: Not enough resources are available to complete this

operation.

 

 

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Data:

0000: b9 06 00 00 ¹...

 

Bouncing the server clears those errors up for a short time (1-2 hours),

then it starts all over again, also noticed the following,

 

Syslog Event ID 2020 errors;

 

Event Type: Error

Event Source: Srv

Event Category: None

Event ID: 2020

Date: 8/14/2008

Time: 7:17:13 AM

User: N/A

Computer: DT00MX55

Description:

The server was unable to allocate from the system paged pool because the

pool was empty.

 

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 00 00 04 00 01 00 54 00 ......T.

0008: 00 00 00 00 e4 07 00 c0 ....ä..À

0010: 00 00 00 00 9a 00 00 c0 ....?..À

0018: 00 00 00 00 00 00 00 00 ........

0020: 00 00 00 00 00 00 00 00 ........

0028: 09 00 00 00 ....

 

Those applog 1058 and syslog 2020 errors went away after tweaking the

Network Connections, Advanced Settings adapter and provider orders on the

terminal server and domain controllers. PrinterMaskKey was added to

HKEY_USERS\.DEFAULT\Printers and DevModes2 emptied (continues to remain

empty now) in the registry on the terminal server. MS recommended system

paged pool tweaks also applied (KB312362).

 

After much searching and testing and gnashing of teeth and pulling of

hair it was determined that those errors went away if the Tivoli services

were stopped. Now we have a workaround with scheduled tasks starting the

Tivoli services after hours, and stopping them before the next business

day begins. Vendor documentation on this particular problem is non-

existent. Not sure how TSM was installed on the server (way before my

time). Does anyone know if TSM should be installed in /install mode or

/execute mode, and if that would make any difference. And what about

SAVCE, I've seen both ways recommended, which is right?

 

--

Best Regards,

Michael Huettich

Kansas Department of Transportation

 

-----BEGIN GEEK CODE BLOCK-----

Version: 3.12

GAT/CM/CS/ED/IT/MU/P/TW d- s: a+ C++++

UL++++ P+ L++ E--- w Y+ PGP t+ 5 X++

R* tv b++ DI+++ D G e++ h--- r+++ y+++**

------END GEEK CODE BLOCK------

[Guest Jeff Pitsch]

Re: TS 2003 and Tivoli Storage Manager problem

 

Everything should always be installed in install mode. That's standard. I

ahve had similar problems with Tivoli in the past. Tivoli, IMHO, is a pile

of ____. You can fill in the blank........ As for SAVCE, same thing. in

fact, I would typically recommend not using anti-virus at all on TS boxes

and let remote scans take care of them. Save a ton on resources and see a

good amount more of users on the systems without the hassles.

 

--

Jeff Pitsch

Microsoft MVP - Terminal Services

 

"Michael Huettich" <looking@the.roads> wrote in message

news:Xns9B0DAD86847D0KDOT@207.46.248.16...

> Windows Server 2003 Standard with SP2 Terminal server with Office 2003,

> SAVCE 10.1.7.7000 and Tivoli Storage Manager 5.5 installed.

>

> The problem started some time back in February, with users unable to log

> on to the terminal server, with profile errors.

>

>

> Applog Event ID 1500 errors;

>

> Event Type: Error

> Event Source: Userenv

> Event Category: None

> Event ID: 1500

> Date: 8/25/2008

> Time: 10:31:18 AM

> User: DTNT\kdotuser

> Computer: DT00MX55

> Description:

> Windows cannot log you on because your profile cannot be loaded. Check

> that you are connected to the network, or that your network is

> functioning correctly. If this problem persists, contact your network

> administrator.

>

> DETAIL - Insufficient system resources exist to complete the requested

> service.

>

> For more information, see Help and Support Center at

> http://go.microsoft.com/fwlink/events.asp.

>

>

> Applog Event ID 1508 errors;

>

> Event Type: Error

> Event Source: Userenv

> Event Category: None

> Event ID: 1508

> Date: 8/13/2008

> Time: 11:04:51 AM

> User: NT AUTHORITY\SYSTEM

> Computer: DT00MX55

> Description:

> Windows was unable to load the registry. This is often caused by

> insufficient memory or insufficient security rights.

>

> DETAIL - Insufficient system resources exist to complete the requested

> service. for C:\Documents and Settings\kdotuser\ntuser.dat

>

> For more information, see Help and Support Center at

> http://go.microsoft.com/fwlink/events.asp.

>

>

> Applog Event ID 1058 errors;

>

> Event Type: Error

> Event Source: Userenv

> Event Category: None

> Event ID: 1058

> Date: 8/25/2008

> Time: 10:47:05 AM

> User: DTNT\kdotuser

> Computer: DT00MX55

> Description:

> Windows cannot access the file gpt.ini for GPO cn={31B2F340-016D-11D2-

> 945F-00C04FB984F9},cn=policies,cn=system,DC=ksdot,DC=org. The file must

> be present at the location <\\ksdot.org\sysvol\ksdot.org\Policies

> \{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Configuration

> information could not be read from the domain controller, either because

> the machine is unavailable, or access has been denied. ). Group Policy

> processing aborted.

>

> For more information, see Help and Support Center at

> http://go.microsoft.com/fwlink/events.asp.

>

> IT COULDN'T READ the Default Domain Policy!?!?!?!

>

> and the killer, Applog event 1219 errors;

>

> Event Type: Error

> Event Source: Winlogon

> Event Category: None

> Event ID: 1219

> Date: 8/13/2008

> Time: 11:06:50 AM

> User: N/A

> Computer: DT00MX55

> Description:

> Logon rejected for DTNT\kdotuser. Unable to obtain Terminal Server User

> Configuration. Error: Not enough resources are available to complete this

> operation.

>

>

> For more information, see Help and Support Center at

> http://go.microsoft.com/fwlink/events.asp.

> Data:

> 0000: b9 06 00 00 ¹...

>

> Bouncing the server clears those errors up for a short time (1-2 hours),

> then it starts all over again, also noticed the following,

>

> Syslog Event ID 2020 errors;

>

> Event Type: Error

> Event Source: Srv

> Event Category: None

> Event ID: 2020

> Date: 8/14/2008

> Time: 7:17:13 AM

> User: N/A

> Computer: DT00MX55

> Description:

> The server was unable to allocate from the system paged pool because the

> pool was empty.

>

> For more information, see Help and Support Center at

> http://go.microsoft.com/fwlink/events.asp.

> Data:

> 0000: 00 00 04 00 01 00 54 00 ......T.

> 0008: 00 00 00 00 e4 07 00 c0 ....ä..À

> 0010: 00 00 00 00 9a 00 00 c0 ....?..À

> 0018: 00 00 00 00 00 00 00 00 ........

> 0020: 00 00 00 00 00 00 00 00 ........

> 0028: 09 00 00 00 ....

>

> Those applog 1058 and syslog 2020 errors went away after tweaking the

> Network Connections, Advanced Settings adapter and provider orders on the

> terminal server and domain controllers. PrinterMaskKey was added to

> HKEY_USERS\.DEFAULT\Printers and DevModes2 emptied (continues to remain

> empty now) in the registry on the terminal server. MS recommended system

> paged pool tweaks also applied (KB312362).

>

> After much searching and testing and gnashing of teeth and pulling of

> hair it was determined that those errors went away if the Tivoli services

> were stopped. Now we have a workaround with scheduled tasks starting the

> Tivoli services after hours, and stopping them before the next business

> day begins. Vendor documentation on this particular problem is non-

> existent. Not sure how TSM was installed on the server (way before my

> time). Does anyone know if TSM should be installed in /install mode or

> /execute mode, and if that would make any difference. And what about

> SAVCE, I've seen both ways recommended, which is right?

>

> --

> Best Regards,

> Michael Huettich

> Kansas Department of Transportation

>

> -----BEGIN GEEK CODE BLOCK-----

> Version: 3.12

> GAT/CM/CS/ED/IT/MU/P/TW d- s: a+ C++++

> UL++++ P+ L++ E--- w Y+ PGP t+ 5 X++

> R* tv b++ DI+++ D G e++ h--- r+++ y+++**

> ------END GEEK CODE BLOCK------

[Guest Michael Huettich]

Re: TS 2003 and Tivoli Storage Manager problem

 

Thanks Jeff! I couldn't agree more about Tivoli, but you play the hand

you're dealt... I've had more trouble with this one beast in the last 6

months than I ever did at my last gig with the 7 terminal servers hosting

adp frontends to a sql backend.

 

So I am thinking after hours, completely wipe Tivoli, bounce, reinstall

Tivoli in /install mode (which it should do by default but actually

manually throw it into /install mode), bounce again to make sure it is

ready for prime time, and then watch it like part two of a cliffhanger to

make sure none of those annoying errors start getting thrown again when

users start logging on. Come to think of it, I was looking at the Tivoli

bits after an upgrade (not performed by yours truly), had to re-run the

upgrade to fix the services bombing with the wrong service exe path, the

system never did bring up that annoying wait until done prompt, and ended

up having to fix the service exe path manually (sc is my friend), so it

is possibly my fault that the whole TSM instance on that server is

wonky...

 

Do you think it might make a difference installing from the console

(/admin rdp session or VNC) rather than a vanilla rdp session?

Considerations that I am fairly sure were not taken into account the

first time around, as the folks managing the box before I got here did

not even know you could do an rdp console session (tsmmc.msc? What's

that? /console, huh? What, it changed to /admin, why, whatever for?).

 

"Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in

news:OUXHLHVDJHA.524@TK2MSFTNGP06.phx.gbl:

> Everything should always be installed in install mode. That's

> standard. I ahve had similar problems with Tivoli in the past.

> Tivoli, IMHO, is a pile of ____. You can fill in the blank........

> As for SAVCE, same thing. in fact, I would typically recommend not

> using anti-virus at all on TS boxes and let remote scans take care of

> them. Save a ton on resources and see a good amount more of users on

> the systems without the hassles.

>

 

 

 

--

Best Regards,

Michael Huettich

Kansas Department of Transportation

 

-----BEGIN GEEK CODE BLOCK-----

Version: 3.12

GAT/CM/CS/ED/IT/MU/P/TW d- s: a+ C++++

UL++++ P+ L++ E--- w Y+ PGP t+ 5 X++

R* tv b++ DI+++ D G e++ h--- r+++ y+++**

------END GEEK CODE BLOCK------

[Guest Vera Noest [MVP]]

Re: TS 2003 and Tivoli Storage Manager problem

 

Are you starting the TSM client through the Client Access Daemon

(CAD)? I do, and it has a very small footprint on the server. The

CAD service runs constantly, retrieves the client schedule from the

TSM server and starts the TSM Client only when it needs to perform

the backup. Might be worth a try.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

Michael Huettich <looking@the.roads> wrote on 03 sep 2008 in

microsoft.public.windows.terminal_services:

> Thanks Jeff! I couldn't agree more about Tivoli, but you play

> the hand you're dealt... I've had more trouble with this one

> beast in the last 6 months than I ever did at my last gig with

> the 7 terminal servers hosting adp frontends to a sql backend.

>

> So I am thinking after hours, completely wipe Tivoli, bounce,

> reinstall Tivoli in /install mode (which it should do by default

> but actually manually throw it into /install mode), bounce again

> to make sure it is ready for prime time, and then watch it like

> part two of a cliffhanger to make sure none of those annoying

> errors start getting thrown again when users start logging on.

> Come to think of it, I was looking at the Tivoli bits after an

> upgrade (not performed by yours truly), had to re-run the

> upgrade to fix the services bombing with the wrong service exe

> path, the system never did bring up that annoying wait until

> done prompt, and ended up having to fix the service exe path

> manually (sc is my friend), so it is possibly my fault that the

> whole TSM instance on that server is wonky...

>

> Do you think it might make a difference installing from the

> console (/admin rdp session or VNC) rather than a vanilla rdp

> session? Considerations that I am fairly sure were not taken

> into account the first time around, as the folks managing the

> box before I got here did not even know you could do an rdp

> console session (tsmmc.msc? What's that? /console, huh? What,

> it changed to /admin, why, whatever for?).

>

> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in

> news:OUXHLHVDJHA.524@TK2MSFTNGP06.phx.gbl:

>

>> Everything should always be installed in install mode. That's

>> standard. I ahve had similar problems with Tivoli in the past.

>> Tivoli, IMHO, is a pile of ____. You can fill in the

>> blank........ As for SAVCE, same thing. in fact, I would

>> typically recommend not using anti-virus at all on TS boxes and

>> let remote scans take care of them. Save a ton on resources

>> and see a good amount more of users on the systems without the

>> hassles.

[Guest Vera Noest [MVP]]

Re: TS 2003 and Tivoli Storage Manager problem

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote on

03 sep 2008:

> Are you starting ... the Client Access Daemon (CAD)?

 

That should of course be: Client Acceptor Daemon.

 

I've been answering to many licensing questions :-)

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

*----------- Please reply in newsgroup -------------*

[Guest Michael Huettich]

Re: TS 2003 and Tivoli Storage Manager problem

 

"Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se> wrote in

news:Xns9B0FA632D328Cveranoesthemutforsse@207.46.248.16:

 

No, we do not currently use the Client Acceptor Daemon. As far as I

know, there are no plans to start, either.

 

The behaviour is still occurring, even with Tivoli turned off during the

day, just not near as frequently as when it was running, so now I am even

more stumped, watching Charleton Heston put his vest on...

 

The latest behavior analysis on the server seems to indicate that it

starts losing it after it fails to retrieve the list of servers from the

master browser. As soon as that happens, the terminal server can no

longer read the default domain policy from the DC, and as a result, users

can no longer connect.

 

Ah, MS licensing, what a kludgefest! :)

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote on

> 03 sep 2008:

>

>> Are you starting ... the Client Access Daemon (CAD)?

>

> That should of course be: Client Acceptor Daemon.

>

> I've been answering to many licensing questions :-)

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> *----------- Please reply in newsgroup -------------*

 

 

 

--

Best Regards,

Michael Huettich

Kansas Department of Transportation

 

-----BEGIN GEEK CODE BLOCK-----

Version: 3.12

GAT/CM/CS/ED/IT/MU/P/TW d- s: a+ C++++

UL++++ P+ L++ E--- w Y+ PGP t+ 5 X++

R* tv b++ DI+++ D G e++ h--- r+++ y+++**

------END GEEK CODE BLOCK------