Actinic errors on a Mac using Parallels

[AngiW]

Hello,

If Anyone uses Actinic on a Mac Please could someone shed some light on these errors I really don't know what they mean, When my client tries to do a snapshot export she gets this error.

FATAL ERRORS
File SnapshotWizard.cpp, Line 679 - Archive error 5 - The compression operation failed
Library error - Can not open file .\\psl\Home\Documents\Actinic v9\site1\ActinicCatalog.mdb! has been caught.

My client gets this error when she leaves the site and Actinic wants to compact the databases

There was a problem compacting the database
.\\psl\Home\Documents\Actinic v9\site1\ActinicCatalog.mdb with the database.
.\\psl\Home\Documents\Actinic v9\site1\ActinicCatalog.mdb
The reported error was: Drivers ConfigDSN, ConfigDriver, or ConfigTranslator failed please use exporer to investigate the problem.
Actinic will now close and must be restarted.


I have an update on this, I asked the client to send me their site 1 folder as she could not send a snapshot and I added all the files replacing my old ones and I have managed to compact the database and export the site, so I guess it must be the way her machine is configured, I don't really know what to go back with her with, has anyone got any suggestions?

Also she has parallels desktop 4.0 for a mac installed and then ms windows xp pro sp3 if that helps?

Thanks
Angi

 

[Richard Wiggins]

I am using Parallel 5 on two different Macs, one running Windows XP, the other Windows 7. I have tried 'Compacting a database' from within Actinic on both and I also get the same error:

There was a problem compacting the database
.\\psf\Home\Documents\Actinic v9\Sites\Site1\ActinicCatalog.mdb with the database.
.\\psf\Home\Documents\Actinic v9\Sites\Site1\ActinicCatalog.mdb
The reported error was: Drivers ConfigDSN, ConfigDriver, or ConfigTranslator failed please use exporer to investigate the problem.
Actinic will now close and must be restarted.

This only ever happens when running on Parallels.

I have also got a Mac running Parallels 3 with Windows XP. When I try the same procedure on that, it works fine, so must be something to do with Parallels 5.

Any help would be mostly appreciated.

Richard