Failed to create empty document.

[m.a.m]

When starting EA 7.1 (Build 833), a warning box with text "Failed to create empty document." appears (see cable000 from 11/20/08). EA doesn't start.

Deinstallation and new installation didn't help.

Env: XP Professional, EA Corporate with Floating license

Can anybody help me please?

[«Midnight»]

This is only a guess...

First, check to make absolutely sure you can reach the license server, and that you have sufficient privilege to read (perhaps to write) to the key store file.

Check out the note - it is someplace on the Sparx site or the EA documentation - regarding the Jet driver from Microsoft. For some recent Windows configurations, particularly those without MS Office, you might need to download and install a legacy driver.

There might be a registry tweak you can use to force EA to use the Jet 4.0 driver. There is a better chance that this is installed by Windows, but even that is no longer assured. I do not know the tweak, but perhaps somebody does.

David

[m.a.m]

Hi David,

we checked the license server, access rights are given (for read and write). We regarded the Jet driver without any result.

At the end, we installed Build 832 and it works without any problem. Perhaps it's a Build 833 problem?

Thanks for your investigations,
mm

[Oliver F.]

When starting EA 7.1 (Build 833), a warning box with text "Failed to create empty document." appears (see cable000 from 11/20/08). EA doesn't start.

Deinstallation and new installation didn't help.

Env: XP Professional, EA Corporate with Floating license

Can anybody help me please?

That might not help you much but I frequently get this when several EA instances are running and EA is not able to open further ones. Propably it runs out of shared memory or it fails creating some locks in the system.

Oliver

[«Midnight»]

It might be worth one or both of you filing a bug report (or a support email) to Sparx.

Sparx might be able to address the problem - at least create a more indicative help message - if they know the specifics of the error.

Who knows, they might even be able to solve the problem.