Alerts Server Troubleshooting: Difference between revisions

From RangerMSP Wiki - PSA software for MSPs and IT services providers
Jump to navigation Jump to search
No edit summary
No edit summary
Line 8: Line 8:


'''Solution:''' You should check the following options:
'''Solution:''' You should check the following options:
#It can take up to 10 minutes for new Alerts preferences to take effect. You can wait, or restart the Commit Server service in order for the settings to take effect immediately.
#It can take up to 10 minutes for new Alerts preferences to take effect. You can wait, or restart the CommitCRM Server service in order for the settings to take effect immediately.
#Make sure your system administrator has activated the system alerts (set the system to ON using the ServerConfig utility) and that the CommitServer Windows service is running).
#Make sure your system administrator has activated the system alerts (set the system to ON using the ServerConfig utility) and that the CommitServer Windows service is running).
#When testing the alerts, note that you will not receive Alerts for changes you have made. You should perform the changes with a different Commit user.
#When testing the alerts, note that you will not receive Alerts for changes you have made. You should perform the changes with a different CommitCRM user.


====='''I checked all of the settings, the alerts system is activated, and and I still don't get email alerts'''=====
====='''I checked all of the settings, the alerts system is activated, and and I still don't get email alerts'''=====
Line 16: Line 16:
'''Solution: '''In some cases, old settings already created wrong email alerts which are "stuck" in the outgoing queue and prevent the system from going on to the new alerts. In this case, you should first cleanup the outgoing queue:
'''Solution: '''In some cases, old settings already created wrong email alerts which are "stuck" in the outgoing queue and prevent the system from going on to the new alerts. In this case, you should first cleanup the outgoing queue:
#Stop CommitServer service
#Stop CommitServer service
#Run <server>\Commit\Server\ServerConfig and make sure all settings are correct. Check that the "From Email Address" is correct. Save any changes you make.
#Run <server>\CommitCRM\Server\ServerConfig and make sure all settings are correct. Check that the "From Email Address" is correct. Save any changes you make.
#To delete old pending alerts, delete all the files in the following folder: <server>\Commit\Server\QSysEDOutbox\
#To delete old pending alerts, delete all the files in the following folder: <server>\CommitCRM\Server\QSysEDOutbox\
#Restart CommitServer service and verify email alerts are being sent
#Restart CommitServer service and verify email alerts are being sent


For more Outgoing Emails troubleshooting, please refer to the [[Troubleshooting#Email Connector Installation Troubleshooting|Email Connector Troubleshooting section below]] (both the Email Connector and the Alerts Server use the same Outgoing mechanism).
For more Outgoing Emails troubleshooting, please refer to the [[Troubleshooting#Email Connector Installation Troubleshooting|Email Connector Troubleshooting section below]] (both the Email Connector and the Alerts Server use the same Outgoing mechanism).
   
   
====='''I made changes in Commit (i.e. added a new Ticket, etc.) and I am not getting any Alerts'''=====
====='''I made changes in CommitCRM (i.e. added a new Ticket, etc.) and I am not getting any Alerts'''=====


'''Solution: '''You only receive Alerts for changes made by other people. When you make a change in the system on entities related to you (e.g. you assign yourself a new Ticket), you will not receive an Alert.
'''Solution: '''You only receive Alerts for changes made by other people. When you make a change in the system on entities related to you (e.g. you assign yourself a new Ticket), you will not receive an Alert.
Line 28: Line 28:


==See Also==
==See Also==
*[[Alerts Server|Commit Alerts Server]]
*[[Alerts Server|CommitCRM Alerts Server]]
*[[Troubleshooting]]
*[[Troubleshooting]]


[[Category:Troubleshooting]]
[[Category:Troubleshooting]]
__NOTOC__
__NOTOC__

Revision as of 10:07, 28 August 2013

Troubleshooting > Alerts Server Troubleshooting


I set my user to receive Alerts but I do not get any email alerts

Solution: You should check the following options:

  1. It can take up to 10 minutes for new Alerts preferences to take effect. You can wait, or restart the CommitCRM Server service in order for the settings to take effect immediately.
  2. Make sure your system administrator has activated the system alerts (set the system to ON using the ServerConfig utility) and that the CommitServer Windows service is running).
  3. When testing the alerts, note that you will not receive Alerts for changes you have made. You should perform the changes with a different CommitCRM user.
I checked all of the settings, the alerts system is activated, and and I still don't get email alerts

Solution: In some cases, old settings already created wrong email alerts which are "stuck" in the outgoing queue and prevent the system from going on to the new alerts. In this case, you should first cleanup the outgoing queue:

  1. Stop CommitServer service
  2. Run <server>\CommitCRM\Server\ServerConfig and make sure all settings are correct. Check that the "From Email Address" is correct. Save any changes you make.
  3. To delete old pending alerts, delete all the files in the following folder: <server>\CommitCRM\Server\QSysEDOutbox\
  4. Restart CommitServer service and verify email alerts are being sent

For more Outgoing Emails troubleshooting, please refer to the Email Connector Troubleshooting section below (both the Email Connector and the Alerts Server use the same Outgoing mechanism).

I made changes in CommitCRM (i.e. added a new Ticket, etc.) and I am not getting any Alerts

Solution: You only receive Alerts for changes made by other people. When you make a change in the system on entities related to you (e.g. you assign yourself a new Ticket), you will not receive an Alert.


See Also