Known Issues and Limitations
This section lists known issues and limitations that have not been resolved yet.
Known Issues Found in Version 7.0
uCreate Print
1. Turning on Marks in the InDesign PDF Export settings dialog (e.g. crop marks or registration marks, found when doing File>Export>PDF in InDesign) causes Dynamic Print to PDF/VT to be offset on the sheet (27571).
Workaround:
Export a page to PDF using the InDesign export (File>Export>PDF>Save) and turn off all Marks. Then, perform the Dynamic Print again.
2. InDesign on a MAC fails to work when the Draw Page Information option is checked under the Imposition view in the Dynamic Print window (24966).
3. XLIM preview does not show images in a Table ADOR Object (25203).
4. In rare cases, when using InDesign CC, the PDF Export Settings view in the Dynamic Print window are missing or disabled (25957).
Workaround:
Reset InDesign to enable it.
5. In some cases, when working with JPEG images and placing the images in a box larger than the image frame (cropped), an Independent Image Rending (IIR) is turned on and consequently, the output file may be larger in size then when the IIR is turned off (27475).
6. InDesign Documents with different page orientation are not supported (27694).
uCreate - uProduce Connectivity
7. The new uCreate - uProduce Connectivity feature is not adapted for Campaigns using Personalized URLs.
Workaround:
For Campaigns using Personalized URLs, please use the classic Import / Export of packages from uCreate Print.
8. When using uCreate - uProduce Connectivity, Ports are created to serve as a connecting point between the desktop and the server. These Ports remain permanently (27151).
9. When using uCreate - uProduce connectivity, changes made to the Plan are saved instantly, even if the Document is not saved to uProduce (27751).
Workaround:
Delete these Ports manually and re-create them again when needed.
uChart
10. When the bar graph in uChart is using numbers greater than 10000, decimal values may get rounded (10,000.01 -> 10,000) (27376).
Installation (uCreate Print, uPlan, uProduce)
11. To support *.accdb files, an upgrade of ACE driver is required if an older version of the driver is installed on the computer. Upgrade is available at http://www.microsoft.com/en-us/download/details.aspx?id=13255 (download file: AccessDatabaseEngine.exe). Note that you will need to uninstall the currently installed ACED driver (via Control Panel) prior to installing the new one.
Upgrade of the ACED driver can occur either before or after installing uCreate Print, uPlan or uProduce.
Production
12. In PPML produciton, Assets are not copied to Secondary Folder destination (26431)
13. Fonts that are used in XNIP or RTF assets, but are absent from the document will not be processed correctly and will result in a missing font error (24346).
Workaround:
a. Install the font on the server(s) as one of the system fonts.
OR
b. (Recommended) Add a text box (or use an existing text box) and add a hidden character that uses the same font, to force the document use the font (a hidden character can be simply a carriage return).
uProduce
14. The File System With Authentication Asset Source Type does not authenticate in a custom uProduce installation, where the uProduce Dashboard and uProduce API are installed on separate machines (27565)..
Known Issues Found in Previous Versions
General
15. Excel 95 is not supported as a Data Source format for . Users wishing to connect to Excel 95 data files, should convert them to Excel 1997-2003 XLS format or to later versions (22656).
Print Production
16. When you run Photoshop on a virtual machine or a computer with a weak graphic adapter, make sure that the Use Graphics Processor option is not selected. You can find the Use Graphics Processor option at Edit > Preferences > General > Performance.
If you do not clear the Use Graphics Processor option, Photoshop will prompt the following warning every time it starts and production may be halted: "Photoshop has encountered a problem with the display driver, and has temporarily disabled enhancements which use the graphics hardware. Check the manufacturer’s website for the latest software. For more information, visit: http://www.adobe.com/go/photoshop_gpu_cc_en.
17. Assets resolving mechanism cannot handle PS (Postscript) Asset file types. Postscript Asset files can only be used with full file name (including extension) in the ADOR (Content) Object value (25478).
18. When using InDesign's Small Caps feature, fonts must be installed on the system. Campaign Fonts are not supported by this functionality (25321).
19. The Bleed functionality does not work properly in an InDesign Document that uses Facing Pages if the "Inside" and "Outside" bleed values are different (23500).
20. Transparency features applied to groups are not maintained in print production.
Workaround:
Assign the transparency features to each element independently (19120).
21. Text Copy Fitting does not work in inline boxes (22036).
22. Converting a string to a number may fail to do so in a reliable manner if the string defines a number containing more than 15 digits. This behavior is tied to range limits of the underlying data type and to a double-precision floating-point number (20177).
23. Unique with Inline optimization might cause production flaws. As a precaution, this optimization is disabled.
24. When a design contains an EPS that embeds a font, then the EPS appears distorted in the output - in some cases. This happens when the font embedded in the EPS is also stored in one of these paths:
● %USERPROFILE%\Application Data\Adobe\InDesign\Version 5.0(or other version)\configuration_17001(or other instance)\CompositeFont
● %USERPROFILE%\Application Data\Adobe\InDesign Server\Version 5.0(or other version)\configuration_17001 (or other instance)\CompositeFont
● %ProgramFiles%\Adobe\Adobe InDesign CS3(or Adobe InDesign CS3 Server or other version)\Fonts
Explanations for the paths above:
● %USERPROFILE% referenced above should be replaced with the root folder for the user that is running InDesign.
§ In the case of desktop production () — item 1 above— this is the root folder of the currently logged in user. A typical example is C:\Documents and Settings\John, where John is the currently logged in user.
§ In the case of server production (uProduce) — item 2 above — this is the root folder of the uProduce service user. Use the Services list in Windows to find which user this is. A typical example is C:\Documents and Settings\operator, where operator is the uProduce service user.
● The Application Data folder referenced above is usually a hidden folder. To show it, take the following steps:
§ Open the C:\Documents and Settings folder in Windows Explorer.
§ From the Tools menu, select Folder Options.
§ Select the View tab, and under the “Hidden files and folders” folder, selected Show hidden files and folders.
§ Click OK.
The Application Data folder should now be visible.
Workaround: Check if the font embedded in the EPS is stored in one of these folders. If it is, move it to the Windows Fonts folder, or place it in Program Files\Common Files\Adobe\Fonts (12188).
25. When an InDesign document uses non-Latin characters, creating a print file without embedding fonts (that is, with "embed fonts" unchecked) causes the text to appear corrupted, although the fonts are available to the printer (or to Acrobat Distiller).
This issue has been reported to Adobe and is being investigated. Note that this problem does not occur in XLIM production (14969).
26. The XMPie Bleed feature creates corrupted output when used in combination with uProduce Global Caching feature (17647).
uImage
27. When running uImage production of XMPie Marketplace templates in Photoshop CC, variable data is not displayed in the output files (26000).
Workaround:
Upgrade Photoshop to version 14.1.2.
28. uImage DPKG import fails if the file path includes Japanese characters. As a workaround, use Latin characters for file names and paths (24347).
29. uImage packaging mechanism does not support text tags that are located in the Smart Objects (24123).
30. After installing a uCreate Print license key that includes uImage, you need to restart InDesign. Until you restart InDesign, a watermark will appear on uImage output files (22318).
31. When exporting CPKGs from uCreate Print referenced uImage DPKGs will not be included (20608).
32. uImage packages that use JavaScript for implementing actions cause production to fail on uProduce. This failure is limited to the packages workflow of uImage. It is still possible to use JavaScript when using the direct templates (PSD files) workflow.
Workaround:
Unpack the uImage package and run production, using the templates directly. You will have to alter the plan definition as well (20251).
33. On some 2008 servers, uImage production may fail. The failure occurs when uImage activates the Photoshop registration dialog, which prevents uImage from operating.
Workaround:
Disable the appearance of the Photoshop registration dialog. Proceed as follows:
a. Open Photoshop on the server.
b. When the registration dialog appears, choose one of the following:
§ Register — the Photoshop registration dialog will not appear again.
§ Be reminded later — the Photoshop registration dialog might appear again, causing uImage production to fail. In that case, repeat this procedure several times, until you are given the option to not be reminded again. Choose this option to prevent the appearance of the Registration dialog (14669).
34. Copy fitting is not supported for paragraph text (text boxes) in Photoshop. Use point text (text lines) instead (6242, 6260, 13977).
uCreate Print
35. When using images with EXIF information (image orientation, for example, for images from iPhone), image rotation will not be honored during production even though InDesign will display them correctly). A possible workaround is to use the Require InDesign Rendering option for PDF and Post Scripts formats (24706).
36. uCreate Print fails to connect to a CSV or TXT file Data Source whose name contains non-Latin characters. The following error message is displayed: “Failed to get table information from data source”.
Workaround:
To overcome this problem, rename the file, so that its name contains Latin characters only (19240).
37. When using a uImage package in a design on uCreate Print, and at the same time making changes to the uImage package (for instance, changing the design in Photoshop, and packing), the changes will not be reflected in the InDesign document.
Workaround:
Close InDesign, reopen it and either run production or browse to a different record. This will update the document to show the modified template (20188).
38. When linking to a Data Source containing a field whose name ends with one or more spaces, the following message is displayed:
"One or more Content Object expressions are not compatible with the Data Source. Modify these expressions (and then link to the Data Source) or link to a compatible Data Source".
To avoid this error, remove all spaces from the end of column titles in your Data Source (7825).
39. If a Document created with InDesign CS3 uses a Text File ADOR Object to include Microsoft Word files, then when producing the Document with uCreate Print , the text in the Text File ADOR Object is aligned to the right instead of the left.
As a workaround, edit the included Word files and change their "Normal" style to be left-aligned (14548).
Qlingo
40. The ICP functionality is incompatible with the "skip" function in Qlingo (23502).
uChart
41. In uChart, text display in Advanced Options may sometimes be incorrect.
For example, writing the command "/LeftScaleFormat (£999,990)" will not display the Pound (£) symbol correctly.
Workaround:
To overcome this problem, avoid using text in Advanced Options (19294).
XLIM
42. The “Text Rotation” feature for tables works correctly only for 0 or 180 degrees. For 90 and 270 degrees, the print output is corrupted (22909).
uProduce
43. When uploading a CPKG that contains an authenticated Asset Source, the password is not restored (27550).
Workaround:
Enter the password again.
44. When sending an email containing
a PDF On-demand while using the Recipient
Data Source option (Email Activity >Recipients section), the PDF-On Demand
link in the sent email is broken.
As a workaround, select the Copy
from Port option in the Recipients section of the Email
Activity (25786).
45. When opening a print job PDF output file on Firefox, the content of the PDF file is not visible. As a workaround, XMPie recommends using Adobe Acrobat as the PDF viewer and not the built-in Firefox PDF viewer to ensure maximized results. For more details, see https://support.mozilla.org/en-US/kb/view-pdf-files-firefox-without-downloading-them (25286).
46. Restart is required after you install uProduce. Please do not ignore the onscreen instructions to restart.
47. There is no option to export a Local Data Source that was originally uploaded as FoxPro to FoxPro (24673).
48. uProduce password may not contain the sequence $$. Otherwise, the RURL wizard will fail to load (23366).
49. To work with FoxPro databases on uProduce, you must install the FoxPro OLEDB driver manually (23905).
50. Exporting a Hosted Data Source to an Excel or Access file fails if the Data Source has more than 256 columns. The following error message is displayed: "Failed to fill exported table by data". To overcome this problem, export the Data Source to a CSV file (19227).
51. Accounts may contain no more than 1255 Campaigns (21341).
52. Non-English Data Sources of type CSV cannot use the “Adapt for the Web” feature.
As a workaround, use Excel or Access Data Sources (15571).
53. Uploading a large Campaign, to either a hosted or non-hosted environment, may sometimes fail. When a failure occurs, you will receive the following message:
"RadUpload Ajax callback error. Source url returned error: 12029 Unknown
../Telerik.RadUploadProgressHandler.ashx?RadUrid=c80c8ce6-c5b8-4f29-8525-bf8d297f348e
Did you register the RadUploadProgressHandler in web.config?
Please, see the help for more details: RadUpload for ASP.NET Ajax - Configuration - RadUploadProgressHandler."
To resolve this issue, try one of the following solutions:
● Upload the Campaign again
● Upload a small Campaign (for example, without the Assets, adding them later)
● Create a new Campaign on uProduce and upload the material components separately (16140).
54. In uProduce, hosting a ZIP file containing an Excel
file of a large size fails.
An operation time-out error message is received in the Process step.
As a workaround, host Excel in a regular non-ZIP format (16857).
55. It is not possible to change the format of XMPieRecipientKey when readapting a Campaign for the web (17938).
56. In uProduce Document Editor, when copying a text block from Microsoft Word to a Plain Text Document (TXT), the formatting is not cleaned. As a result, the text in the Email message body appears with Microsoft Word tags.
As a workaround, when creating a Plain Text Document, copy the text, first, from Microsoft Word to Notepad, and then from Notepad to the uProduce Document Editor (18692).
57. Windows 2008: When uninstalling uProduce Server, the following message is shown: "An error occurred while trying to uninstall XMPie uProduce Server. It may have already been uninstalled. Would you like to remove XMPie uProduce Server from the Programs and Features list?". To uninstall uProduce Server, click the Yes button. Uninstallation will continue normally and should be completed successfully (14680).
58. uProduce version 4.6 provides a connection to the MySQL 5.0 database (through the uProduce Dashboard's Data Source drop-down list, which includes a MySQL 5.0 option). This connection is based on the ODBC provider of MySQL 5.0, which has been found to occasionally throw exceptions.
As a workaround, XMPie recommends using different providers. For example, use Cherry City Software® oledb provider. For details, see the following URL: http://cherrycitysoftware.com/ccs/Home/default.aspx
uPlan
59. A Plan that does not define a Data Source, and, instead, provides data through a stored procedure using the EXECUTE command, fails to be validated in uPlan. This happens even though the Plan is valid and will be successful in production or generation of a Proof Set (17389).
60. On Windows Server 2008 and Windows Vista machines, in the Link to Data dialog, clicking Browse... to select an Asset Source using the Browse for Folder dialog allows selecting both folders and ZIP files. Selecting ZIP files causes the Proof Set generation to fail.
To avoid this problem, select only folders as Asset Sources (14636).
Installation
61. uProduce installation fails with the following error message: "Failed on XMPieInstallerHelpersObject.CreateScheduleTask: ERROR: A specified logon session does not exist. It may already have been terminated." (19598). This may happen if the Windows security option is set not to allow storage of credentials or .NET passports for network authentication. To overcome this issue, perform the following steps:
c. Open the Start menu, type secpol.msc in the search line and press Enter. This will open the Local Security Settings Manager.
d. In the Security Settings tree, select Local Policies and then choose Security Options in the right pane.
e. Search for the Network Access: Do not allow storage of credentials or .NET passwords for network authentication option and double-click it. A Properties window will open allowing you to change the configuration.
f. Select Disabled.
g. Close the window, and try installing uProduce again.
62. New versions of Norton Antivirus may mistakenly identify uPlan and Proof Set Viewer as viruses and block these applications. When either finishing the uPlan installation or when trying to run the application, Norton Antivirus may notify you that a "Suspicious.Cloud" threat has been encountered and automatically quarantine the uPlan or Proof Set Viewer application.
Neither uPlan nor Proof Set Viewer are viruses, nor do they contain malicious code. The "Suspicious.Cloud" threat detection is known to falsely identify possible threats from safe applications.
To workaround this issue, you can take uPlan and/or Proof Set Viewer out of quarantine. Other possible workarounds are described in Symantec's web page, detailing issues concerning the "Suspicious.Cloud" threat detection:
http://www.symantec.com/security_response/writeup.jsp?docid=2009-090107-2513-99
63. A conflict occurs when installing the following configuration:
● uStore and uProduce inside the LAN environment.
● RURL Wizard outside the LAN environment, in the DMZ.
● The public IP address of the RURL Wizard server (defined as uProduce External Address in the uProduce "Path Locator") is not accessible from the LAN.
This conflict results in one of the following:
a. If: the uProduce External Address in the Path Locator is configured with the RURL Wizard server's Public IP
Then: uStore will fail to generate proof samples
b. If: the uProduce External Address in the Path Locator is configured with the uProduce internal LAN address
Then:
t PDF On Demand links will be inaccessible.
t An email with Assets, which uses a uProduce local Document (uProduce HTML/TXT Editor or uploaded Document) or a URL Document that points to an ICP page that is configured without a friendly URL, will fail to show the Assets.
t An email Unsubscribe link that uses the "generic Unsubscribe page" as the "Unsubscribe web address" will not function.
To resolve this issue, install uStore version 4.1 or higher, and verify that the uProduce External Path Locator Address is configured with the RURL Wizard server's Public IP.
uCreate XM
64. When you create or edit a Facebook Share button with Adobe Dreamweaver CS6 or uCreateXM, the button is not properly displayed on the RURL page (22968).
65. In uCreate XM it is not possible to have more than a single instance of a QR code snippet on a web page (18660).
66. When modifying a website that was created using the Email Template, and changing the Page Settings, the Document Name containing spaces will show a Parameter name containing invalid characters error.
Workaround:
Remove the spaces from the Document Name (18677).
RURL Wizard
67. The Map RURL template is no longer available.
Workaround:
You can integrate 3rd party mapping services, such as Google Maps, with custom code (22278).
68. When creating a personalized Custom Unsubscribe website using the Email Unsubscribe RURL Template, the Sample Link of this site in the RURL Wizard is not working.
Workaround:
In order to test such site, you need to send an email and click the Unsubscribe link from the received email (18595).
69. It may be impossible to navigate to RURL sites if the Recipient Key contains non-URL conforming characters (23121).
70. The RURL Wizard does not allow creating a website with the name of a deleted port.
Use another name for the website (18663).
71. When a user's uProduce username and/or password are changed, the personalized websites created by this user stop working.
As a workaround, update the site to work with the new user/password by connecting to the RURL Wizard with the new credentials and editing the site:
In the RURL Wizard's Sites page, go to the Actions section and click Edit. When editing the site, the wizard follows the same pages as when creating the site, except that your previous selections are already displayed as default settings. Click Next all the way through and finally click the Finish button (without making any changes).
Alternatively, simply revert to the previous password (16854).
72. RURL Wizard and RURL Websites can only exist on an IIS default website. The RURL Wizard installs the wizard on the IIS default website. All subsequent sites the Wizard creates are also created in the IIS default website (15460).
73. If the domain used to create the site is not registered on an Internet DNS, the last step of the RURL Wizard shows an error instead of a link.
To overcome this problem, purchase the domain and make sure that it is both accessible over the Internet and mapped to the external IP address of the RURL Wizard machine (14543).
74. In GURL Templates, when using Graphic ADOR Objects as placeholders on the GURLSelfRegistration.aspx page, this page returns an error.
To avoid this problem, do not use Graphic ADOR Objects if you intend to use the GURLSelfRegistration.aspx page. Alternatively, edit this page in Dreamweaver and replace the dynamic content with static content (15250).
75. It is possible to create two sites with the same name: one using RURL Wizard and the other using uStore.
As a workaround, recreate the RURL Wizard site using an alternate name (14672).
76. In the RURL Wizard's Settings page, when FTP is selected as the connection method, testing the connection by pressing the Test button sometimes fails, even when the connection is defined correctly.
To correctly test the FTP connection definitions, create a website with the RURL Wizard, and try to use its Site Definition File (STE) with Adobe Dreamweaver (13914).
77. When an email blast job contains recipients with non-unique email addresses, the tracking information for these recipients is not correct.
Workaround:
Make sure that each recipient has a unique email address before you send an email blast job (21824).
78. When you set up a uCreate XM Email page with content type Text, the resulting email body contains unnecessary HTML tags.
Workaround:
Instead of using uCreate XM, create the email body using uProduce HTML and Text Editor (18680).
79. When using XMPie Email Service or Exact Target Delivery provider for sending emails, it is not possible to define a From email address that contains "noreply@" or "no-replay@" (19147).
80. When an email based on an ASPX URL Email Document is viewed in an Internet browser, the ADOR Objects representing the Unsubscribe link and the Sender’s Business Details are not replaced by the real values. The ADOR Object names are displayed instead (19488).
81. Sending an Email Activity to multiple recipients with a constant email address results in tracking events associated with a single recipient.
In order to test emails and email tracking events correctly, send the Email Activity to recipients with a different email address (19918).
82. When sending emails with an Unsubscribe link, make sure that the Unsubscribe link is not an IP address but rather a Domain Name. Otherwise, clients, such as Outlook, might show a phishing warning (18371).
83. The Unsubscribe Email Template cannot be used with Image ADOR Objects. Static images, such as logos and banners, will work (18674.
84. The Email Template does not create an Email Activity for uProduce Accounts that were created prior to PersonalEffect 5.0.
As a workaround, open uProduce Account Settings for editing, and click Save without modifying any field (17772).
Web
85. In a website accessible via the HTTPS protocol, images that are used in the context of a Graphic ADOR and are hosted on a uProduce Asset Source will not appear. uProduce Asset resolving for web pages supports only HTTP protocol.
Workaround:
Instead of using the uProduce Asset resolving mechanism, you may choose to place the images in the website itself, thus, determining the image URL directly from the ADOR Object value (23860).
Social Media
86. It is not possible to track the landing of the recipients' friends on the Shared Page (for example, a Self-registration page). As a result, the response of the recipients' friends from the social media cannot be analyzed.
87. In each web page or email, it is possible to add only a single Share button for each social network (19812).
88. A user clicking the Share button while not being logged into Facebook will be first prompted to log into Facebook. Logging in will open the expected Share page. In some cases, after submitting the login information, a Facebook Error page will be displayed instead of the Share page. This is due to a general problem with the Facebook Share button.
As a workaround, the user can close the Error window and press the Share button again. This time, the Share window will open while the user is already logged into Facebook and the user will be able to complete the share process (20291).
uProduce Marketing Console
89. Customers must refrain from tracking campaigns with non-unique recipient keys. Otherwise, the availability of data for reporting will be considerably delayed, and the respective data will be useless for reporting.
Tracking
90. All events except email and print batch are not tracked
if the Regional Settings of the operating system are set to use comma
as a decimal separator (for example, in German or French locales) (26149).
To resolve this issue, contact XMPie support.