Cannot join tables used in the workbook. Join "" not found in the EUL

Question

Does anybody have any idea on this error?
We are getting it from our new server. We exported and inported the EUL from the old server.
Thanks,
Dave

Answer 1

I was just looking at the Disco Admin documentation on technet for version 9 to see if there's any major difference between v4, v9 and v10 and it looks about the same.
If you're exporting from the Admin program directly then I assume you chose to export the entire EUL?
I usually use the batch version (DOS) and I've cut the following text from the export command line as right at the top you can see how it's supposed to handle joins.
Did you not receive any kind of warning when importing the .eex file (ie: something didn't exist for the join to resolve, etc)?
Also, was this a new EUL or an existing one?
If existing, did it warn you about a folder may already exist so it changed the name of the folder by appending a number (ie: _1)?
==========================================================
/export (EUL objects)
This command enables you to export EUL objects to a Discoverer export file (EEX file). You can selectively export individual EUL objects (e.g. folders, business areas, functions) or entire EULs (using the /all modifier). When you import multiple files, Discoverer automatically resolves references between the files. For example, you can export the Emp folder in fileA.eex and the Dept folder in fileB.eex. If Emp and Dept are joined, the join information will actually be in both files, but neither file contains the information for both folders. If you import both files, the join will be recreated when the second file is processed.
Information Details
Syntax:
/export <filename> [<bus_area_name>]
Or
/export <filename> <modifier(s)> [identifier]
Modifiers:
"/all"
/asm_policy <asm policy>
"/audit_info" <audit details>
"/business_area" <business area>
"/external_element" <filename> (this filename refers to an xml file,
not the export filename)
"/folder" <folder>
"/function" <function>
"/hierarchy" <hierarchy>
"/identifier"
"/item_class" <item_class>
"/log" <log file name> [log_only]
"/summary" <summary>
/set_created_by <creator name>
/set_updated_by <updated name>
"/show_progress"
"/workbook" <workbook> [XML_workbook]
"/xmlworkbook" (takes no parameters)
Notes:
<filename> - The name of the target *.EEX file. If a directory path is not specified, the target file is created in the default Discoverer folder. To override the default target directory setting, specify a directory path for the file, for example c:\data\sales.eex . Note that the directory path must be an absolute path, not a relative path.
Wildcards are not allowed for parameters (e.g. business areas, folders) these must be named explicitly.
[<bus_area_name>] - Use this option to export an entire business area and contents. If you only want to export the business area definition and metadata for the contents, use the /business_area modifier.
When you export a business area using the /business_area modifier, Discoverer exports only business area definitions and links to the folders in the business area. Discoverer will export the folders and workbooks only when they are specified by name.
<modifiers> - When specifying parameters, you can use either their Display Name or Identifier.
To maintain data relationships, you must also export linked (or joined) objects.
Example:
To export two business areas named Test BA and Final BA, residing in an EUL named eul31, into a file named export.eex, and write to a log file named export.log, enter:
dis5adm.exe /connect me/mypassword@database /export export.eex "Test BA, Final BA" /eul eul31 /log export.log
Message was edited by:
russ_proudman