Exporting Data
If the scheduled Export job runs continuously for long time or when an SQL job for a scheduled Export configuration is run, the exported information is saved as a .csv file instead of .xlsx.
Solution
DCOM Permissions must be enabled on the following computers:
◦ Main Server computer
◦ Destination computer in the network where the Microsoft Excel file will be created.
Perform the following steps on the above computers:
1. In Windows Task Manager, if Excel.exe is displayed in the list of processes, right-click the process and select End Process.
2. In the Services window, stop the services that automate Microsoft Excel.
3. In the Component Services window:
a. Navigate to Console Root > Component Services > Computers > My Computer > DCOM Config. The component list will be displayed in the right pane.
b. Right-click Microsoft Excel Application and select Properties. The Microsoft Excel Application Properties window will be displayed.
c. In the Identity tab, ensure that The interactive user is selected.
d. Click OK.
4. In the Services window, restart the services that were stopped in step 2.
On the main server computer, navigate to the following paths and verify that the Desktop folder is available with all permissions granted to the Everyone user:
• <System drive>:\Windows\SysWOW64\config\systemprofile\Desktop.
• <System drive>:\Windows\System32\config\systemprofile\Desktop.
If the folder is not available, create the folder and then grant the permissions.
When object records were exported to MS Excel, information not displayed correctly in columns if the source data was prefixed with mathematical symbols such as + or -.
Solution
If the symbols + or - are used in the object's source data, ensure that they are configured in the tblglobalInfo table.
For example, to add the + character, run the following SQL statement on Main database:
Declare @SplChar nvarchar(512)
Set @SplChar='+'
update tblGlobalInfo set tValueData =tValueData + @SplChar where tValueName like 'SpecialCharacterSet'
When the user upgraded to the current version, scheduled export configurations created in previous versions failed to run.
Cause
For the export job to execute the operation, the tilde character (~) that is no longer supported was specified as a shortcut to the directory path where the tlschexport.exe file was available.
Solution
Perform the following steps on the Main database computer:
a. In the Properties dialog of the scheduled export job, navigate to Steps, Export Step, Edit.
b. Specify the full path of the tlschexport.exe in the following format
‘”<Drive name>:\<path>\tlschexport.exe”. . . . .other details’
Ensure that the double quotation marks are specified at the beginning (after the single quotation mark) and after the tlschexport.exe file name. The single quotation marks must continue to be specified at the beginning and at the end.
4. Problem
In a scenario where an Export Configuration is enabled, if Main database is uninstalled, and then reinstalled on a different computer, the Schedule enabled column continues to display Yes for the Configuration although it was enabled on the computer from which Main database was uninstalled.
Solution
Run the following SQL command on the computer on which Main database is reinstalled:
Update tblexportconfiguration
Set bIsScheduled = 0, nFilterID = NULL, bCreateNewFile = NULL, tClientLangString = NULL
The value in the Schedule enabled column for those Export Configurations that were previously enabled is now set to No.
5. Problem
For an export configuration for which Scheduling is enabled, although I modified the format of the destination file, the data is exported to the original file specified in the SQL job.
For example, the SQL job is configured to export data to a .xls type of destination file. In the Export wizard, I modify the destination file type to .xml. When the SQL job is run, data is exported in xml format to the .xls file.
Solution
Carry out the following steps in Desktop Client:
a. Disable the Scheduling of the Configuration.
b. Modify the format of the destination file to the required file type.
c. Enable the Scheduling of the Configuration.
6. Problem
Occasionally, export of data in MS Excel format fails.
Cause
You are not logged on to the computer as an Administrator.
Solution
Log on to the computer as an Administrator, and perform the export operation.