We were running Windows SBS-2000 and recently upgraded to SBS-2003 R2 ...

It was a clean installation where I had to disjoint the Workstations from
the old Domain then re-join them to the new Domain running SBS-2003 ...

After the deployment went fine, every now and then, I get calls from
randomUsers indicating that when they try to login every morning they get the
following error pop-up box:

Windows cannot load the locally stored
profile. Possible causes of this error
include insufficient security rights or a
corrupt local profile. If this problem
persists, contact your network
administrator.

Then it starts counting 30 sec. and pops the 2nd message box:

Windows cannot find the local profile and
is logging you on with a temporary profile.
Changes you make to this profile will be
lost when you log off.



The User is then logged to a [ Temp ] profile with minimum network resources.

After they Shutdown and Restart, they can log again with no problems ...

The only GPO that is running on the PDC is providing the following:

- Network Drive Mapping
- Network Print Mapping
- Active Desktop Enabled with a JPG image stored on Server

I have read that it might be because of the Active Desktop or the long login
idle mode as Users log poff each day and leave their workstation on the login
screen ...

Can anyone give me so ideas about how to solve that issue ...

Thanks in advance ...

As the error indicates, it's often a corrupt profile.

First thing I'd do is chkdsk the computers this is happening to, eg:
chkdsk c: /f

If the problem persists, I'd rejoin them, which will make a new profile
(backup the old one just in case, but typically, it'll leave it behind
and make a new one). And then manually migrate the old user settings
and data across.

--
Duncan.

In article <FDA3CD8B-FF51-402D-AB71-EACACB2AEDB9@newsgroup>,
RedaHanna@newsgroup says...

> We were running Windows SBS-2000 and recently upgraded to SBS-2003 R2 ...
>
> It was a clean installation where I had to disjoint the Workstations from
> the old Domain then re-join them to the new Domain running SBS-2003 ...
>
> After the deployment went fine, every now and then, I get calls from
> randomUsers indicating that when they try to login every morning they get the
> following error pop-up box:
>
> Windows cannot load the locally stored
> profile. Possible causes of this error
> include insufficient security rights or a
> corrupt local profile. If this problem
> persists, contact your network
> administrator.
>
> Then it starts counting 30 sec. and pops the 2nd message box:
>
> Windows cannot find the local profile and
> is logging you on with a temporary profile.
> Changes you make to this profile will be
> lost when you log off.
>
> The User is then logged to a [ Temp ] profile with minimum network resources.
>
> After they Shutdown and Restart, they can log again with no problems ...
>
> The only GPO that is running on the PDC is providing the following:
>
> - Network Drive Mapping
> - Network Print Mapping
> - Active Desktop Enabled with a JPG image stored on Server
>
> I have read that it might be because of the Active Desktop or the long login
> idle mode as Users log poff each day and leave their workstation on the login
> screen ...
>
> Can anyone give me so ideas about how to solve that issue ...
>
> Thanks in advance ...
>

I don't know how often it really is corrupt--I bet in most cases it's
perfectly fine. I think this is more a long-standing bug that rears its head
randomly and indiscriminately right up through current-day OS's (i.e. not
just XP). I've even seen the SBS server itself do it!

This is what I've used to fix it on more than one occasion (Step 4 being the
focus here):
http://www.ehow.com/how_4718523_repl...r-profile.html

If anyone knows of a way to make this idiotic issue from happening in the
first place, I'd love to know about it. Perhaps, as the article suggests,
it's a matter of timing. Perhaps a timeout value somewhere in the Registry?

"Duncan McC" <hard@newsgroup> wrote in message
news:MPG.2536b3915035165d989b20@newsgroup

> As the error indicates, it's often a corrupt profile.
>
> First thing I'd do is chkdsk the computers this is happening to, eg:
> chkdsk c: /f
>
> If the problem persists, I'd rejoin them, which will make a new profile
> (backup the old one just in case, but typically, it'll leave it behind
> and make a new one). And then manually migrate the old user settings
> and data across.
>
> --
> Duncan.
>
> In article <FDA3CD8B-FF51-402D-AB71-EACACB2AEDB9@newsgroup>,
> RedaHanna@newsgroup says...

