Known Issues and Limitations in Version 6.5
uProduce
1. There is no option to export a Local Data Source that was originally uploaded as FoxPro to FoxPro (24673).
uImage
1. When using uImage, production will fail if uImage horizontal scale is set. It is recommended to set the Optimize attribut to Automatic (24240).
2. uImage DPKG import fails if the file path includes Japanese characters. As a workaround, use Latin characters for file names and paths (24347).
3. When the uImage Server is running on Windows Server 2012, uImage ADOR objects that use an Adobe Illustrator template fail to run. As a workaround, it is possible to install the uImage Processing Unit (UPU) on another operating system (24919).
uCreate Print
1. When using Japanese and Australian postal barcodes, the barcode is not sized by default according to the postal office requirements. It is necessary to adjust the size manually. For example, the Australian barcode needs to be stretched 170% horizontal and squeezed to 38% vertical to meet the requirements (24459).
2. When using the XMPbarcode function, human readable text does not appear in PDF\VT (24460).
3. When a XNIP file is imported to InDesign as inline image or table, the rest of the objects may not be positioned correctly (24487).
4. Production of PDF/VT format file with "Draw Page Information" enabled fails. As a workaround, use PostScript output (24586).
5. 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).
6. When working on a Mac with an ANSI Data Source, accented characters are not display correctly. It is recommended to use a UTF-16 Data Source instead (24812).
Production
1. When using "Merge Output" in production for designs with Graphic elements, production fails (24546).
uCreate XM
1. Facebook Share in email does not work. As a workaround, you can place the Facebook Share button in a RURL site (24921).
Known Issues and Limitations in Previous Versions
General
1. When linking a Document to a Data Source containing a Time column (for example, “11:16:26”), the 31/12/1899 date is erroneously added to the time value (24514).
2. Shift-JIS encoding in a CSV Data Source is not handled correctly (24522).
Workaround:
Use Unicode encoding instead of Shift-JIS.
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).
Print Production
1. 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).
2. Transparency features applied to groups are not maintained in print production.
Workaround:
Assign the transparency features to each element independently (19120).
3. Text Copy Fitting does not work in inline boxes (22036).
4. uCreate Print Standard edition does not support the “Number of copies” feature for PDF. This feature allows you to create multiple copies of each record output. The number of copies can either be the same for all recipients, or vary between them per Content Object.
5. 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).
6. In multiple-instance environments, where the data is stored in an Access (MDB) file, running production may fail. This failure occurs when the file is being accessed more times than the allowed number of connections (~20).
Workaround:
Use an alternative File Data Source type (such as CSV), or host the database on a server database (19172).
7. Unique with Inline optimization might cause production flaws.
As a precaution, this optimization is disabled.
8. 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:
a. %USERPROFILE%\Application Data\Adobe\InDesign\Version 5.0(or other version)\configuration_17001(or other instance)\CompositeFont
b. %USERPROFILE%\Application Data\Adobe\InDesign Server\Version 5.0(or other version)\configuration_17001
(or other instance)\CompositeFont
c. %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.
t In the case of desktop production (uCreate Print) — 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.
t 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.
n The Application Data folder referenced above is usually a hidden folder. To show it, take the following steps:
i. Open the C:\Documents and Settings folder in Windows Explorer.
ii. From the Tools menu, select Folder Options.
iii. Select the View tab, and under the “Hidden files and folders” folder, selected Show hidden files and folders.
iv. 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).
9. 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).
10. On uProduce systems that use InDesign Server CS5, Documents that contain transparency effects (including shadow, blur etc.) sometimes fail to produce Print Output files. This happens only at the early production stages. If you follow up with another production, the new production job does succeed.
If this is the case, the failure might be caused by InDesign CS5 startup issues.
As a workaround, you can use a registry key named InDesignRestartSleep to set uProduce to wait longer for InDesign CS5 to start up properly. This normally resolves all issues. A value of 3 seconds is a good default setting, which does not cause significant production delays (note that this "sleep time" is not applied to all production jobs, only to a very small amount).
To set the InDesignRestartSleep key, proceed as follows:
a. Open the Registry Editor (Start > Run > Regedit).
b. In the Registry Editor window, under My Computer, go to one of the following folders:
t For 32 bit systems:
HKEY_LOCAL_MACHINE>SOFTWARE>XMPie>XMPie uProduce Server Object>1.00.000
t For 64 bit systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\XMPie\XMPie uProduce Server Object\1.00.000
c. If the InDesignRestartSleep property is not listed, configure it now: Right-click the 1.00.000 folder, select New > String Value from the context menu and set the new property's name to InDesignRestartSleep.
d. Set the InDesignRestartSleep property to the desired sleep time in 1/1000 of a second. For example, to set the value to 3 seconds, double click it to display the Edit String window and set Value Data to 3000.
11. The XMPie Bleed feature creates corrupted output when used in combination with uProduce Global Caching feature (17647).
12. uProduce fails to produce uImage Document Packages (DPKGs) that reference a JavaScript file. This is because uProduce mistakenly searches for the JavaScript file in its location during packaging (the designer's machine), instead of its new location on the uProduce Server.
To work around this problem:
a. Manually upload the JavaScript file to the uProduce Server.
b. Edit the Plan file and modify the uImage function call, so that it references the uploaded JavaScript file.
c. Check in the updated Plan file to the uProduce Server (14697).
uImage
1. uImage packaging mechanism does not support text tags that are located in the Smart Objects (24123).
2. 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).
3. When exporting CPKGs from uCreate Print referenced uImage DPKGs will not be included (20608).
4. 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).
5. When creating personalized images from uImage templates that make use of dynamic images, the generated images do not show the dynamic images, even though production completes successfully. The same problem occurs in some XMPie Marketplace "image font" templates, where there is a dynamic image placeholder for each character. In these templates, the personalization (that is., the person's name) does not appear in the image created by uImage.
This problem happens because of a change in uImage behavior in version 4.6. Up to this release, when uImage created a personalized image for a given recipient, any invisible dynamic image layers in which images were placed by uImage, were automatically made visible. As of 4.6, hidden dynamic image layers remain hidden.
Workaround:
• If you are using a Marketplace template, try to download it again from Marketplace. It may have been updated since you last downloaded it. You can download the template again, and get the update for free.
n If you are using your own template, make sure all dynamic image layers (Smart Object layers) are visible in the template. Some of these layers may have content, in which case the content will have to be deleted, otherwise it will appear in all images generated by uImage. To delete the contents of dynamic image layers, follow the steps below to for each dynamic image layer:
i. Open the layer's Smart Object by double clicking the layer's thumbnail in the Layers palette.
ii. Delete all layers except one. Any layer will do.
iii. Select the entire layer (Ctrl+A in Windows, cmd+A in Mac)
iv. Press the delete key to clear the layer.
v. Close the Smart Object (File -> Close). When prompted whether or not to save the file, save it.
After completing the steps above, save the template file, and try to generate the personalized images again (15394).
6. On some 2008 servers, uImage production may fail. The failure occurs when uImage activates the Photoshop registration dialog, which prevents uImage from operating.
As a 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:
t Register — the Photoshop registration dialog will not appear again.
t 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).
7. Copy fitting is not supported for paragraph text (text boxes) in Photoshop. Use point text (text lines) instead (6242, 6260, 13977).
8. uImage does not generate new images that reflect the changes made in its definition.
This occurs in uCreate Print, when the definition of a uImage Content Object is changed in the Rule Editor, Skip Duplicates is checked, images have already been generated for some recipients and Dynamic Print is invoked, or the user browses through recipient records.
This also occurs in uPlan, when the uImage function call is changed, the OPT: parameter is used, images have already been generated for some recipients, and Generate Proof Set is invoked.
To work around this problem and cause uImage to generate new images, proceed as follows:
a. Browse to the uImage Output Folder — in uCreate Print this folder is defined by the Content Object Rule. In uPlan this folder is defined by the ADOR Object definition.
b. Delete all existing uImage Output files.
c. Generate new images — in uCreate Print, run Dynamic Print or browse through recipient records. In uPlan, invoke Generate Proof Set.
(11112, 13982)
uProduce
1. uProduce password may not contain the sequence $$. Otherwise, the RURL wizard will fail to load (23366).
2. To work with FoxPro databses on uProduce, you must install the FoxPro OLEDB driver manually (23905).
3. 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).
4. Exporting a Data Source to Excel from uProduce corrupts Date fields (23498).
5. Accounts may contain no more than 1255 Campaigns (21341).
6. When working in uProduce with a Hosted Data Source that has one or more columns whose name contains a dot (.) character, the dot is replaced with a number (#) character. Later, exporting the Hosted Data Source will fail. The failure will also occur for any Data Source in which the number (#) character originally appears in a column name. To overcome this problem, avoid using either dot (.) or number (#) characters in a column name (19744, 19746).
7. Downloading a personalized PDF fails when clicking a link in an email created in uProduce Email Editor. The PDF is created on the server, but an error message appears to the end user, not allowing to download the file.
As a workaround, create the email in uCreate XM. Email documents created in uCreate XM work correctly with the PDF On Demand feature (20325).
8. The Credit Status window provides information only on Email Credits.
For information about Production Units, login to uProduce as an administrator and select Balance from the Navigation Bar.
9. 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).
10. When tracking a large amount of ADOR Objects (around 70 or more), then after reaching approximately 70000 events the events are no longer registered.
It is recommended to track a lower number of ADOR Objects. Note that in that case restarting the server will cause the unregistered events to be registered, due to the existence of a fallback mechanism (16125).
11. 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.
n Upload a small Campaign (for example, without the Assets, adding them later)
n Create a new Campaign on uProduce and upload the material components separately (16140).
12. When creating a new Data Source by uploading large file databases (more than ~190MB) with the "Host Data Source" option enabled, the upload may fail. The following error message will appear: "RadUpload Ajax callback error".
To resolve this issue, try one of the following solutions:
• Try again. The error may be due to a temporary high load on uProduce.
n Upload the database file without the "Host Data source" option. After having completed the upload, use the "Host" functionality to complete the hosting of the database.
n If possible, try using a smaller database (16853).
13. 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).
14. Creating an Asset Source and adding Assets after a Port has been created does not affect the current RURL, leaving the image un-rendered. Be aware of the following:
a. The image will show correctly for all other recipients RURLs, that were not browsed before adding the ADOR Objects.
b. Even the RURL that causes the problem will work okay on other machines and browsers, who did not use this URL before the Assets have been added.
To view correctly the RURL that causes the problem on the same machine and browser, take the following steps:
a. Add the Assets.
b. Switch one of the characters of an existing recipient from uppercase to lowercase or vice versa (17277).
15. The HTML Editor used to create web pages and emails on uProduce does not show Graphic ADOR Object images when in preview mode.
Note that when the page is actually used, that is: viewed in the browser or accessed from a link in an email, the images appear correctly (17480).
16. It is not possible to change the format of XMPieRecipientKey when readapting a Campaign for the web (17938).
17. When installing uProduce, you may receive the following error during the installation process.
"failed on XMPieInstallerHelpersObject.InstallApplicationComponents
Errors occurred accessing one or more objects - the ErrorInfo collection may have more detail (Exception from
HRESULT: 0x80110401)
Installation will be aborted. Please address this issue and run the installer again."
This issue is normally due to a corrupted version of the installed .NET environment.
To correct this problem, either re-install .NET with the version provided by the IT department, or consult http://www.xmpie.com/docreferences to download and install the .NET version for uProduce. After re-install has been completed, you can try installing uProduce again (18129).
18. When installing uProduce on a server where Microsoft Visual Studio 2005 is installed as well, the installation might fail. The following message will be displayed upon failure:
"Program compatibility Assistant:
Check online to see if solutions are available from the Microsoft website. If solutions are found, Windows will automatically Display a website that lists steps you can take.
Program: Visual studio 2OO5
Publisher: Microsoft."
To resolve this problem:
a. Go to the following link:
b. Download the update for Visual Studio 2005.
c. Run the update.
d. Install uProduce (18489).
19. uProduce processing of HTML or Text Documents for Email Distribution (Proof or Process) does not work for a Document that was created using the Document Editor in the uProduce Dashboard. Once such Document is proofed or processed, the job will be completed successfully, but the output files will not be available.
This problem occurs since the Document Editor creates Documents with UTF-8 encoding, whereas Proof/Process does not support Unicode-based encoding.
As a workaround, HTML/TXT Documents can be uploaded rather than edited from the Dashboard.
For an "upload" document that does not use Unicode-based encoding (UTF-8 or UTF-16), Proof or Process are working correctly (18544).
20. 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).
21. 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).
22. 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
23. When using old HTML Production (XOD), the Document Edit feature does not work. Use upload instead (14156).
24. On Windows Server 2008 machines, a system error occurs when the system is not used for some time, and the following message is displayed:
"Error in '/XMPieDashboard' Application. Missing username\password in soap header."
If this happens, go to the XMPie Dashboard login page (replace <yourServerName> with the name of your server):
http://<yourServerName>/XMPieDashboard
(14702).
25. When installing uProduce on a Windows Server 2008 machine, the message "IIS component is not installed" appears during the installation.
For instructions on configuring the IIS component, see "Chapter 2: Preparing the uProduce Environment" of the uProduce installation Guide (14113).
26. When installing uProduce on a Windows Server 2008 machine, the installation sometimes fails and the following message is displayed:
"Failed on XMPieInstallerHelpersObject.DeleteVirtualDir: Unknown error (0x80005000)"
To correct this problem, your IIS installation should include the IIS 6 Management Compatibility tool. For instructions on configuring the IIS component, see "Chapter 2: Preparing the uProduce Environment" of the uProduce Installation Guide (14119).
27. When running the XMPie Legacy API setup, error messages are displayed. Clicking the error message's OK button continues the installation and it is completed successfully (14829).
uProduce e-Media
1. In Email production, if the URL throws an exception even for a single recipient, the email production job fails.
To make sure this problem does not occur at production time, use the new Email Preflight feature (15381).
2. When the email content is a RURL web page, and it contains a link to another web page on the same RURL site, the link does not always work. Specifically, it fails when the link does not contain the current Recipient's unique identifier (Recipient Key), that is, the value of the Primary Field for the Recipient.
Workaround:
Include the Recipient Key in any link to the RURL site from the email content web page. For example, instead of linking to: linkedPage.aspx link to: linkedPage.aspx?XMPieRecipientKey=<%# /* Text ADOR */ AdorRec.FieldValue("RecipientID", Container)%>. Note that in this example, the Recipient Key ADOR Object is "RecipientID". You should replace it with the Recipient Key ADOR Object in your Campaign (15456).
3. The Email Preflight Delivery Provider does not provide any warnings if the message does not include ExactTarget fields, including those used to unsubscribe and the sender's physical address. Make sure you include these fields, such as %%member_addr%%, in your email message. For more information, see the uProduce Reference Manual (15703).
XLIM
1. 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).
2. The "Repeat Header" and "Repeat Footer" features for tables will always be "Once per Frame" regardless of the user’s choice (23086).
3. When using different widths for lines in a table, the lines would have blanks around the edges (23162).
uCreate Print
1. 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).
2. 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).
3. The Carriage Return ("\r") characters of the Text ADOR Objects are replaced with Newlines ("\n") when the Text ADOR Object values are delivered through a Port. InDesign treats Carriage Returns as paragraph ending marks as opposed to Newlines that are handled as simple line ending, with no paragraph ending. As a result, the text alignment and justification settings for the last line of a paragraph will be ignored.
Workaround:
Use generated Proof Sets instead of directly using the Port (20266).
4. Text that is tagged with a Style ADOR Object is lost when converting the Document's Rules to a Plan and later linking to this Plan.
When a "Text with Style" ADOR Object is used in uCreate Print, and later the Document Rules are converted to a Plan using the "Convert Rules to Plan" feature, two ADOR Objects are created:
• A Text ADOR Object — representing the text value of the "Text with Style" ADOR Object. This ADOR Object is named after the "Text with Style" ADOR Object.
n A Style ADOR Object — with the style value of the "Text with Style" ADOR Object. This ADOR Object is named after the "Text with Style" ADOR Object, with an additional, "corrupted" character ("?").
When viewing the Plan in uPlan, both the Text and the Style ADOR Objects appear (and the Style ADOR Object has the "corrupted" name).
However, when using the Plan in uCreate Print, only the Text ADOR Object is available, while the Style ADOR Object is unavailable.
As a result, the "Text with Style" feature is not usable in the workflow of converting the uCreate Print Rules to a Plan.
For example:
In uCreate Print, a Text with Style ADOR Object is defined with the name
"A Name". Converting the rules to a Plan results in a Text ADOR Object named "A Name", as well as a Style ADOR Object named "A Name?". Apart from the "corrupted" appearance, this Plan is unusable in uCreate Print, as it does not make the Style ADOR Object available.
There are two possible workarounds:
• Avoid using Text with Style ADOR in uCreate Print. Instead use two separate ADORs - one Text ADOR and another Style ADOR.
n If Text with Style ADOR is used, then after converting the rules to a plan rename the Style ADOR in uPlan to a proper name. Now the Style ADOR can be used in uCreate Print.
5. 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).
6. 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 or uProduce, 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).
7. When a bullet has color and "Suppress Trailing Spaces" is activated, the bullet color is determined by the suppressed line, as opposed to its own color setting (14774).
uPlan
1. 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).
2. When an ADOR Object named "XMPieRecipientKey" exists in a Plan file, the Plan cannot be viewed in uPlan and the following message is displayed:
"XMPieRecipientKey is a reserved word. Please choose a different name for this ADOR."
To prevent this issue, avoid using the reserved word "XMPieRecipientKey" as an ADOR Object name.
If you already have a Plan file with an ADOR Object named "XMPieRecipientKey", which cannot be edited as described above, recover it by taking the following steps:
a. Make a backup copy of the damaged Plan file.
b. Open one of the Plan file copies with a text editor (for example, Notepad in Windows).
c. Use the "Search and Replace" functionality to replace all occurrences of "XMPieRecipientKey" with another name, and save the updated Plan file.
d. Edit the updated Plan file in uPlan (10536).
3. 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).
Qlingo
1. The ICP functionality is incompatible with the "skip" function in Qlingo (23502).
uChart
1. 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).
Installation
1. 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:
a. Open the Start menu, type secpol.msc in the search line and press Enter. This will open the Local Security Settings Manager.
b. In the Security Settings tree, select Local Policies and then choose Security Options in the right pane.
c. 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.
d. Select Disabled.
e. Close the window, and try installing uProduce again.
2. 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
3. A conflict occurs when installing the following configuration:
• uStore and uProduce inside the LAN environment.
n RURL Wizard outside the LAN environment, in the DMZ.
n 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
1. On Demand emails that are triggered by the uCreate XM Self-Registration mechanism are not sent out when you use ExactTarget or ExactTarget Enhanced delivery providers (22312).
2. 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).
3. The Facebook Share functionality is not available for IE8 (22971).
4. In uCreate XM it is not possible to have more than a single instance of a QR code snippet on a web page (18660).
5. 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).
6. When editing an Unsubscribe Email site created from the Unsubscribe Email Template, the preview will not work.
To preview the page, perform "test send" on the real email and click Unsubscribe from within the email. Remember to re-subscribe again, or you will no longer receive emails (18684).
7. When double-clicking the QR Code snippet in uCreate XM, the QR Code will not work in runtime (18628).
8. The Response.Redirect function will not work when using Proxy. Instead of using this method, use uCreateXMCtrls.uCreateXMCommonCSharp.XMP_Redirect (15229).
9. Emails that fail to be sent from a uCreate XM website are not reported by uProduce (13870).
10. On Windows, after installing uCreate XM on Adobe CS4, the Email, Tracking and Insert buttons do not respond to clicks.
To fix this problem, go to the Control Panel, double click Add or Remove Programs, select XMPie uCreate XM, click the Change button, select Repair and then click Next (13974).
11. When upgrading uCreate XM after upgrading Adobe Dreamweaver CS3 to CS4, the uCreate XM installation fails.
To fix this issue, take the following steps:
a. Open Adobe Extension Manager CS4.
You are asked whether extensions installed in the previous version
b. Click Yes.
c. Close Adobe Extension Manager.
d. Perform the uCreate XM installation.
RURL Wizard
1. The Map RURL template is no longer available.
Workaround:
You can integrate 3rd party mapping services, such as Google Maps, with custom code (22278).
2. When you use the Email Unsubscribe RURL Template to create a RURL site for a Custom Unsubscribe page, the RURL site’s sample link does not work in the RURL Wizard.
Workaround:
To test the RURL site, you need to send an email that contains the Unsubscribe link and click the link from the received email.
3. 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).
4. It may be impossible to navigate to RURL sites if the Recipient Key contains non-URL conforming characters (23121).
5. When upgrading the RURL Wizard from version 4.6.3 to version 5.0, the URL Domain setting is not saved. After the upgrade, go to the RURL Wizard Settings page and re-enter the value of the URL Domain in the URL Domain field (17606).
6. The RURL Wizard does not allow creating a website with the name of a deleted port.
Use another name for the website (18663).
7. In the URL step of the RURL Wizard, if the URL address is left with the default Friendly value, then the RURL Wizard crashes. Note that the Friendly value must be replaced with the real URL address (18672).
8. After upgrading from PersonalEffect 4.6.3 to PersonalEffect 5.0, the RURL Domain field in the RURL Wizard Settings is reset to None.
The administrator must login to the RURL Wizard and set the RURL Domain field to the value that was previously defined in version 4.6.3 (18005).
9. 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).
10. 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).
11. 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).
12. In the URL page of the RURL Wizard, when configuring a friendly URL, the name of the Virtual Folder cannot begin with a number.
To continue, give the Virtual Folder a name that does not begin with a number (15244).
13. 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).
14. Some RURL Templates throw an exception instead of going to the specified template error page.
To fix this problem, define the required error page for the page using Dreamweaver (15269).
15. 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).
16. On Mac machines, the Site Definition File (STE) created by the RURL Wizard does not work as created. When trying to connect to uProduce, the error message "FTP error 0" is displayed.
To correct this error, edit the STE by going to Site > Manage Sites > Edit, and change all instances of the RURL Wizard's host name with its IP address (13911).
17. 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).
18. On the Web Server machine, the user must manually install Helicon Tech's ISAPI_Rewrite 3.0. For details, see the uProduce Installation Guide (14111).
1. The “Email link tracking” functionality described in uProduce Reference Manual is currently not supported and will be implemented in the future.
2. 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).
3. 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).
4. 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).
5. 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).
6. 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).
7. When clicking the Unsubscribe link from an email, it might take a long time for the Unsubscribe Confirmation page to load. This happens only when the Unsubscribe mechanism is starting its service after not being used for more than 720 minutes (usually it will happen only when the first recipient is trying to unsubscribe from an email blast job or when testing the Email Campaign)(19005).
8. Email Preflight fails for an HTML document that was created using the uProduce Document Editor in PersonalEffect version 4.6.3 or below.
As a workaround, check out the HTML Document and check it in using the Edit option in the Document Editor (20159).
9. 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).
10. The Unsubscribe Email Template cannot be used with Image ADOR Objects. Static images, such as logos and banners, will work (18674).
11. 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
1. 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
1. 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.
2. In each web page or email, it is possible to add only a single Share button for each social network (19812).
3. 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).
Tracking
1. In a cluster configuration, when the SQL Server TCP/IP Port is defined as Static instead of Dynamic, the system encounters critical issues, such as tracking events are not written to the Tracking database.
Workaround:
Use a Dynamic Port or enable the SQL Browser Service (22646).
uProduce Marketing Console
1. 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.