Checklist: Difference between revisions

From Accelerator for SageCRM
No edit summary
No edit summary
 
(8 intermediate revisions by the same user not shown)
Line 11: Line 11:
   From that screen check that the user is in the list
   From that screen check that the user is in the list


3. In the Outlook settings check that the active path is set and that the value is correct
In the Outlook settings check the following :
 
[[File:Final_settings_tab.jpg]]
[[File:Final_settings_2.png]]
 
3. That the active path is set and that the value is correct


[[File:activepath.png]]
[[File:activepath.png]]


4. You cannot use the ampersand '&' character or '%' character in a password when using Accelerator (this is due to a web-service bug in Sage CRM).
4. You cannot use the ampersand '&' character or '%' character or '#' hash in a password when using Accelerator (this is due to a web-service bug in Sage CRM).
**Other strange characters may also be unsupported-remove all to test
**Other strange characters may also be unsupported-remove all to test


Line 21: Line 26:


6. Check that IISAutologon is '''not''' check (This is only used if your Sage CRM system is using IISAutologon)
6. Check that IISAutologon is '''not''' check (This is only used if your Sage CRM system is using IISAutologon)
[[File:Settings3.jpg]]

Latest revision as of 11:56, 14 March 2023

A checklist to be used when a user cannot log on

1. User is allowed log on to CRM via CRM's web services (Allow WebService Access:True)

  Navigate to the users details (Administration -> Users -> Users) and view the users details and check that the
  "Allow WebService Access" setting is set to true

2. Accelerator license check.

  Navigate to "Administration -> CRM Together -> Accelerator"
  From that screen check that the user is in the list

In the Outlook settings check the following :

3. That the active path is set and that the value is correct

4. You cannot use the ampersand '&' character or '%' character or '#' hash in a password when using Accelerator (this is due to a web-service bug in Sage CRM).

    • Other strange characters may also be unsupported-remove all to test

5. Uncheck "Ping to CRM" in the user settings

6. Check that IISAutologon is not check (This is only used if your Sage CRM system is using IISAutologon)