Cluster Name Failing...

Hi All, Cluster Group is failing to come online due to cluster name.
Unfortunately running MSCS on Win2k Adv Server so most of the help mentioned
is towards Win2k3...Any luck guys...?
Event ID: 1052 and 1069
TIA
CLuster name failing is a Cluster service issue, not SQL, yes?
SQL Name failing is different.
What to the application and system event logs say?
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.expertsrt.com - not your average tech Q&A site
"Vai2000" <nospam@.microsoft.com> wrote in message
news:%23MuguCnMGHA.500@.TK2MSFTNGP15.phx.gbl...
> Hi All, Cluster Group is failing to come online due to cluster name.
> Unfortunately running MSCS on Win2k Adv Server so most of the help
> mentioned
> is towards Win2k3...Any luck guys...?
> Event ID: 1052 and 1069
> TIA
>

Cluster install failing

When installing SQL 2005 on a 2 node cluster, the install fails saying setup
on the remote machine failed, check the task scheduler log. The log on the
remote machine says "Unable to start task...Access is denied". Any idea how
to get around this?
Environment is DL585, Windows 2003 x64 sp1, SQL 2005 x64 Dev Edition
I also need to mention that I have Act as part of the operating system and
log on as a service rights on both nodes.
"Brad" wrote:

> When installing SQL 2005 on a 2 node cluster, the install fails saying setup
> on the remote machine failed, check the task scheduler log. The log on the
> remote machine says "Unable to start task...Access is denied". Any idea how
> to get around this?
> Environment is DL585, Windows 2003 x64 sp1, SQL 2005 x64 Dev Edition
|||You have to install using a domain account that is a member of the local
administrators group on each server.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Brad" <Brad@.discussions.microsoft.com> wrote in message
news:AA1196F9-0113-4844-B2C4-1BEABCAE97F3@.microsoft.com...[vbcol=seagreen]
>I also need to mention that I have Act as part of the operating system and
> log on as a service rights on both nodes.
> "Brad" wrote:
|||Permissions. The account that you are using to install the failover cluster
instance must be a member of the local admin group on each machine. (The
service accounts related to SQL Server do NOT need to be.)
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Brad" <Brad@.discussions.microsoft.com> wrote in message
news:F9ED4AEF-08EF-40CD-845E-E86794714C8A@.microsoft.com...
> When installing SQL 2005 on a 2 node cluster, the install fails saying
> setup
> on the remote machine failed, check the task scheduler log. The log on
> the
> remote machine says "Unable to start task...Access is denied". Any idea
> how
> to get around this?
> Environment is DL585, Windows 2003 x64 sp1, SQL 2005 x64 Dev Edition
|||Yes, thank you. The domain account I am using is already a member of the
admin group on both nodes. The error still persists.
"Geoff N. Hiten" wrote:

> You have to install using a domain account that is a member of the local
> administrators group on each server.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Brad" <Brad@.discussions.microsoft.com> wrote in message
> news:AA1196F9-0113-4844-B2C4-1BEABCAE97F3@.microsoft.com...
>
>
|||I didn't provide that information up front but the account is a member of the
admin group on both boxes.
"Michael Hotek" wrote:

> Permissions. The account that you are using to install the failover cluster
> instance must be a member of the local admin group on each machine. (The
> service accounts related to SQL Server do NOT need to be.)
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
> "Brad" <Brad@.discussions.microsoft.com> wrote in message
> news:F9ED4AEF-08EF-40CD-845E-E86794714C8A@.microsoft.com...
>
>
|||Hi,
But is it the LOCAL ADMIN ACCOUNT not domain admin account?
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"Brad" <Brad@.discussions.microsoft.com> wrote in message
news:56372080-3701-40DA-8CF1-9B002BDC2E11@.microsoft.com...[vbcol=seagreen]
> Yes, thank you. The domain account I am using is already a member of the
> admin group on both nodes. The error still persists.
> "Geoff N. Hiten" wrote:
|||Yes, it is in the local admin group on both machines.
"Nik Marshall-Blank" wrote:

