Article ID: 52318 - Last Review: August 7, 2015
Go to services.msc . Click on the prairieFyre Workforce Management Service and Restart.
PROBLEM
When the WFM Connector exports data, some intervals return 0KB files.
SYMPTOMS
In the prairieFyre.WFM.Services.log file you will see warnings like the following:
Error: 2015-Apr-14 19:15:42.237 SQL Exception encountered in GetDataForPeriod: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ()
CAUSE
There is a timeout value configured in the registry that determines how long a SQL operation can take to connect or complete. WFM uses this for the completion time.
RESOLUTION
You will need to increase the timeout period used for the SQL connection.
NOTE: This solution requires a registry edit. Please use caution when making changes.
- On the MiContact Center server open the registry editor regedit.exe .
- Go to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\PrairieFyre Software Inc\CCM\Enterprise\ .
- Right click on ConnectionString and select Modify.
- The contents will look like: Persist Security Info=false;Integrated Security=SSPI;Data Source=.\SQLEXPRESS;Initial Catalog=CCMData;Connect Timeout=30;
- Modify the Connect Timeout=##; value at the end. We recommend incrementing the timeout value by 30 (measured in seconds) and testing until you are no longer seeing 0KB files.
- NOTE: If you are using the prairieFyre.WFM.Utilities.HistoricalDataRecollector.exe application instead, you will need to restart the program for the settings to take effect.
APPLIES TO
MiCC Version 7.X and newer
Keywords: WFM connector 0KB empty file no data interval intervals timeout