Answer
This kind of database-information-loading failure, especially on a client machine that ALSO has Crystal Reports Developer installed locally, commonly indicates a Crystal runtime-library version mismatch — the developer-edition libraries installed for report design work can silently overwrite or shadow the runtime libraries that Enterprise Explorer actually needs at print/preview time. Reinstall the Crystal Report Runtime specifically from the Add-ons page on the affected client machine and restart Enterprise Explorer afterward — this resolves this exact mismatch-driven error.