> Hi,
> But is it the LOCAL ADMIN ACCOUNT not domain admin account?
> --
> Nik Marshall-Blank MCSD/MCDBA
> Linz, Austria
> "Brad" <Brad@.discussions.microsoft.com> wrote in message
> news:56372080-3701-40DA-8CF1-9B002BDC2E11@.microsoft.com...
>
>
|||Make sure the task scheduler service is enabled and running on all nodes.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Brad" <Brad@.discussions.microsoft.com> wrote in message
news:DC6D365B-B9E9-4A59-947C-0A947C91826B@.microsoft.com...[vbcol=seagreen]
> Yes, it is in the local admin group on both machines.
> "Nik Marshall-Blank" wrote:
|||Did you ever get a resolution on this ? I am having the exact same
problem.
I have checked all the obvious problems, like permissions, task
scheduler service running, etc.
I am going to call Microsoft Support tomorrow if I can't figure this
out.
Brad wrote:[vbcol=seagreen]
> I didn't provide that information up front but the account is a member of the
> admin group on both boxes.
> "Michael Hotek" wrote:
sqlsql

Cluster Failover - Setting Affinity

Hi Folks:
How do you script-o-matically set processor affinity on SQL after a
cluster failure?
The purpose is that I'll be failing to a machine with a different
amount of CPU's (4 instead of 8). I want to control what SQL
instances take what amounts of processor.
Is this even possible?
Thanks!
Not that this will help any, but Datacenter allows for this from the Process
Control program
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"The Researcher" <the_re_searcher@.hotmail.com> wrote in message
news:59fe996a.0408300823.1bfbe5d2@.posting.google.c om...
> Hi Folks:
> How do you script-o-matically set processor affinity on SQL after a
> cluster failure?
> The purpose is that I'll be failing to a machine with a different
> amount of CPU's (4 instead of 8). I want to control what SQL
> instances take what amounts of processor.
> Is this even possible?
> Thanks!
|||... then I wonder if you can do it in WSRM in Win2k3 that allows you to set
percentages etc on processors - it seems to be derived from the Process
Control Tool in Datacenter ?
Andy.
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:eHgTAWrjEHA.1656@.TK2MSFTNGP09.phx.gbl...
> Not that this will help any, but Datacenter allows for this from the
Process
> Control program
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> "The Researcher" <the_re_searcher@.hotmail.com> wrote in message
> news:59fe996a.0408300823.1bfbe5d2@.posting.google.c om...
>
|||Excellent idea Andy! WSRM is not do processors affinity though. It does do
these things:
Set CPU and memory allocation policies on applications. This includes
selecting processes to be managed, and setting resource usage targets or
limits.
Manage CPU utilization (percent CPU in use).
Limit the process working set size (physical resident pages in use).
Manage committed memory (pagefile usage).
Apply policies to users or groups on a Terminal Services application
server.
Apply policies on a date/time schedule.
Generate, store, view, and export resource utilization accounting
records for management, service level agreement (SLA) tracking, and
charge-back purposes.
see
http://www.microsoft.com/windowsserv...fastfacts.mspx
for more on WSRM.
Its a great package and free for EE and DC editions.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Andy Ball" <andy.ball@.remove4spam_greenfell.com> wrote in message
news:O%23xgKBFkEHA.324@.TK2MSFTNGP11.phx.gbl...
> ... then I wonder if you can do it in WSRM in Win2k3 that allows you to
> set
> percentages etc on processors - it seems to be derived from the Process
> Control Tool in Datacenter ?
> Andy.
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:eHgTAWrjEHA.1656@.TK2MSFTNGP09.phx.gbl...
> Process
>
|||Dang English language and spell chuckers! WSRM is not do processors affinity
though - Should be WSRM does not do processors affinity.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:uunBBKJkEHA.3712@.TK2MSFTNGP15.phx.gbl...
> Excellent idea Andy! WSRM is not do processors affinity though. It does do
> these things:
> Set CPU and memory allocation policies on applications. This includes
> selecting processes to be managed, and setting resource usage targets or
> limits.
> Manage CPU utilization (percent CPU in use).
> Limit the process working set size (physical resident pages in
> use).
> Manage committed memory (pagefile usage).
> Apply policies to users or groups on a Terminal Services
> application server.
> Apply policies on a date/time schedule.
> Generate, store, view, and export resource utilization accounting
> records for management, service level agreement (SLA) tracking, and
> charge-back purposes.
>
> see
> http://www.microsoft.com/windowsserv...fastfacts.mspx
> for more on WSRM.
> Its a great package and free for EE and DC editions.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> "Andy Ball" <andy.ball@.remove4spam_greenfell.com> wrote in message
> news:O%23xgKBFkEHA.324@.TK2MSFTNGP11.phx.gbl...
>
|||"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in message news:<eHgTAWrjEHA.1656@.TK2MSFTNGP09.phx.gbl>...
> Not that this will help any, but Datacenter allows for this from the Process
> Control program
ehr, I just checked with the WSRM site and found the following snippet:
It is not recommended that you use WSRM CPU affinity for SQL Server 2000.
That being said, it doesn't appear as though that's going to work.
Any other suggestions?
Thx
sqlsql

