Vista Tutorial - Access Violation after dock / undock?

Has anyone else experienced an Access Violation in powershell.exe after docking
/ undocking a laptop? I don't have an exact repro, but here are some of
the things I have configured that others may not have (I haven't determined
whether or not these items have a direct impact on the problem at hand):

1. Redirected 'My Documents' folder to a network drive
2. 'My Documents' folder made available offline
3. When docked, my laptop has both a wired and wireless connection to the
same subnet (wired connection is higher in binding order)
4. When I launch powershell, I'm placed in my u:\ (redirected mydocs) by
default.
5. Powershell Community Extensions installed
6. MoW's TabCompletion installed

If the current directory is a network drive and I undock my laptop, nearly
any action (even 'cd c:\temp') results in an Access Violation and powershell
needs to be shutdown. The same thing happens if a network drive is the current
directory and I dock my laptop. I haven't completely tested this with all
network drives, but since I'm placed in U:\ at powershell startup and I spend
most of my time there, I'm often see this problem.

I've hesitated to post this, as my company has some pretty strange desktop
/ laptop configurations (including ZenWorks from Novell) and I don't know
what all they have excluded from the standard Windows XP installation.

If anyone else has noticed (or specifically NOT noticed) this, please let
me know and I'll post this to connect as necessary.

Thanks,
Mark

Hi Mark,
I will get this checked out internally and post back.

--
Abhishek Agrawal [MSFT]
Windows PowerShell Team
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mark Ingalls" <mark@nospam.nospam> wrote in message
news:c3aa33fb2c0358c9138f1b5deafa@msnews.microsoft.com...
> Has anyone else experienced an Access Violation in powershell.exe after
> docking / undocking a laptop? I don't have an exact repro, but here are
> some of the things I have configured that others may not have (I haven't
> determined whether or not these items have a direct impact on the problem
> at hand):
>
> 1. Redirected 'My Documents' folder to a network drive
> 2. 'My Documents' folder made available offline
> 3. When docked, my laptop has both a wired and wireless connection to the
> same subnet (wired connection is higher in binding order)
> 4. When I launch powershell, I'm placed in my u:\ (redirected mydocs) by
> default.
> 5. Powershell Community Extensions installed
> 6. MoW's TabCompletion installed
>
> If the current directory is a network drive and I undock my laptop, nearly
> any action (even 'cd c:\temp') results in an Access Violation and
> powershell needs to be shutdown. The same thing happens if a network
> drive is the current directory and I dock my laptop. I haven't completely
> tested this with all network drives, but since I'm placed in U:\ at
> powershell startup and I spend most of my time there, I'm often see this
> problem.
>
> I've hesitated to post this, as my company has some pretty strange desktop
> / laptop configurations (including ZenWorks from Novell) and I don't know
> what all they have excluded from the standard Windows XP installation.
>
> If anyone else has noticed (or specifically NOT noticed) this, please let
> me know and I'll post this to connect as necessary.
>
> Thanks,
> Mark
>
>

Hello Abhishek Agrawal [MSFT],

> Hi Mark,
> I will get this checked out internally and post back.
> "Mark Ingalls" <mark@nospam.nospam> wrote in message
> news:c3aa33fb2c0358c9138f1b5deafa@msnews.microsoft.com...
>

I reproduced this error again today. More information:

Setting the working directory to c:\ prior to undocking allowed me to use
'dir' on c:\ after undock

U:\ went into offline status and I was able to 'dir' in u:\ seeing those
files marked for offline access

the windows sync manager came up (after detecting the wireless network) and
u:\ came back online

U:\ went into online status and a 'dir' in u:\ prouced the access violation.

I clicked on the "debug" button, holding out hope that I'd be able to get
something usable from the debug session. Alas, this was not true. Are the
powershell symbols on the msdl symbol server?

the exception thrown was:

System.ExecutionEngineException was unhandled
Message="Exception of type 'System.ExecutionEngineException' was thrown."

which is not too helpful, but I can only post the data I can collect.

thanks,
mark

Hi mark,
Thanks for the information. This is a known bug. We have received other
reports on this issue and it is being investigated further.

--
Abhishek Agrawal [MSFT]
Windows PowerShell Team
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mark Ingalls" <mark@nospam.nospam> wrote in message
news:c3aa33fb2c7898c914012515b182@msnews.microsoft.com...
> Hello Abhishek Agrawal [MSFT],
>
>> Hi Mark,
>> I will get this checked out internally and post back.
>> "Mark Ingalls" <mark@nospam.nospam> wrote in message
>> news:c3aa33fb2c0358c9138f1b5deafa@msnews.microsoft.com...
>>
>
> I reproduced this error again today. More information:
>
> Setting the working directory to c:\ prior to undocking allowed me to use
> 'dir' on c:\ after undock
>
> U:\ went into offline status and I was able to 'dir' in u:\ seeing those
> files marked for offline access
>
> the windows sync manager came up (after detecting the wireless network)
> and u:\ came back online
>
> U:\ went into online status and a 'dir' in u:\ prouced the access
> violation.
>
> I clicked on the "debug" button, holding out hope that I'd be able to get
> something usable from the debug session. Alas, this was not true. Are
> the powershell symbols on the msdl symbol server?
>
> the exception thrown was:
>
> System.ExecutionEngineException was unhandled
> Message="Exception of type 'System.ExecutionEngineException' was thrown."
>
> which is not too helpful, but I can only post the data I can collect.
>
> thanks,
> mark
>
>