Hi all,
I am trying out OTRS as a completely new user for our company.
Installation on a centos 6.4 server according to instructions went well.
I created an agent and a testuser. Testuser created a ticket through the /customer.pl webinterface.
What happens is that the testagent receives a notification (as intended) with a link to the ticket.
Now , when you click on the link, I receive the message: Error Message: Module Kernel/Modules/AgentTicketZoomTicketID3.pm not found!
The log show: Module Kernel/Modules/AgentTicketZoomTicketID3.pm not found!
When I search this forum about this, i cannot find any similar errors, so maybe somebody can shed some light on this for me?
Rgds.
New ticket notification error in backend?
Moderator: crythias
-
crythias
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: New ticket notification error in backend?
You mistyped the link provided.
Provide the url you created in the autoreply and the result the recipient received.
Provide the url you created in the autoreply and the result the recipient received.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: New ticket notification error in backend?
Thank you for your reply.
I checked all the settings again, and now because of your answer, I was more certain that it had to be caused by someting other than OTRS.
I checked again and discovered that a reverse proxy setting was incorrect. I changed some rewrite rules and now it works.
Thank you very much.
High regards.
I checked all the settings again, and now because of your answer, I was more certain that it had to be caused by someting other than OTRS.
I checked again and discovered that a reverse proxy setting was incorrect. I changed some rewrite rules and now it works.
Thank you very much.
High regards.