Known Issues and Limitations
This section lists known issues and limitations that have not been resolved yet.
No new known issues have been discovered in this version.
1. Marketing Console does not support SQL Server Windows Authentication.
2. SQL Server Windows Authentication is supported only when using Microsoft SQL Sever version 2012 and above.
3. Excel 95 is not supported as a Data Source format for PersonalEffect. Users wishing to connect to Excel 95 data files, should convert them to Excel 1997-2003 XLS format or to later versions (22656).
4. Rotated PDF images (full rotation by property) are currently not supported (131317).
5. The DotCode barcode is only supported for PS-based formats (VIPP, PPML, VPS, PS and Legacy PDF). It is not supported in PDF or PDF/VT output (the output dots will be squares) (28775).
6. In uCreate Print, it is not possible to use XMPieRURL ADOR object in a barcode (31141).
7. Saving a document using uProduce-uCreate connectivity with a non-English file name, using Mac OS, fails (29400).
Workaround:
Rename the file to English.
8. When accessing a campaign using uProduce connectivity and creating an audience, the audience panel does not display the number of recipients per segment (30312).
9. Custom Qlingo
extensions were not recognized by the system. This happened due to a change
in the mechanism that is loading the extension.
The new mechanism is looking for the following DLL filename: Extentionname_v110_x32_R.dll,
where:
● v110 represents the appropriate Visual Studio runtime version
● x32 is the CPU architecture
● R stands for Release versions (as opposed to Debug).
Workaround:
As a workaround, just rename the Qlingo dll to match this format - for uProduce, use _v110_x32_R (30142).
10. Photoshop CC-2014 must have the latest updates installed in order to run correctly (28373).
11. In some cases, when the trim function in InDesign is in use, and Image Rendering > Allow non-InDesign Rendering (Optimized for performance) is selected, the file size may be larger than when Require InDesign Rendering (Enhanced color management) is selected (28404).
12. 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.
13. 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).
14. XLIM preview does not show images in a Table ADOR Object (25203).
15. 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).
16. InDesign Documents with different page orientation are not supported (27694).
17. 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.
18. 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).
19. 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).
20. 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).
21. 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).
22. 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).
23. 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.
24. uImage DPKG import fails if the file path includes Japanese characters. As a workaround, use Latin characters for file names and paths (24347).
25. uImage packaging mechanism does not support text tags that are located in the Smart Objects (24123).
26. 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).
27. When exporting CPKGs from uCreate Print referenced uImage DPKGs will not be included (20608).
28. 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).
29. 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).
30. Copy fitting is not supported for paragraph text (text boxes) in Photoshop. Use point text (text lines) instead (6242, 6260, 13977).
31. When running production with uChart inside and using very specific fonts, such as Tahoma, in the chart, the fonts are not correctly displayed. This happens only with PS-based production (PS, PDF Legacy, VIPP, PPML) and using Adobe CC-2015. This is an Adobe CC-2015 limitation (31086).
32. When the bar graph in uChart is using numbers greater than 10000, decimal values may get rounded (10,000.01 -> 10,000) (27376).
33. 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).
34. 2G: In uCreate Print, when creating a new table ADOR in a document linked to Circle, the additional data source is not mapped to the data source table.
Workaround: When creating a table ADOR in uCreate Print, a new data source line is created in the Circle Data Source pane > Additional Data Sources section. Manually map the additional data source to the data source table defined in uCreate Print (132718).
35. uCreate Print provides connectivity to Circle for 2G projects. However, you cannot start a project in uCreate Print. You can only connect to an existing project that already has a plan and a data source.
36. In 2G, uCreate Print - Circle connectivity does not support PDF on-demand.
37. When a data source recipient table column names are mapped to the plan's recipient schema, uCreate Print connectivity (1G and 2G) does not work (30060).
38. In 1G, when accessing a campaign using uCreate Print-uProduce connectivity and creating an audience, the XMPie Audiences panel does not show the number of recipients for each audience (30312).
39. In 1G, in uCreate Print - uProduce connectivity, it is not possible to edit a data source that is adapted to web using uCreate Print. Modifications can only be done directly from uProduce (29928).
40. The uCreate Print - 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.
41. When using uCreate Print - uProduce Connectivity, Ports are created to serve as a connecting point between the desktop and the server. These Ports remain permanently (27151).
42. When using uCreate Print - 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.
43. A print-only system cannot use 2G in this version, and would have to use 1G. A cross media project can either be implemented as 1G or as 2G. However, once you selected 1G or 2G, there is no easy way to migrate the project to a different technology.
44. 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.
45. 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).
46. When using InDesign's Small Caps feature, fonts must be installed on the system. Campaign Fonts are not supported by this functionality (25321).
47. 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).
48. Transparency features applied to groups are not maintained in print production.
Workaround:
Assign the transparency features to each element independently (19120).
49. Text Copy Fitting does not work in inline boxes (22036).
50. 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).
51. Unique with Inline optimization might cause production flaws. As a precaution, this optimization is disabled.
52. 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).
53. 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).
54. The XMPie Bleed feature creates corrupted output when used in combination with uProduce Global Caching feature (17647).
55. Various page sizes within a single document are not supported (28218).
56. The ICP functionality is incompatible with the "skip" function in Qlingo (23502).
57. Version 7.1 and Adobe Development Environment are compiled with Microsoft Visual Studio 2012. Custom Qlingo extensions developed on earlier environments (visual studio 2010 or earlier) may need to be recompiled using the same development environment before they can run.
58. In XLIM production, empty paragraphs with bullets are not suppressed (28823).
59. Rich Text Format values are based on the attributes defined in the [Basic Paragraph] style of the InDesign document, hence any attribute that was not set in the RTE (Rich Text Editor) will use the attribute value in the [Basic Paragraph] style (28914).
Workaround:
Change the document [Basic Paragraph] style to the values you want to use as defaults for the RTE.
60. In some cases, PDF assets may appear slightly different between XLIM composition and InDesign composition (29403).
61. In some cases, text composition using XLIM may differ from InDesign text composition. This can occur when specific grammar rules used by InDesign dictate a line break earlier than required (29478, and also bugs 29471, 29472, 29473, 29474, 29475).
62. Specific fonts, most likely imported from MAC, may return a corruption error when installed on Windows. These fonts cannot be used in XLIM. It is recommended that when importing fonts from MAC to uProduce Server, first try to install these fonts on Windows.
63. 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).
64. In some rare cases, XLIM proof fails when the proof has hundreds of images involved (28283).
Workaround:
In the Registry, locate the string value "EnableXLIMProofImageCompression", and set the value to 0
Location:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\XMPie\XMPie uProduce Server Object\1.00.000
65. The uProduce installer does not grant uProduce user permissions to the XMPie database (130071).
66. After upgrading uProduce from 7.2.1 to 8.0 , the Cloud Tracking configuration is not saved. The Circle Agent settings must be reconfigured from the Circle Agent UI (30983).
67. In uProduce > Path Locator, the External IP and Internal IP values must not have spaces (31059).
68. 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).
69. When uploading a CPKG that contains an authenticated Asset Source, the password is not restored (27550).
Workaround:
Enter the password again.
70. 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).
71. 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).
72. Restart is required after you install uProduce. Please do not ignore the onscreen instructions to restart.
73. There is no option to export a Local Data Source that was originally uploaded as FoxPro to FoxPro (24673).
74. uProduce password may not contain the sequence $$. Otherwise, the RURL wizard will fail to load (23366).
75. To work with FoxPro databases on uProduce, you must install the FoxPro OLEDB driver manually (23905).
76. 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).
77. Accounts may contain no more than 1255 Campaigns (21341).
78. 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).
79. 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).
80. 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).
81. It is not possible to change the format of XMPieRecipientKey when readapting a Campaign for the web (17938).
82. 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).
83. 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).
84. 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
85. 2G: The new functionality in which an email delivery provider is restricted to the scope of a uProduce account is still not supported in 2G (132722).
86. 2G: A proof set does not show the job link while it is being generated (132702).
87. 2G: When deleting a website, the friendly URL is deleted and freed and there is no preview. However, the website content remains (132578).
88. 2G: In a master list, when adding a new data source that does not match the plan, the master list does not prompt to map the data source to the plan and adapting the data sources for web fails (132362).
89. In 2G, if multiple data sources are used in the master list, the Recipient Table field might disappear for a few seconds after clicking Save (132257).
90. In 2G, when working in Firefox, after deleting a touchpoint with production information from the Plan tab, the touchpoint is not displayed in the list of touchpoints in the library (31608).
91. In 2G, in print touchpoint production settings, document bleed settings are not extracted from INDD/XLIM document (even for DPKG), and the user needs to fill them in (29684).
92. In 2G, while Circle is sending a job to uProduce and its queue is busy, the Run Center will show an "In progress" button, but with a "Triggered" tooltip instead of a "Waiting" tooltip. The job ID is not shown (29794).
93. In 2G, when creating a document for a touchpoint from uCreate Digital or uCreate Print, Circle is unaware of the action until the project is re-opened or the touchpoint is saved. Therefore, the touchpoint preview link is not shown (30493).
94. In 2G, after deleting a document from the library, the document details remain visible although the document was deleted, which is misleading.
Workaround: Moving to another tab resolves the visual issue (30700).
95. In 2G, there is no way to view, edit, or test a remote data source.
Workaround: Create a new data source instead (30816).
96. In 2G, when using recurrent scheduling, a list containing the next few scheduled runs is not visible in the touchpoint's Production dialog box (as opposed to 1G). The runs are nevertheless executed (30826).
97. In 2G, if using the "force delete" option during the deletion of a project, the friendly URL domain will remain allocated, with no automated way to recover it, and thus the domain can no longer be in use (30961).
98. In 1G, in event filters, sometimes the Event dropdown list is not shown (30969).
99. In 2G, changing the name of the uProduce Account (in uProduce or in Circle by clicking Connect > Edit uProduce Account) while working on a project causes the websites and email to stop working (30966).
100. In 2G, in the Circle library, changing the recipient table selection of a data source does not clear the Sample Recipients list (31008).
101. In the Build tab, Sample Recipients > Recipient Details, the Refresh button does not function: nothing happens while pressing on it and the page is not refreshed. Circle ignores the button clicks.
102. The Run Center does not update the run status while it is open.
Workaround: Reopen it and the status will be refreshed (31064).
103. After clicking Recipient Details, and then editing the Sample Recipients, clicking the Next button closes the wizard before the process completes.
Workaround: Reopen the project (31088).
104. In 2G, when renaming a webpage on a web touchpoint with a friendly URL that is mapped to XMPieRURL, you get an unrelated error message.
Workaround: First, delete the friendly URL and, then, repeat the operation (31115).
105. In 2G, filtered list details cannot be viewed while a project is live.
Workaround: Switch the project to the Draft mode or view the filtered list events in the library (31127).
106. On some computers it takes a long time for the toolbox to display the touchpoints when moving from Build to Plan (31099).
107. It is impossible to save a Sample project as another project (31159).
108. In 2G, on Mac Safari, when it takes a long time to upload a CPKG, only after arround 30 seconds the busy indicator is shown (31163).
109. In 2G, when editing an existing connection, the user must re-enter the password. Proceeding with the default password shown in the password text box causes the system to fail but it will still show that the connection is successful (31219).
110. 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).
111. 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).
112. uCreate XM installer fails on 32bit Windows 7 machines (29325).
113. In DreamWeaver CC-2014, when working in Design mode, Text ADORs are represented with an ASP icon instead of the ADOR name (28274).
114. 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).
115. In uCreate XM it is not possible to have more than a single instance of a QR code snippet on a web page (18660).
116. 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).
117. Upon completing the uCreate Digital installation on Windows, you must restart your computer. In addition, when running uCreate Digital for the first time, Windows will prompt you to allow the execution of the Node.js component. Allow it.
118. In some cases, in uCreate Digital installation on Mac OS, the Test button does not appear in the dialog when clicking Link to Circle Project. This is an indication that some functionality will not be available (132016).
Workaround: To resolve this issue, run manually the following command in the terminal and then restart Dreamweaver:
. ~/.nvm/nvm.sh
Nvm install 4.2.1
Notice the space between "." and "~/".
119. uCreate Digital does not support building websites with SSL. To establish an encrypted link, you will need to tag the HTML elements with XMPL tags in another development environment.
120. On PC, when uCreate Digital is in the "Show Data" mode, clicking on a Link ADOR value causes an error (132223).
121. The XMPie plug-in for implementing cross media in Dreamweaver works on Adobe Dreamweaver CC-2015 only. It does not work with earlier versions of Adobe Dreamweaver.
122. In uCreate Digital, when connecting to a project that has no plan and no data source, connection fails (29225).
123. When prompted for a user name and password, the tab will not move the cursor to the password text box. Mouse point and click are required (29601).
124. Creating managed websites from uCreate Digital sometimes does not work and generates an HTTP Error 500.
Workaround: Create the website from Circle (30186).
125. The Map RURL template is no longer available.
Workaround:
You can integrate 3rd party mapping services, such as Google Maps, with custom code (22278).
126. 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).
127. It may be impossible to navigate to RURL sites if the Recipient Key contains non-URL conforming characters (23121).
128. The RURL Wizard does not allow creating a website with the name of a deleted port.
Use another name for the website (18663).
129. 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).
130. 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).
131. 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).
132. 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).
133. 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).
134. 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).
135. In the online email editor, in Internet Explorer, when switching between HTML Mode and Design Mode, extra <br> tags are added (28124).
136. Email batch production fails, when the plan file contains more than 245 ADOR objects (28265).
137. With ExactTarget Enhanced delivery provider, there is no way to set a Reply To field. It is identical to the From address (29177).
138. In 1G, URL documents that have Text ADOR objects containing the "greater than" character ('>') will not display the text after that character (29182).
139. ExactTarget and ExactTarget Enhanced email providers cannot work if uProduce is behind a proxy (29590).
140. ExactTarget Enhanced email delivery provider is supported
in 2G. The old ExactTarget delivery provider is not supported.
When ExactTarget is selected in the Account Settings,
the default delivery provider in the email touchpoint is not correctly
applied: the system selects the next delivery provider in the list and
not the default delivery provider defined in the Account Settings
dialog (30552).
141. The CAN SPAM email footer must remain in the 1G syntax even in 2G emails (30811).
142. In 2G, the preview of an email with a Table ADOR object does not show the table, just its headers (30856).
143. If moving between the uCreate Digital and the Email Online Editor, problems are expected. For example, the XMPieRURL ADOR will not appear as a link. The recommendation is to stick to using a single email editor for a document (31081).
144. In 2G, if an XMPL email has the XMPL scripts required to preview it as a webpage, its email preview from Circle will not work.
Workaround: Remove the scripts before uploading the email document to the email touchpoint (31094).
145. In 2G, email text documetns created in uCreated Digital do not support Table ADOR objects. XMPL does support tables (31146).
146. In 2G, Style and Visibility ADOR objects are note supported in the online email editor. They are supported in uCreate Digital and in XMPL coding (31151).
147. In 2G, preview of text email document in Circle does not work (31162).
148. The Unsubscribe link found within emails may be broken if a change was made to the uProduce External Address Path Locator.
When you change the external address in the Path Locator, the change does not apply to the Unsubscribe link, resulting in the unsubscribe link showing the old address of the Path Locator, which may no longer be valid.
Workaround:
In order for the Unsubscribe link to use the new and correct external address, open the account for editing in uProduce and then save it. (29169).
149. 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).
150. 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).
151. 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).
152. 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).
153. 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).
154. 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).
155. The Unsubscribe Email Template cannot be used with Image ADOR Objects. Static images, such as logos and banners, will work (18674.
156. 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).
157. In 2G, XMPL websites that work on SSL do not work out-of-the box and require some special and manual work. For assistance, contact XMPie (132721).
158. 2G fault tolerance: XMPL upgrade/repair fails if a website was deleted while the XMPL server was down (132581).
159. 2G fault tolerance: Creating a friendly URL while one of the XMPL servers is down shows success, but will actually fail when the server goes back up (132639).
160. 2G fault tolerance: Creating a website when one of the servers is down fails opening the Web touchpoint (132622).
161. If a 1G port is created using the uProduce Dashboard or the API (and not using the RURL Wizard), it will not validate the friendly URL uniqueness with 2G projects.
162. The RURL ADOR object will not display the RecipientID correctly if it has an apostrophe in it. It will display http://pe8beta.xmpie.net/BetaSite/Tyrone.O???Brien, whereas the correct URL, the one that will work is http://pe8beta.xmpie.net/BetaSite/Tyrone.O%E2%80%99Brien (29173).
163. In 2G, friendly URL does not support the prefix format, e.g., recipient-name.domain.com (30977).
164. In 2G, when a GURL page has both personalized and anonymous content, after registering there is a short flicker of the personalized content, before moving to the target page (e.g., Thank You page). Similarly, when a known user arrives at the GURL, the anonymous content flickers before showing the personalized content (31179).
165. In 2G, a friendly URL can only be composed of lower-case characters (31202).
166. 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).
167. In 2G, a personalized image cannot be used as a link to a personalized PDF On Demand (132264).
168. 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.
169. In each web page or email, it is possible to add only a single Share button for each social network (19812).
170. 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).
171. In version 8.0, uStore products can only be implemented as 1G projects.
172. 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.
173. 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.
174. In PPML produciton, Assets are not copied to Secondary Folder destination (26431)
175. 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:
Install the font on the server(s) as one of the system fonts.
OR
(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).
176. 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:
● Open the Start menu, type secpol.msc in the search line and press Enter. This will open the Local Security Settings Manager.
● In the Security Settings tree, select Local Policies and then choose Security Options in the right pane.
● 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.
● Select Disabled.
● Close the window, and try installing uProduce again.
177. 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
178. 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:
● 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
● If: the uProduce
External Address in the Path Locator is configured with the uProduce internal
LAN address
Then:
§ PDF On Demand links will be inaccessible.
§ 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.
§ 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.
179. 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.
180. In 2G, uninstalling a Circle Agent and then reinstalling it causes the agent to report an error. Reinstall/modify/repair does not resolve the issue. Only a second uninstall and install resolves the issue (30632).
181. When the servers' clocks are not synchronized with the world clock there are connection problems with no indication that they are related to clock synchronization (31045).
182. In 2G, the XMPL Server is installed using a Circle user and a Circle Agent. If the Circle Accounts permitted to the user are not all permitted to the Agent, the Agent will not appear in the installer selection drop box (31183).
183. In 2G, the XMPL Server leaves files after uninstall. However, these files do not prevent reinstall (31220).
184. The 2G cross media XMPL Server cannot be configured as active-active fault-tolerant. While uProduce can be set up to be fault-tolerant, the website component, XMPL Server, is a single point of failure, and, therefore, PURL browsing in a fault situation might fail.
185. The Circle Agent cannot be configured as active-active fault tolerant. While uProduce can be set up to be fault-tolerant, production originated in Circle is not fault tolerant, and, therefore, in fault situation might not reach the uProduce and the execution will fail.
186. In a fault tolerant system, website content needs to be copied manually, and the Circle Agent is not fault tolerant. Only a single agent can be used per system.
187. It is crucial that all the servers, whether on-premises or on the cloud are accurately synchronized with the world clock, or else API calls will not function, leading to strange behavior.
188. SECURL is not supported. The technology does not support personalized websites that require a login.