>> We were running Windows SBS-2000 and recently upgraded to SBS-2003 R2 ...
>>
>> It was a clean installation where I had to disjoint the Workstations from
>> the old Domain then re-join them to the new Domain running SBS-2003 ...
>>
>> After the deployment went fine, every now and then, I get calls from
>> randomUsers indicating that when they try to login every morning they get
>> the
>> following error pop-up box:
>>
>> Windows cannot load the locally stored
>> profile. Possible causes of this error
>> include insufficient security rights or a
>> corrupt local profile. If this problem
>> persists, contact your network
>> administrator.
>>
>> Then it starts counting 30 sec. and pops the 2nd message box:
>>
>> Windows cannot find the local profile and
>> is logging you on with a temporary profile.
>> Changes you make to this profile will be
>> lost when you log off.
>>
>> The User is then logged to a [ Temp ] profile with minimum network
>> resources.
>>
>> After they Shutdown and Restart, they can log again with no problems ...
>>
>> The only GPO that is running on the PDC is providing the following:
>>
>> - Network Drive Mapping
>> - Network Print Mapping
>> - Active Desktop Enabled with a JPG image stored on Server
>>
>> I have read that it might be because of the Active Desktop or the long
>> login
>> idle mode as Users log poff each day and leave their workstation on the
>> login
>> screen ...
>>
>> Can anyone give me so ideas about how to solve that issue ...
>>
>> Thanks in advance ...
>>

>

Yes, that's true - so have I - even on SBS servers.

If it's pretty rare - once or twice a year - I'd not worry about it.

I think it helps to run the profile cleanup wizard on all computers
(including Servers).

http://www.microsoft.com/Downloads/d...1B286E6D-8912-
4E18-B570-42470E2F3582&displaylang=en

(sorry about the long link - I'm sure you'll be able to unwrap it

--
Duncan.

In article <#R6zL5vRKHA.1372@newsgroup>, btvs@newsgroup
says...

> I don't know how often it really is corrupt--I bet in most cases it's
> perfectly fine. I think this is more a long-standing bug that rears its head
> randomly and indiscriminately right up through current-day OS's (i.e. not
> just XP). I've even seen the SBS server itself do it!
>
> This is what I've used to fix it on more than one occasion (Step 4 being the
> focus here):
> http://www.ehow.com/how_4718523_repl...r-profile.html
>
> If anyone knows of a way to make this idiotic issue from happening in the
> first place, I'd love to know about it. Perhaps, as the article suggests,
> it's a matter of timing. Perhaps a timeout value somewhere in the Registry?
>
> "Duncan McC" <hard@newsgroup> wrote in message
> news:MPG.2536b3915035165d989b20@newsgroup

> > As the error indicates, it's often a corrupt profile.
> >
> > First thing I'd do is chkdsk the computers this is happening to, eg:
> > chkdsk c: /f
> >
> > If the problem persists, I'd rejoin them, which will make a new profile
> > (backup the old one just in case, but typically, it'll leave it behind
> > and make a new one). And then manually migrate the old user settings
> > and data across.
> >
> > --
> > Duncan.
> >
> > In article <FDA3CD8B-FF51-402D-AB71-EACACB2AEDB9@newsgroup>,
> > RedaHanna@newsgroup says...

> >> We were running Windows SBS-2000 and recently upgraded to SBS-2003 R2 ...
> >>
> >> It was a clean installation where I had to disjoint the Workstations from
> >> the old Domain then re-join them to the new Domain running SBS-2003 ...
> >>
> >> After the deployment went fine, every now and then, I get calls from
> >> randomUsers indicating that when they try to login every morning they get
> >> the
> >> following error pop-up box:
> >>
> >> Windows cannot load the locally stored
> >> profile. Possible causes of this error
> >> include insufficient security rights or a
> >> corrupt local profile. If this problem
> >> persists, contact your network
> >> administrator.
> >>
> >> Then it starts counting 30 sec. and pops the 2nd message box:
> >>
> >> Windows cannot find the local profile and
> >> is logging you on with a temporary profile.
> >> Changes you make to this profile will be
> >> lost when you log off.
> >>
> >> The User is then logged to a [ Temp ] profile with minimum network
> >> resources.
> >>
> >> After they Shutdown and Restart, they can log again with no problems ...
> >>
> >> The only GPO that is running on the PDC is providing the following:
> >>
> >> - Network Drive Mapping
> >> - Network Print Mapping
> >> - Active Desktop Enabled with a JPG image stored on Server
> >>
> >> I have read that it might be because of the Active Desktop or the long
> >> login
> >> idle mode as Users log poff each day and leave their workstation on the
> >> login
> >> screen ...
> >>
> >> Can anyone give me so ideas about how to solve that issue ...
> >>
> >> Thanks in advance ...
> >>

