SYSAID 7.5

 
Author
Message
SysAid Customer Relations
761
 


Hi Smeagol and yessivenezuela,

Please contact us (helpdesk@sysaid.com by chat or by phone) or open a Service Request in our help desk https://helpdesk.sysaid.com. we should resolve your issues remotely.

Looking forward to your response.

Thanks Inna
Super SysAider
84
 
Opening an SR is not possible for me... I'm just using SysAid as a hobby. Buying support is not an option for me...
Assumption is the mother of all fuckups...
SysAid Customer Relations
761
 
Dear Smeagol,

This issue can be solved by upgrading your tomcat from tomcat 4 to tomcat 6 if you have the idea of how doing this then great if not you should still contact us in order we could do it remotely.

Thanks

Inna
SysAider
4
 
I have de same problem. Do you help me with upgrade from tomcat 4 to tomcat 6?
Thanks.
Super SysAider
84
 
At this very moment I'm working on the issue with help of Inna. So please be patient...
Assumption is the mother of all fuckups...
SysAid R&D
37
 
7.5.03 Free upgrade installation[u]

If you have upgraded using sysaid free upgarded and you receive the following error message:

"Tomcat 6 is required for this SysAid version. please contact support for further information !!"

Please use the attached patch upgrade, it will add the missing Tomcat 6.0 files.



This message was edited 1 time. Last update was at Nov. 11, 2010 07:17 AM

Super SysAider
55
 
is about to begin
SysAider
40
 
upgraded from Pro 7 to 7.5 Upgrade went smooth, all agents deployed smooth as well.

Great release so far. Running alot smoother and faster.
Super SysAider
84
 
For me this did it!
Assumption is the mother of all fuckups...
Super SysAider
55
 
are you in the conference webinar SysAid?? I, yes. Excellent
SysAider
43
 
worked here, with new upgrade
Win 2k server
SysAider
11
 
I just upgrade the production server from 7.0.5 to 7.5.03 and now all the routing defined are not associate the service request to the corresponding Group.
I’m using routing to send notification and to automatically associate the service requests to the Groups and not to the Administrators.

Any idea?
SysAider
20
 
Unfortunately, the patch did not work for me. I still get a "Tomcat 6 is required for this installation" even after running the 7.5.03 patch.
I have rebooted the server, restarted the SysAid service etc, but no joy.
When accessing Sysaid, I get the file list with "Apache Tomcat/4.1.24-LE-jdk14" at the bottom of the page. However, when I log in, it says v7.5.03 for the version number on the top right of the page.
Super SysAider
84
 
mark25787 wrote:Unfortunately, the patch did not work for me. I still get a "Tomcat 6 is required for this installation" even after running the 7.5.03 patch.
I have rebooted the server, restarted the SysAid service etc, but no joy.
When accessing Sysaid, I get the file list with "Apache Tomcat/4.1.24-LE-jdk14" at the bottom of the page. However, when I log in, it says v7.5.03 for the version number on the top right of the page.
Hi Mark,

Did you do a fresh download of the 7.5.0.3-package? Please check Inna's thread: CLICK
Assumption is the mother of all fuckups...
SysAid Customer Relations
761
 
Adrian Anton wrote:I just upgrade the production server from 7.0.5 to 7.5.03 and now all the routing defined are not associate the service request to the corresponding Group.
I’m using routing to send notification and to automatically associate the service requests to the Groups and not to the Administrators.

Any idea?


Dear Adrian Anton i have opened for you a service request in our help desk # 331898 please reply to it in order we could further investigate this issue.

Thanks Inna