Desktop Client - General
On upgrading to the current version, Portal properties previously inserted in the following areas may or may not work as expected:
◦ Contact and Event objects: Properties in the Portal tab in table view column sets
◦ Filters: Contact and Event objects
◦ Canned Responses
◦ Mailer Templates
◦ Reports: Column sets and filters
◦ Rules
◦ Print Templates
◦ Relationships
◦ Campaigns: Filters
◦ Campaigns: The Set Property action
Solution
Remove any Portal properties and then view the affected module.
Note
The same issues may also occur in the above areas that are common to Web Client.
When the user tried to view the content of a file (MS Word or Excel) in a custom Document type of tab, instead of being displayed in the Document tab the file was launched in a separate window.
Solution
a. Launch the registry on the Desktop Client computer and create the following DWORD values:
| Path | Name | Value |
|---|---|---|
| HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Word.Document.12 | BrowserFlags | 80000024 |
| HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Excel.Sheet.12 | BrowserFlags | 80000A00 |
b. Close the registry.
c. Refresh Desktop Client or log on again.
Users encountered an error in a Web tab and content was not displayed because the tab used Internet Explorer 7 to render pages.
Solution
a. On the Desktop Client computer, navigate to the following registry key location:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION
b. Create a new key (Talisma.exe) of type Dword and retain its default value of 0.
c. Log on afresh to Desktop Client.
When I try to uninstall Desktop Client from the Start menu or Control panel, the following error message is displayed:
The Talisma Client can be installed only on a computer whose operating system in windows7, windows8 and Windows 2008, Windows 2008R2, Windows 2012 Server or later.
Exiting Setup.
Solution
Run Desktop Client setup again and select the Remove option.
The associated KB Solution was not displayed in the KB Solution Manager even though KB solutions with matching subjects were available. This occurred in a scenario where the Automatically use Interaction Subject for KB Search option was selected in Business Administrator and Internet Explorer 11 was installed on the Desktop Client computer
Note
This issue occurred only once in a Desktop Client login session when I first tried to insert a matching KB solution.
Solution
Close the KB Solution Manager and view it again. KB solutions that match the subject of the Interaction are displayed.
6. Problem
If the Export Records action of a Campaign fails to export data, the status of Targets is displayed as Export Failed in the View Targets window of Desktop Client. You can view the error details by running the following query in Microsoft SQL Management Studio:
Select * from tblcampaignexporterrorlog where nCampaignID= <campaignid> and tStepName = ‘<stepname>’
Look for the error details in the tErrorMsg column.
Solution
Fix the error and export the Targets again. To export the Targets, you must first set the status of the targets to Marked for Export by running the following query:
Update tblCampaignTarget set nIntStatus = 11 where nIntStatus = 12 and nCampaignID = <campaigned> and nCurrentElementID = <stepid>
If you are unable to fix the error, contact Product Support.
Note
If the following message is displayed in the tErrorMsg column, perform the steps indicated in scenarios 1 or 2 to ensure that the error no longer occurs:
Error occurred in xp_cmdshell->tlschexport.exe while exporting records for campaign-<campaignname>, step-<stepname>
◦ Scenario 1: The tlschexport.exe is not available in the path <Drive name>\Program file (x86)\Common Files\Talisma Shared\tlMain\.
Solution: Obtain the file tlschexport.exe from Product Support and copy it to the path <Drive name>\Program file (x86)\Common Files\Talisma Shared\tlMain\.
◦ Scenario 2: The available Talisma Shared folder in the path <Drive name>\Program file (x86)\Common Files\ is renamed and Desktop Client is then upgraded. A new Talisma Shared folder is created. As a result, this causes a new value to be generated for the Command prompt short file name for the new Talisma Shared folder, while the old value, Talism~1, continues to be referenced for the old Talisma Shared folder even though the folder is renamed.
Solution: Move both Talisma Shared folders to a different folder and then copy only the new Talisma Shared folder to the path <Drive name>\Program file (x86)\Common Files\.
7. Problem
In Desktop Client, symbols like ™ (Trademark symbol) are not displayed correctly if UTF-8 encoding is used in the HTML Mailer content.
Solution
In HTML mailer content, use ISO-8859-1 encoding instead of UTF-8.
8. Problem
In a Citrix environment, when a user tries to add a subject to a mailer template, the content is not displayed.
Solution
Click Save or refresh the window to view the content in the subject.
9. Problem
When I try to merge two Object items that contain more than 1365 Properties, the operation fails and the following error message is displayed:
There has been an unknown database error. Contact your System Administrator.
Cause
A query that has to retrieve data of more than 4096 columns fails. As three columns are created for every Property, 1365 Properties will require SQL to retrieve data containing 4095 columns. As a result, the operation fails.
Solution
As the maximum number of Properties for an Object is 1365, it is recommended to have only the required number of properties for an object, as this improves performance. As a best practice, it is recommended to delete unused properties, this ensures that the number of Properties does not exceed the maximum limit.
10. Problem
Scenario
A User-defined workspace is created for the Interaction Object where one pane is configured to display the Interaction Table View and another pane is configured to display the Reply pane of an Interaction.
In this scenario, when a Desktop Client user clicks an Interaction in the Interaction Table View, the content displayed in the Reply pane flickers.
Solution
In the pane where the Interaction Table View is displayed, select an Interaction and then double click. The Reply pane will be displayed correctly.
11. Problem
In Business Administrator, default values are configured for Reference Objects for a Team.
When a Desktop Client User creates a new lead, default values are automatically populated for the reference object fields for the team.
In this scenario, when the User saves the Lead, occasionally, the default values of the Reference Objects that were automatically set for the Lead become blank.
Cause
The Lead is created and saved without logging off and logging on to Desktop Client after a Reference Object item that is configured as a default value for a Team is deleted.
Solution
After deleting a Reference Object item that is configured as a default value for a Team perform the following steps:
a. In Business Administrator, configure a different Reference Object item as the default value for the Team.
b. The user must log off and log on to Desktop Client and create a Lead.
12. Problem
When Lead is imported using an Import Configuration with Name, Email, Team, and Campus in the source file, the import operation fails and the Lead information is not imported.
Cause
An entry for the viewImp_106_5010043 View exists in the tblimptlproperties table but the viewImp_106_5010043 View does not exist in Main database.
Solution
To import the Lead information, perform the following steps:
a. In Main database, delete the entry of the viewImp_106_5010043 View from the tblimptlproperties table using the following SQL statements:
Delete from tblImpTlProperties where sEnumViewName like 'viewImp_106_5010043'
b. In the Data Management Utility, modify the existing import configuration for the Lead Object and map the columns of the interface table with the Lead properties.
c. Run the Import Configuration.
13. Problem
When an SMS-based Campaign with an action to create Events when recipients respond to the mailer is processed, Events are not created when the recipients of the Campaign respond to the mailer.
Solution
On the computer where Main database is installed, run the following SQL query in Microsoft SQL Server Management Studio:
select * from tblCampaignEventTypeLang
--insert into tblCampaignEventTypeLang values(1001,0,'No response to SMS')
--insert into tblCampaignEventTypeLang values(1000,0,'On response to SMS')
14. Problem
The Enable Activity Creation for the Interaction Object Global Option is enabled in Business Administrator and the characters typed in an SMS message for Contact(s) or Lead(s) exceeds 200. In this scenario, two incorrect error messages are displayed when a Desktop Client user sends the SMS messages. Although the error messages are displayed, the SMS messages are sent to the recipients successfully.
Solution
It is recommended that you do not exceed 200 characters in a single SMS message.
15. Problem
Scenario 1
Web Components and Application Server are installed on a 64-bit computer. When the user double-clicks the Business Administrator option and clicks Apply in the Talisma Business Administrator - Trace Options window, traces are not generated and the following error message is displayed:
Unable to communicate the changes to the running process. File not found: TLCmnLibU.dll
Scenario 2
Desktop Client, Web Components and Application Server are installed on a 64-bit computer. When the user double-clicks the Business Administrator option and clicks Apply in the Talisma Business Administrator - Trace Options window, traces are not generated. Further, the following error message is displayed:
Unable to communicate the changes to the running process. File not found: TLCmnLibU.dll
Solution to Scenario 1
a. From the Control Panel, double-click the System icon.
b. In the System Properties dialog box, select the Advanced tab, and click Environment Variables.
c. In the System variables area of the Environment Variables dialog box, select the Path variable and click Edit.
The Edit System Variable dialog box is displayed.
d. Add the following path in the Variable value field:
<Drive name>:\Program Files (x86)\Common Files\Talisma Shared
e. Click OK thrice.
Solution to Scenario 2
Perform step b of Scenario 1.
16. Problem
E-mail messages that include large attachments are not extracted into the system through the HTTP channel.
Solution
Perform the following steps on the Application Server computer:
a. On the Application Server computer, navigate to the <system drive>:\TalismaApplicationServer\Backup path.
b. Open the web.config file, and navigate to the following section of code:
<httpRuntime executionTimeout="900" maxRequestLength="5248" useFullyQualifiedRedirectUrl="false" minFreeThreads="8"
c. Change the value of maxRequestLength from 5248 to an appropriate value.
d. Save and close the web.config file.
17. Problem
Desktop Client fails to respond when the User updates an Interaction by:
a. Inserting a Signature in the Insert Signature dialog box.
b. Performing an operation in the Canned Response Manager using the Insert menu in the Interaction window.
Solution
Install Visual C++ 2012 Redistributable Package, version 11.0.60610, on the computer on which you want to work with Desktop Client.
On a Windows 2008 R2 or Windows 7 computer
To verify if you have the correct version of Visual C++ 2012 Redistributable Package, check whether the 8.0.50727.762.manifest file is available in the <System drive>:\Windows\winsxs path on the Desktop Client computer.
If a higher version of the file is available, the xxx text in the 8.0.50727.xxx.manifest file will exceed the value 762.
In a scenario where a higher version of the file is available, perform the following steps:
a. On the Desktop Client computer, navigate to the <System drive>:\Windows\winsxs path.
b. Open the policy file using a text editor.
c. Navigate to the following section of code:
<bindingRedirect oldVersion="8.0.41204.256-8.0.50608.0" newVersion="xxxxxxxxxx"/>
<bindingRedirect oldVersion="8.0.50727.42-8.0.50727.762" newVersion=" xxxxxxxxxx"/>
<bindingRedirect oldVersion="8.0.50727.1833" newVersion=" xxxxxxxxxx"/>
where XXXXXXXXXXXXXXX is the higher version.
d. Change the value of the text after new version to 8.0.50727.762.
e. Save and close the file.
You must also add the <System drive>:\Windows\winsxs path to the Environment Variables path on the Desktop Client computer. To do so, perform the following steps:
a. Right-click the My Computer icon on the Desktop Client computer.
b. Select Properties from the shortcut menu. The System Properties window is displayed.
c. In the Advanced tab, click Environment Variables. The Environment Variables window is displayed.
d. In the System Variables area, select the Path variable, and click Edit. The Edit System Variable dialog box is displayed.
e. Position your cursor at the beginning of the text in the Variable value field. Type <System drive>:\Windows\winsxs, and click through OK thrice.
f. Restart the Desktop Client computer.
18. Problem
In the Canned Response Manager, when the Desktop Client User clicks New to create a new Canned Response, Desktop Client fails to respond.
AND
Campaign Dispatcher fails to respond when the Desktop Client User tries to create a Canned Response or Mailer.
Solution
Install Visual C++ 2012 Redistributable Package, version 11.0.60610, on the computer on which you want to work with Desktop Client.
19. Problem
On a Windows 7 or a Windows 8 computer, when I use the scroll wheel in the Properties tab in the Object window, the display of content is distorted.
Solution
Use the scroll bar on the screen to scroll through content
- OR -
Refresh the window.
20. Problem
I am unable to log on to Desktop Client, and the following error message is displayed:
Unable to Connect to Talisma Application Server
Solution
On the Application Server computer, add the details of the User to the Distributed COM Users group. To do so, carry out the following steps on the Application Server computer:
a. Navigate to Administrative Tools and click Computer Management. The Computer Management window is displayed.
b. In the left pane, navigate to System Tools, Local Users and Groups, Groups.
c. In the right pane, right-click the Distributed COM Users group, and select Add to Group from the shortcut menu. The Distributed COM Users Properties dialog box is displayed.
d. Click Add. The Select Users, Computers, or Groups dialog box is displayed.
e. In the Enter the object names to select area, specify the names of the CampusNexus CRM Users that you want to add to the Distributed COM Users group. Use a semicolon (;) to separate the names of multiple Users.
f. Click Check Names. The users are added to the group.
g. Click through OK twice.
Note
After carrying out the above steps, if you are still unable to log on to Desktop Client, on the Desktop Client computer, open the Hosts.lm file available in the <system drive>:\WINDOWS\system32\drivers\etc path. In this file, specify the IP address, and name details of the Desktop Client computer, and save the file.
You will now be able to log on to Desktop Client.
21. Problem
Desktop Client fails to respond when I view the details of archived Interactions, and custom Object items.
Cause
Archive database was uninstalled and re-installed.
Solution
After you attach Archive database to Main database, wait for the Talisma-Archive-New Job to run before you view details of archived Interactions, and custom Object items in Desktop Client.
22. Problem
Blank Interactions are created if multiple threader jobs are running at the same time.
Solution
You must manually delete the blank Interactions. Ensure that only one Threader Job is running at any given point in time.
23. Problem
On a computer where Windows 7 or Windows 2008 R2 is installed, the following error message displayed when a User tries to log on to Desktop Client:
Unable to connect to Talisma Application Server. Remote calls are not allowed for this process.
Also the following event is logged in the Event log:
Remote calls are not allowed for this process. Contact your Talisma System Administrator.
Solution
Enable network DTC access on the computer where Desktop Client is installed. For more information about enabling network DTC access on a Windows 2008 R2 and Windows 7 computer, see http://technet.microsoft.com/en-us/library/cc753510(v=ws.10).aspx.
If the problem persists, contact Product Support.
24. Problem
Application Server and Main Database are installed on a Windows 2008 R2 or Windows 2012 computer. When I attempt to log on to Desktop Client with the Connection Type specified as LAN, the following error message is displayed:
“Server details may be incorrect.”
Solution
Remote Launch and Remote Activation permissions need to be enabled for all users. By default, these permissions are enabled for the Distributed COM Users group. You need to add Users to the Distributed COM Users group so that the permissions are enabled for all users.
To verify whether the Remote Launch, and Remote Activation Permissions have been enabled for the Distributed COM Users group, carry out the following steps computer(s) where Main database and Application Server are installed:
a. From the Control Panel, navigate to Administrative Tools, Component Services. The Component Services Window is displayed.
b. Browse to the following path: Console Root/Component Services/Computers.
c. Right-click the My Computer node, and select Properties. The My Computer Properties Dialog box is displayed.
d. Click the COM Security tab.
e. In the Launch and Activation Permissions area, click Edit Limits.
The Launch Permissions dialog box is displayed.
f. Select the Distributed COM Users group. In the Permissions for Distributed Com Users area, the Remote Launch, and Remote Activation permissions will be enabled:
To add Users to the Distributed COM Users group, carry out the following steps on computer(s) where Main database and Application Server are installed:
a. From the Control Panel, navigate to Administrative Tools, Computer Management, System Tools, Local Users and Groups, Groups
b. Right-click the Distributed COM Users group, and select Add to Group from the shortcut menu. The Distributed COM Users Properties dialog box is displayed.
c. Click the Add button. The Select Users, Computers, or Groups dialog box is displayed.
d. In the Enter the object names to select area, specify the names of the users that you want to add to the Distributed COM Users group. Use a semicolon (;) to separate the names of multiple Users.
e. Click Check Names. The users are added to the group.
f. Click through OK twice.
25. Problem
"WMS Idle: Talisma.exe - Unable To Locate Component. This application has failed to start because OUTEX.DLL was not found. Re-installing the application may fix this problem."
Cause
The Outex.dll file is missing, or is corrupted.
Solution
Perform the following steps to prevent this error:
◦ Check whether Outex.dll is available in the C:\Program Files\Common Files\System\MSMAPI\1033 folder.
If Outex.dll does not exist, skip to To create or repair the Outex.dll file.
If Outex.dll exists, carry out the following steps to add the System Variables:
a. Right-click My Computer, and select Properties from the shortcut menu.
The System Properties dialog box is displayed.
b. Click the Advanced tab, and click Environment Variables.
The Environment Variables dialog box is displayed.
c. In the System Variables area, select a Variable path, click Edit.
The Edit System Variable dialog box is displayed.
d. In the Variable Value field, add the following text to the end of the Path value:
C:\Program Files\Common Files\System\MSMAPI\1033
e. Click OK thrice.
f. Restart the computer and check whether the problem recurs again.
If the problem recurs, the Outex.dll file may be damaged. Continue with the following steps.
To create or repair the Outex.dll file
a. Go to the folder C:\Program Files\CommonFiles\System\MSMAPI\1033
b. If Outex.dll exists in this folder, rename the file as Outexold.dll.
c. Start MS Outlook, and from the Help menu, select Detect and Repair to repair MS Outlook.
MS Outlook will copy a clean version of the Outex.dll file to the relevant folder on your computer.
d. Check whether the problem recurs.
26. Problem
When I add a row in a RecordList tab of an Object window, and click the Compute Button, or try to save the Object item, the new row is not saved.
In any Object window, when I add new rows in a RecordList tab that contains only Computed Properties, click the Compute button and save the Object item, all the new rows are lost.
Cause
The Record List tab in which you want to add rows, comprises only Computed Properties.
Solution
Create at least one Property which is not a Computed Property, in the RecordList tab.
27. Problem
I am unable to open Online Help from a Terminal Services Client.
Solution
This workaround is specific to Desktop Clients running on WinMedia. Carry out these steps on the Terminal Server computer:
a. From the Start menu, select Programs, Administrative Tools, Terminal Services Configuration. The Terminal Services Configuration window is displayed.
b. Select the Connections node. All connection details are listed in the Results pane.
c. Right-click the RDP-tcp connection and select Properties from the shortcut menu. The RDP-tcp Properties dialog box is displayed.
d. Click the Environment tab.
e. In the Start In field, specify the path where you have installed Desktop Client.
f. Click OK.
28. Problem
When I perform a spelling check for text written in Dutch, I get incorrect results.
Cause
This is due to an extra space introduced between dictionary files in the registry during Desktop Client setup.
Solution
Remove the space between the dictionary files in the Registry. To do so:
a. From the Start menu, select Run. The Run dialog box is displayed.
b. In the Open field, type Regedit. The Registry Editor is displayed.
c. Locate the following path: HKEY_CURRENT_USER\Software\Talisma\Talisma Client\CurrentVersion\SpellCheck\Dutch.
d. Double-click MainLexFiles.
e. In the Value data field, the value sscedu.tlx, sscedu2.clx is displayed.
f. Remove the space after the comma (,).
g. Click OK.
h. Restart Desktop Client.
When I try to log on to Desktop Client, the following error message is displayed:
"Unable to connect using the specified server details. Specify valid server details and ensure that the servers are running."
Cause
The Proxy Client is configured with an incorrect ISA Server.
Solution
Change the setting of the Proxy Client to configure it with the correct ISA Server.
When I try to log on to Desktop Client or Business Administrator, depending on whether I am using DCOM or HTTP, one of the following error messages is displayed:
If I am using DCOM: "Unable to connect to the application server. Please try again."
If I am using HTTP: "Invalid pointer."
Cause
By default, Application Server is configured to run using an interactive account, which is for the User who is currently logged on. This problem occurs when no User is logged on to Application Server.
Solution
Configure Application Server to run under an Account that has been granted administrative privileges. To do so:
a. From the Start menu of the Application Server computer, select Settings, Control Panel. The Control Panel is displayed.
b. Double-click the Administrative Tools icon. The Administrative Tools window is displayed.
c. Double-click the shortcut for Component Services. The Component Services window is displayed.
d. Expand the following nodes: Component Services, Computers, My Computer, COM+ Applications. All COM+ applications are listed.
e. Right-click the Application Server component, and select Properties from the shortcut menu. The COM+ Talisma Application Server Properties dialog box is displayed.
f. Select the Identity tab.
g. In the Account area, select the This user option, and click Browse to locate a User who has administrative privileges on the Application Server computer.
h. Specify a password for the User in the Password field.
i. Type the password again in the Confirm Password field.
j. Click OK. Application Server is now configured to run using a local administrator account.
When I log on to Desktop Client, the following error message is displayed:
"Log in to the chat database failed. You will not be able to use chat."
OR
If any additional databases are installed after the server installation, users encounter errors when they log on to Desktop Client.
Cause
One or more databases have been added and Application Server has not been restarted after the addition.
Solution
Restart Application Server, and log on to Desktop Client. To restart the Application Server component in the Component Services, do so:
a. From the Start menu, select Programs, Administrative Tools, Component Services.
The Component Services window is displayed.
b. Browse to the following path:
Console Root/Component Services/Computers/My Computer/COM+ Applications
c. Right-click the TalismaApplicationServer component and select Shut down from the shortcut menu.
d. Right-click the TalismaApplicationServer component and select Start from the shortcut menu
32. Problem
I am unable to view a complete list of Contacts in the Address Book dialog box.
Cause
Pagination is not supported in the Address Book dialog box.
Solution
In the Address Book dialog box, from the Tools menu, select Find. The Find dialog box is displayed. You can search for Contacts by defining conditions. The Contacts that match your search criteria are listed in the Address Book dialog box.
33. Problem
I am unable to uninstall Desktop Client.
Cause
Disk space is insufficient to start InstallShield for the removal of Desktop Client.
Solution
Free some disk space before removing Desktop Client.
34. Problem
When I try to log on to Desktop Client, the following error message is displayed
“Unable to connect using the specified server details. Specify valid server details and ensure that the servers are running."
Cause
Invalid server details have been provided in the profile that is used, or the user does not belong to the domain in which the database server is installed.
Solution
Follow these steps:
a. From the Start menu, select Run.
b. Type DCOMCNFG in the Open field.
c. Click OK.
The Distributed COM Configuration Properties dialog box is displayed.
d. Click Properties.
e. Click the Security tab.
f. Select the Use custom access permissions option, and click Edit.
The Registry Value Permissions dialog box is displayed.
g. Click Add.
The Add Users and Groups dialog box is displayed.
h. Select Everyone from the Names list.
i. Click Add.
j. Click through OK twice.
k. Select the Use custom launch permissions option, and click Edit.
The Registry Value Permissions dialog box is displayed.
l. Click Add.
The Add Users and Groups dialog box is displayed.
m. Select Everyone from the Names list.
n. Click Add.
o. Click through OK thrice.
The Client logon fails on Microsoft® Windows 2008 R2 for a User with roaming profile.
Cause
This problem occurs if the Microsoft® Windows 2008 R2 computer is unable to access the roaming profile. This in turn occurs if you do not have Permission to access the roaming profile.
Solution
The system administrator must grant you permission on the following folder:
<SystemDrive>\ProgramData\Microsoft\Crypto\RSA\MachineKeys
When I log on to Desktop Client, the following error message is displayed:
“Decryption has failed because you do not have sufficient Permissions. For more information, see the Troubleshooting Guide or Release Notes. Talisma is unable to access the Microsoft® Windows 2000 server's key container. Talisma’s first attempt to open an existing container fails. Talisma tries to create a key container with the same name, which is rejected with NTE_EXISTS (0x8009000f)”
Cause
Permissions on one of the key containers are corrupt.
Solution
Reset permissions on these key containers. To do so:
a. Open Microsoft® Windows Explorer on a Windows 2008 R2 computer.
b. Locate the following folder:
<SystemDrive>\ProgramData\Microsoft\Crypto\RSA\MachineKeys.
There are several files in this folder. Each file corresponds to a key container.
c. Open each file using Notepad.
If you receive an “Access Denied” error message when you try to open a file, open the properties of the file, and take ownership of it. Reassign Full access to the Administrator account. Repeat this procedure for each file in this folder. You should then be able to log on to Desktop Client.
37. Problem
Desktop Client displays the following message:
“The system is running on low virtual memory.”
Cause
This could happen due to any of the following reasons:
◦ Cause 1: The Limit client page size for Filters to option has been set to a value that cannot be supported by the existing RAM size on your computer.
◦ Cause 2: Either too many applications or several Desktop Client windows are open.
Solution
Choose the appropriate solution:
◦ Solution for Cause 1: From the Tools menu, select Options to open the Options dialog box. Set the value of the Limit client page size for Filters to field to 200.
◦ Solution for Cause 2: Close other applications or Desktop Client windows that are currently not being used.
Some characters in messages sent from Desktop Client appear garbled when I view them in a browser.
Solution
Set UTF-8 encoding in the browser preferences to view the messages correctly.
The icon for Desktop Client appears distorted.
Cause
This could happen due to any of the following reasons:
◦ Cause 1: The Show icons using all possible colors option in the desktop properties dialog is not selected.
◦ Cause 2: Desktop Client is running on a Terminal Server, and the color resolution of the computer is not set to 16 bit.
Solution
Choose the appropriate solution:
◦ Solution 1: Select the Show icons using all possible colors option in the Desktop Properties dialog box.
◦ Solution 2: Set the color resolution of the computer to 16 bit.
40. Problem
An error message is displayed indicating that the server is busy.
Cause
This problem occurs if a message box is displayed in an external application running on the computer, such as Microsoft® Excel or Microsoft® Outlook, while you are working on Desktop Client. This message is first displayed when you do not respond to the message in the external application in 25 seconds.
Solution
Open the external application and close the message box.
41. Problem
I am not able to edit the Properties tab in the Object window.
Solution
Ensure that the Properties tab is always the first tab in an Object window, and that the Business Administrator User does not change the position of the tab from Business Administrator.
42. Problem
When I try to create or modify an Object, the following message is displayed:
“You do not have access to some of the Mandatory Properties. You can not update the item.”
Cause
You have created a Mandatory Property in a tab that is shared only to Teams where you do not have access. As a result, you will neither be able to edit the Properties of an Object, nor create the Object. Alternatively, in the case of Interactions only the values you defined for the Properties will not be saved, although the Interaction is created.
Solution
The administrator must share Tabs with Mandatory Properties with all Teams from Business Administrator.
Occasionally, when I am working with Desktop Client, I encounter error messages without any description.
OR
There are neither incoming nor outgoing e-mail messages in Desktop Client.
Cause
This problem occurs if the system path variable exceeded 1024 characters during Desktop Client setup and Setup was unable to add the path.
Solution
Clean the system path by removing unnecessary folders from the computer where Desktop Client is running. To do so:
a. From the Control Panel, double-click the System icon.
b. In the System Properties dialog box, select the Advanced tab, and click Environment Variables.
c. In the System Variables area of the Environment Variables dialog box, locate the PATH variable and click Edit to modify the contents.
d. To the system path variable on the computer where the problem occurred, add the path to the Talisma Shared folder. The default path to the Talisma Shared folder is: <System Drive>\program files\common files\talisma shared. If you have not changed this path at the time of installation, you can add the default path to the system path variable.
44. Problem
Though I have not done the previous installation, I upgrade Desktop Client from an earlier version on a computer running Windows Terminal Server. When I try to log on to Main server, an error message is displayed, indicating a version mismatch because some files have not been copied. However, the Client logon goes through.
Cause
The TalismaClient3.ini or TalismaClient3.ini files have not been copied.
Solution
Copy the TalismaClient3.ini OR TalismaClient3.ini file to your Windows folder and then reinstall Desktop Client.
45. Problem
When I select the AutoCorrect tab in the AutoText dialog box, the following message is displayed:
“Unable to find or create the file '\\MONDEO\TLCommon1\argusmain\SpellCheck\540\amAC.tlx'.”
I am able to create AutoCorrect entries after clicking OK. However, when saving the AutoCorrect entry, the following message is displayed:
“Unable to save information to '\\TALISMA31\TLCommon1\Genesis021018\SpellCheck\9\amAC.tlx'.”
Cause
You do not have the Modify permission in the root drive where CampusNexus CRM is installed.
Solution
Prior to creating an AutoCorrect entry, ensure that you are granted the Modify permission in the root drive.
46. Problem
Desktop Client does not save the modifications in a linked document that was opened from an Object window (Account, Contact, Opportunity, Order).
Cause
Another User has opened the same document and saved it while the you were still editing the document.
Solution
Ensure that no other User is editing the document. Modify the linked document and save it again.
When I send a merged field as part of a URL in a Canned Response, AutoAcknowledgement, or AutoResponse, for example, http://support.talisma.com/intid=<insertint ID property> and the Contact clicks the URL, the browser displays the “Page not found” error.
Cause
The inserted Property is not part of the URL.
Solution
To insert a merged field into a URL like this:
http://www.talisma.com/default.as?interactionID=002-232
where 002-232 is a merged field, do the following:
a. Type the URL: http://www.talisma.com/default.as?interactionID=x
b. Place the cursor before ‘x’: http://www.talisma.com/default.as?interactionID= Ix
c. Insert the field Interaction ID: http://www.talisma.com/default.as?interactionID= <<Interaction ID>>x
d. Delete ‘x’ if it is still displayed: http://www.talisma.com/default.as?interactionID=
<<Interaction ID>>
48. Problem
I am unable to export a large number of items.
Cause
The number of items exported is determined by the page size defined for the Table View.
Solution
Increase the page size and then export data.
49. Problem
When I attempt to log on to Desktop Client as a trusted user, the following error message is displayed:
"Unspecified error" or "Cannot generate SSPI context" or "Unknown Error"
Solution
Open C:\WINNT\system32\drivers\etc\hosts in Notepad. Follow these steps to add a host entry at the end of the hosts file:
a. Type < IP Address of Main Server >
b. Press <TAB>
c. Type < Talisma Server Name >
For example - 172.17.48.93 apollo
For more information, refer to Microsoft Knowledge Base Article - 811889
http://support.microsoft.com/default.aspx?scid=kb;en-us;811889