Cluster failing connections with SSL error message

We recently migrated our production environment from a win2k3/SQL 2000 EE cluster to a new 64 bit win2k3/ SQL 2005 SP1 Cluster.

Cluster works fine for a while (3-6 hours), then our logins start failing. We recieve the following error in the event log:

"The server was unable to load the SSL provider library needed to log in; the connection has been closed. SSL is used to encrypt either the login sequence or all communications, depending on how the administrator has configured the server. See Books Online for information on this error message"

The only way to resume connectivity is to offline and online the sql service in the cluster.

The only reference to this error that I can find has something to do with a hotfix that might be available?

It's sad to say but we are experiencing the same issue.
Only we get this after a good 30 minutes...

Someone from Microsoft Spain is flying over here.

Very painful

|||

In working with microsoft PSS, we found the issue to be a permissions issue of all things.

Our service account did not have rights to lock pages in memory on either machines in the cluster. (even though is a domain administrator).

Once we gave it this right and restarted the SQL Server object in the cluster we have not had a similar failure since.

|||

This was unfortunately enabled already so it did not cause the problem here :-(

|||Hi Wesley,

Any joy with this? I'm currently going throught the same thing, and also have locked pages enabled for my SQL service account. I'm currently going through MS Support, but seem to be going around the houses :o(

Thanks

Stu|||Any luck, we have a similar problem.
We noticed that memory usage grows slowly beyond physical memory (32G) then connection failiurs start and server becomes inoperable.
Workaround solution is to reduce max mem in the server, down to 18G from (25).
This causes the server and OS to release memory. After the system stabilized we increased the maxmem in the server back to its original settng. Lock pages in memory is set.

Hope this helps.

This is a workaround, so we don't have to bounce the server, we are still looking for the cause.
esk.

Setup:2 node Cluster 4*dual 64bit AMD, 32Gb, SQL 2005 Enterprise SP0.|||

Hi,

Apparently we have hit a bug where the usercache size becomes too large and for every execution of a statement SQL Server has to check this store.
This store is not cleaned and keep growing too the point where lookups become blocked with spinlocks. If you want I can give you the commands to check this.

This will be fixed in SP2 because of the major impact a fix would have. The workaround is adding the users to the sysadmin group or clearing the cache manually with DBCC FREESYSTEMCACHE.

HTH

Kind regards,
Wesley

|||Thanks for the replies !

Wes, if you could give the command to check the spinlocks that would be great.

many thanks

Stu|||

Stu,

It's actually the query for checking the cache size.

SELECT * FROM sys.dm_os_memory_clerks
WHERE type = 'USERSTORE_TOKENPERM'
We have seen problems as of 150MB in our environment but this probably all depends on the load and types of queries. Add up the single pages and multipages to determine the size.

HTH
Wesley

|||Thanks Wesley!

After much investigation it turned out the problem was the iLO Management Channel Interface Driver (Cpqcidrv.sys) from Hewlett-Packard. Apparently this

is known to cause this issue on x64 editions of SQL Server 2005. The driver

causes the SQL Server 2005 64-bit working set to be trimmed!


We do not use ILO on our HP Servers, so I disable it in device manager, and so far so good (fingers crossed)!!!

Thanks

Stu|||

Great news!

There seems to be a hotfix for Windows 2003 concerning working set trims too.
Apparently working sets get trimmed when you use Terminal Services on the server... so beware ;-)

|||

If possible could you share the hotfix number? Thanks in advance,

Drew

|||

Hey Wesley. Can you please elaborate more on this 'working sets get trimmed' and beware. and the hotfix available? Thank you very much. I've had problems with this also.

|||

I am also have a problem with this issue. I am going to try disabling the ILO. The terminal service hotfix seems to be this one:

http://support.microsoft.com/kb/905865/en-us

sqlsql

Cluster failing connections with SSL error message

We recently migrated our production environment from a win2k3/SQL 2000 EE cluster to a new 64 bit win2k3/ SQL 2005 SP1 Cluster.

Cluster works fine for a while (3-6 hours), then our logins start failing. We recieve the following error in the event log:

"The server was unable to load the SSL provider library needed to log in; the connection has been closed. SSL is used to encrypt either the login sequence or all communications, depending on how the administrator has configured the server. See Books Online for information on this error message"

The only way to resume connectivity is to offline and online the sql service in the cluster.

The only reference to this error that I can find has something to do with a hotfix that might be available?

It's sad to say but we are experiencing the same issue.
Only we get this after a good 30 minutes...

Someone from Microsoft Spain is flying over here.

Very painful

|||

In working with microsoft PSS, we found the issue to be a permissions issue of all things.

Our service account did not have rights to lock pages in memory on either machines in the cluster. (even though is a domain administrator).

Once we gave it this right and restarted the SQL Server object in the cluster we have not had a similar failure since.

|||

This was unfortunately enabled already so it did not cause the problem here :-(

|||Hi Wesley,

Any joy with this? I'm currently going throught the same thing, and also have locked pages enabled for my SQL service account. I'm currently going through MS Support, but seem to be going around the houses :o(

Thanks

Stu|||Any luck, we have a similar problem.
We noticed that memory usage grows slowly beyond physical memory (32G) then connection failiurs start and server becomes inoperable.
Workaround solution is to reduce max mem in the server, down to 18G from (25).
This causes the server and OS to release memory. After the system stabilized we increased the maxmem in the server back to its original settng. Lock pages in memory is set.

Hope this helps.

This is a workaround, so we don't have to bounce the server, we are still looking for the cause.
esk.

Setup:2 node Cluster 4*dual 64bit AMD, 32Gb, SQL 2005 Enterprise SP0.|||

Hi,

Apparently we have hit a bug where the usercache size becomes too large and for every execution of a statement SQL Server has to check this store.
This store is not cleaned and keep growing too the point where lookups become blocked with spinlocks. If you want I can give you the commands to check this.

This will be fixed in SP2 because of the major impact a fix would have. The workaround is adding the users to the sysadmin group or clearing the cache manually with DBCC FREESYSTEMCACHE.

HTH

Kind regards,
Wesley

|||Thanks for the replies !

Wes, if you could give the command to check the spinlocks that would be great.

many thanks

Stu|||

Stu,

It's actually the query for checking the cache size.

SELECT * FROM sys.dm_os_memory_clerks
WHERE type = 'USERSTORE_TOKENPERM'
We have seen problems as of 150MB in our environment but this probably all depends on the load and types of queries. Add up the single pages and multipages to determine the size.

HTH
Wesley

|||Thanks Wesley!

After much investigation it turned out the problem was the iLO Management Channel Interface Driver (Cpqcidrv.sys) from Hewlett-Packard. Apparently this

is known to cause this issue on x64 editions of SQL Server 2005. The driver

causes the SQL Server 2005 64-bit working set to be trimmed!


We do not use ILO on our HP Servers, so I disable it in device manager, and so far so good (fingers crossed)!!!

Thanks

Stu|||

Great news!

There seems to be a hotfix for Windows 2003 concerning working set trims too.
Apparently working sets get trimmed when you use Terminal Services on the server... so beware ;-)

|||

If possible could you share the hotfix number? Thanks in advance,

Drew

|||

Hey Wesley. Can you please elaborate more on this 'working sets get trimmed' and beware. and the hotfix available? Thank you very much. I've had problems with this also.

|||

I am also have a problem with this issue. I am going to try disabling the ILO. The terminal service hotfix seems to be this one:

http://support.microsoft.com/kb/905865/en-us

Cluster failing connections with SSL error message

We recently migrated our production environment from a win2k3/SQL 2000 EE cluster to a new 64 bit win2k3/ SQL 2005 SP1 Cluster.

Cluster works fine for a while (3-6 hours), then our logins start failing. We recieve the following error in the event log:

"The server was unable to load the SSL provider library needed to log in; the connection has been closed. SSL is used to encrypt either the login sequence or all communications, depending on how the administrator has configured the server. See Books Online for information on this error message"

The only way to resume connectivity is to offline and online the sql service in the cluster.

The only reference to this error that I can find has something to do with a hotfix that might be available?

It's sad to say but we are experiencing the same issue.
Only we get this after a good 30 minutes...

Someone from Microsoft Spain is flying over here.

Very painful

|||

In working with microsoft PSS, we found the issue to be a permissions issue of all things.

Our service account did not have rights to lock pages in memory on either machines in the cluster. (even though is a domain administrator).

Once we gave it this right and restarted the SQL Server object in the cluster we have not had a similar failure since.

|||

This was unfortunately enabled already so it did not cause the problem here :-(

|||Hi Wesley,

Any joy with this? I'm currently going throught the same thing, and also have locked pages enabled for my SQL service account. I'm currently going through MS Support, but seem to be going around the houses :o(

Thanks

Stu|||Any luck, we have a similar problem.
We noticed that memory usage grows slowly beyond physical memory (32G) then connection failiurs start and server becomes inoperable.
Workaround solution is to reduce max mem in the server, down to 18G from (25).
This causes the server and OS to release memory. After the system stabilized we increased the maxmem in the server back to its original settng. Lock pages in memory is set.

Hope this helps.

This is a workaround, so we don't have to bounce the server, we are still looking for the cause.
esk.

Setup:2 node Cluster 4*dual 64bit AMD, 32Gb, SQL 2005 Enterprise SP0.|||

Hi,

Apparently we have hit a bug where the usercache size becomes too large and for every execution of a statement SQL Server has to check this store.
This store is not cleaned and keep growing too the point where lookups become blocked with spinlocks. If you want I can give you the commands to check this.

This will be fixed in SP2 because of the major impact a fix would have. The workaround is adding the users to the sysadmin group or clearing the cache manually with DBCC FREESYSTEMCACHE.

HTH

Kind regards,
Wesley

|||Thanks for the replies !

Wes, if you could give the command to check the spinlocks that would be great.

many thanks

Stu|||

Stu,

It's actually the query for checking the cache size.

SELECT * FROM sys.dm_os_memory_clerks
WHERE type = 'USERSTORE_TOKENPERM'
We have seen problems as of 150MB in our environment but this probably all depends on the load and types of queries. Add up the single pages and multipages to determine the size.

HTH
Wesley

|||Thanks Wesley!

After much investigation it turned out the problem was the iLO Management Channel Interface Driver (Cpqcidrv.sys) from Hewlett-Packard. Apparently this

is known to cause this issue on x64 editions of SQL Server 2005. The driver

causes the SQL Server 2005 64-bit working set to be trimmed!


We do not use ILO on our HP Servers, so I disable it in device manager, and so far so good (fingers crossed)!!!

Thanks

Stu|||

Great news!

There seems to be a hotfix for Windows 2003 concerning working set trims too.
Apparently working sets get trimmed when you use Terminal Services on the server... so beware ;-)

|||

If possible could you share the hotfix number? Thanks in advance,

Drew

|||

Hey Wesley. Can you please elaborate more on this 'working sets get trimmed' and beware. and the hotfix available? Thank you very much. I've had problems with this also.

|||

I am also have a problem with this issue. I am going to try disabling the ILO. The terminal service hotfix seems to be this one:

http://support.microsoft.com/kb/905865/en-us

Cluster failing connections with SSL error message

We recently migrated our production environment from a win2k3/SQL 2000 EE cluster to a new 64 bit win2k3/ SQL 2005 SP1 Cluster.

Cluster works fine for a while (3-6 hours), then our logins start failing. We recieve the following error in the event log:

"The server was unable to load the SSL provider library needed to log in; the connection has been closed. SSL is used to encrypt either the login sequence or all communications, depending on how the administrator has configured the server. See Books Online for information on this error message"

The only way to resume connectivity is to offline and online the sql service in the cluster.

The only reference to this error that I can find has something to do with a hotfix that might be available?

It's sad to say but we are experiencing the same issue.
Only we get this after a good 30 minutes...

Someone from Microsoft Spain is flying over here.

Very painful

|||

In working with microsoft PSS, we found the issue to be a permissions issue of all things.

Our service account did not have rights to lock pages in memory on either machines in the cluster. (even though is a domain administrator).

Once we gave it this right and restarted the SQL Server object in the cluster we have not had a similar failure since.

|||

This was unfortunately enabled already so it did not cause the problem here :-(

|||Hi Wesley,

Any joy with this? I'm currently going throught the same thing, and also have locked pages enabled for my SQL service account. I'm currently going through MS Support, but seem to be going around the houses :o(

Thanks

Stu|||Any luck, we have a similar problem.
We noticed that memory usage grows slowly beyond physical memory (32G) then connection failiurs start and server becomes inoperable.
Workaround solution is to reduce max mem in the server, down to 18G from (25).
This causes the server and OS to release memory. After the system stabilized we increased the maxmem in the server back to its original settng. Lock pages in memory is set.

Hope this helps.

This is a workaround, so we don't have to bounce the server, we are still looking for the cause.
esk.

Setup:2 node Cluster 4*dual 64bit AMD, 32Gb, SQL 2005 Enterprise SP0.|||

Hi,

Apparently we have hit a bug where the usercache size becomes too large and for every execution of a statement SQL Server has to check this store.
This store is not cleaned and keep growing too the point where lookups become blocked with spinlocks. If you want I can give you the commands to check this.

This will be fixed in SP2 because of the major impact a fix would have. The workaround is adding the users to the sysadmin group or clearing the cache manually with DBCC FREESYSTEMCACHE.

HTH

Kind regards,
Wesley

|||Thanks for the replies !

Wes, if you could give the command to check the spinlocks that would be great.

many thanks

Stu|||

Stu,

It's actually the query for checking the cache size.

SELECT * FROM sys.dm_os_memory_clerks
WHERE type = 'USERSTORE_TOKENPERM'
We have seen problems as of 150MB in our environment but this probably all depends on the load and types of queries. Add up the single pages and multipages to determine the size.

HTH
Wesley

|||Thanks Wesley!

After much investigation it turned out the problem was the iLO Management Channel Interface Driver (Cpqcidrv.sys) from Hewlett-Packard. Apparently this

is known to cause this issue on x64 editions of SQL Server 2005. The driver

causes the SQL Server 2005 64-bit working set to be trimmed!


We do not use ILO on our HP Servers, so I disable it in device manager, and so far so good (fingers crossed)!!!

Thanks

Stu|||

Great news!

There seems to be a hotfix for Windows 2003 concerning working set trims too.
Apparently working sets get trimmed when you use Terminal Services on the server... so beware ;-)

|||

If possible could you share the hotfix number? Thanks in advance,

Drew

|||

Hey Wesley. Can you please elaborate more on this 'working sets get trimmed' and beware. and the hotfix available? Thank you very much. I've had problems with this also.

|||

I am also have a problem with this issue. I am going to try disabling the ILO. The terminal service hotfix seems to be this one:

http://support.microsoft.com/kb/905865/en-us