Abhishek Agrawal [MSFT]

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
>
>