> >

>

Hello,

Thank you for posting here.

According to your description, I understand that:

After you upgrade to the SBS 2003, random users report that they cannot
logon with the local profile.

If I have misunderstood the problem, please don't hesitate to let me know.

Agree with Duncan that you should make sure whether the hard disk is OK for
those problematic users. If the disk scan passes without errors, please
answer the following questions for further investigations:

1. How many users are affected with the profile loading error? Is it
related to the workstation that the user logs onto? You may have a record
of which user gets the error and on which the user logs onto.

2. If you detect a issue, check how it works if you recreate the profile
for the problematic user on the workstation he logs onto.

If you have any questions or concerns, please do not hesitate to let me
know.

Best regards,

Miles Li

Microsoft Online Newsgroup Support

==================================================================
Please post your SBS 2008 related questions to the SBS newsgroup on Connect
website:
https://connect.microsoft.com/sbs08/...i/default.aspx


Please post your EBS related questions to the EBS newsgroup on Connect
website:
https://connect.microsoft.com/ebs08/...i/default.aspx


If you want to use a newsreader other than a web forum to access these
newsgroups,
please refer to the following blog to apply NNTP password and configure a
newsreader:
http://msmvps.com/blogs/bradley/arch...for-the-sbs-20
08-newsgroups.aspx
==================================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
==================================================================

Thanks for the different thoughts ...

I have installed the the User Profile Hive Cleanup Service on all
Workstations of the problematic Users ... Again randomly, they will get this
error ...

The issue started when moving to SBS2003-R2 whereas I have other Clients
that run SBS2003 and have no problems ...

I am still concerned about the GPO for Active Desktop that pushes the
Companies Backgrounds and locks the Users from changing it ...

Also, I have googled tons of articles and no one have a definite answer ...

Any ideas or thoughts will be apppreciated ...

Reda


"Miles Li [MSFT]" wrote:

> Hello,
>
> Thank you for posting here.
>
> According to your description, I understand that:
>
> After you upgrade to the SBS 2003, random users report that they cannot
> logon with the local profile.
>
> If I have misunderstood the problem, please don't hesitate to let me know.
>
> Agree with Duncan that you should make sure whether the hard disk is OK for
> those problematic users. If the disk scan passes without errors, please
> answer the following questions for further investigations:
>
> 1. How many users are affected with the profile loading error? Is it
> related to the workstation that the user logs onto? You may have a record
> of which user gets the error and on which the user logs onto.
>
> 2. If you detect a issue, check how it works if you recreate the profile
> for the problematic user on the workstation he logs onto.
>
> If you have any questions or concerns, please do not hesitate to let me
> know.
>
> Best regards,
>
> Miles Li
>
> Microsoft Online Newsgroup Support
>
> ==================================================================
> Please post your SBS 2008 related questions to the SBS newsgroup on Connect
> website:
> https://connect.microsoft.com/sbs08/...i/default.aspx
>
>
> Please post your EBS related questions to the EBS newsgroup on Connect
> website:
> https://connect.microsoft.com/ebs08/...i/default.aspx
>
>
> If you want to use a newsreader other than a web forum to access these
> newsgroups,
> please refer to the following blog to apply NNTP password and configure a
> newsreader:
> http://msmvps.com/blogs/bradley/arch...for-the-sbs-20
> 08-newsgroups.aspx
> ==================================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ==================================================================
>
>