Evolution Technical Information Sharing

Transcription

1 Evolution Technical Information Sharing 25 June 2012 ARTICLE 1 The following error message may be displayed when trying to link a document to an incident : REASON AND SOLUTION: 1. First always ensure that the relevant Windows user accounts have the required read and write access to the dedicated Document Storage Path as setup on the Contact Management Defaults \ Document Storage Path field 2. If the above is in order, then consider that the Users folder, as mentioned in the above screenshot, might be considered to be a protected folder on the relevant (e.g. Evolution) server PC. Therefore, rather migrate the Resolve Document Storage directory to another location on the server PC, e.g. C:\Resolve Document Storage

2 ARTICLE 2 The following error message might be displayed when opening a specific company REASON AND SOLUTION: The company might be listed on the Evolution company logon screen, but it s actually missing in MS SQL Management Studio Therefore, restore a backup. ARTICLE 3 The following message may be displayed when trying to open the Batch Properties of a GL Journal batch

3 REASON AND SOLUTION: The specific agent attempting to open the Batch Property screen has net been given the following Access Permission rights on the Agent Administration Access permission tab: Simply selecting the above option, while the agent is logged out of the company, should resolve the matter ARTICLE 4 The following error message might be received when opening Pastel Evolution:

4 When opening the BIC Report Manager the following message is received, and you cannot run any BIC report from the Evolution front end or even open Report Manager to run it from there. SOLUTION: 1. First of all, notice that BIC is not designed to work on a demo license on a Terminal Server PC. Therefore ensure if this is perhaps not the case. If you therefore see Business Intelligence Centre listed under the Help / About / Modules registered list, do the following 2. Rename the C:\EvoBICMetadata folder to EvoBICMetadataold if you have any customised BIC reports 3. Uninstall Evolution and BIC 4. Delete the installed Pastel Evolution folder if still in place 5. Delete all traces of Pastel Evolution and BIOC in the Registry under HKEY Local machine and HKEY Current user For BIC, use the following Registry clean up procedures: 1. In the PC s Registry, delete the complete BICEvolution key under a. HKEY_CURRENT_USER Software as well as under b. HKEY_LOCAL_MACHINE Software 2. Do a Registry search (Edit Find) for the Alchemex key and delete all keys found. There are quite a substantial number of them and ensure all keys found are deleted. Therefore make use of the Edit / Find Next menu until no more Alchemex records are found.

5 Note the following: A possible Search find could be an Alchemex value on the right hand of the screen, but on the left hand you will notice an opened Registry folder where the Registry key belongs to (as showed below in red). Therefore, delete the complete folder on the left hand (including all sub folders). BUT ALWAYS ENSURE THE FOLDER YOU DELETE ON THE LEFT SIDE ACTUALLY CONTAINS AN ALCHEMEX RELATED KEY ON THE RIGHT. The Registry search tool has a habit of jumping automatically to the next folder and this one is not necessarily supposed to be deleted as well. 6. Restart the PC and install Evolution, not including BIC 7. Browse the Evolution install disk to the BIC folder and install it, by browsing its installation into the relevant existing Pastel Evolution folder 8. Copy the contents (Alchemex.svd file and Template folder) of the EvoBICMetadataold folder into the newly created C:\EvoBICMetadata folder and replace files if needed

6 ARTICLE 5 What could cause the following problem on the Trial Balance as ran in a segmented GL company 1. The Accounting Year is for March to February 2. Run the Trial Balance for the end of Year 3, February 2011 The total debits and Credits are in balance and equal R , no problem 3. Run the Trial Balance for the end of Year 4, February 2012 The PY (Previous Year) Debits = R ,61 The PY (Previous Year) Credits = R This is obviously incorrect as the PY Debits/Credit values when the report is ran on February 2012, should be equal to the debits/credits for the report ran on February Not only are they not in balance, but the PY Debit and Credit values are not the same also SOLUTION: In a recent case study the following was found: The GL account segments are: Account Number, Region and Branch The above problem became evident when the Trial Balance report filer was set to, instead of the lowest segment, Branch, when running it on both February 2011 and February 2012

7 When the report was ran on February 2012, by selecting the Branch option, the PY Debits/Credits values agreed to the actual Debit/Credit values for the same report as ran on February 2011