I need more information for this case, because I meet such situation second time, please create ticket and reply in PM with number I will ask additional information
Hi there. I'm experiencing the exact same issue with one of the laptops I support. Here's my configuration: MacBookPro 3,1 (Intel Core2 Duo) Brand new installation of Leopard 10.5.4 Brand new installation of Windows XP Pro SP2 with all updates installed using Boot Camp Leopard is bound to an OD server but all accounts are local ones Parallels v3 build 5806 I've been doing some google searching about this issue, and I found a post from someone saying that they got this error after deleting a bunch of Login items which are apparently added by Parallels. I also know that binding a Mac to an AD or OD server can cause a weird crash/bug when accessing Login Items. But, after doing a Parallels install I didn't see anything added into the Login Items so maybe this is just a red herring. I already have a ticket open, 557701 but from my past experience with the ticketing system, I'm not expecting any miracles. So in the meantime I put the installer on the users desktop and told him to reinstall every time he's done using Bootcamp.
Can you please account to somewhere, I can download it, for example to rapidshare. Also we reply ticket information in email is sending to requestor (your email)
I think you can get to the ticketing system by going to https://support.parallels.com/ but to initially open a ticket, go to http://www.parallels.com/en/support/desktop/request/ In the response from Parallels to my ticket I was asked to uninstall Symantec Antivirus from the Mac (version 10.2) and the problem seems to have gone away. I'm working on the machine remotely though and the user has stepped away from his machine. I've now reinstalled Symantec and when he gets back I will ask him to restart into Windows, then go back to OSX and try Parallels again. If the problem comes back, we have VMware Fusion here and next week I will try installing that to see if that also fixes the problem for me. Unfortunately, not having Antivirus isn't an option for us and the entire company is running on Symantec AV 10.2
Oh, and the reason Symantec was suspected to be the problem is because the app was designed for PPC mac computers. The Rosetta processor or whatever it's called that translates old code might be the cause. Symantec is the only PPC app we have installed that I know of. If you open Activity Monitor on the Mac, one of the sorting columns is "Kind" which tells if the process is Intel-based or PPC-based - You might want to try killing the PPC processes. Still haven't verified that reinstalling Symantec makes the problem come back though.
PPC version is not compatible and that was created problems, I suppose others also has such kind of software I didn't check but I believe that Symantec have Intel Compatible version
It looks like I've also had a magic fix. Uninstalling Symantec as Parallels support recommended did in fact fix the problem. But then after reinstalling it, the problem was still gone! That's pretty weird, but at least it's working.
I just had a second computer have this exact same problem. I wiped the Mac partition and put a fresh install of Leopard on it. Installed Symantec Antivirus 10.2 and a couple other misc. things like XCode. Then I installed Parallels and configured Boot Camp. After restarting into Windows and then restarting back into Leopard, Parallels wouldn't open and said it was having driver errors and needed to be reinstalled. I uninstalled Symantec and verified the problem went away. Then I reinstalled Symantec, did a reinstall of Parallels and the problem did not come back when switching between Boot Camp and Leopard. Moral of the story for anyone having this error message repeatedly: If you have a PPC app or Antivirus app, reinstall the app and then reinstall Parallels. It might just work fine. Still seems weird to me but I hope this helps other people out there.
