Incident list would not appear

Incident list would not appear

After upgrading SysAid versions, incident list would not appear.

Instead, you see an error message -

'The list can not be loaded, because it was defined with a bad query. Click "Customize View" to review the view settings and try again.'

Go to your database, run this query - select version from version. You may see the same version number (of the tables) as the version of the new SysAid Server software.

Run this query - delete version from version. You may see different old version numbers (of tables), while the newest version number has disappeared. That is correct.

Go see the incident list. It appears now. Congratulations!

Instructions on how to download and connect your server with ms sql database

1) please download the migrated database from the provided link.
2) In the zip folder you will find MDF and LDF files. Please attach it to your mssql server.
2) On the SysAid server, please go to servics.msc and stop the sysaid server service.
3) Go to SysAidServer\root\WEB-INF\conf folder,locate the file called "serverconf.xml" and edit it with notepad.
4) Find the following lines:

<dbConf>
<dbDriver>org.apache.derby.jdbc.EmbeddedDriver</dbDriver>
<dbUrl>jdbc:derby:default</dbUrl>
<dbUser>sysdba</dbUser>
<dbPassword>masterkey</dbPassword>
<dbType>derby</dbType>
<dbEncoding>utf-8</dbEncoding>
<dbMultiply>false</dbMultiply>
<dbMainName>ilient</dbMainName>
</dbConf>

And replace them with these lines :

<dbConf>
<dbDriver>net.sourceforge.jtds.jdbc.Driver</dbDriver>
<dbUrl>jdbc:jtds:sqlserver://"replace this with your database server's IP:1433/"replace this with the database name"</dbUrl>
<dbUser>"replace this with the database user name"</dbUser>
<dbPassword>"replace this with your database password"</dbPassword>
<dbType>mssql</dbType>
<dbEncoding>utf-8</dbEncoding>
<dbMultiply>false</dbMultiply>
<dbMainName>ilient</dbMainName>
</dbConf>


5) Once you finished to edit this file, save it, and close it.
6) Go to services.msc and start SysAid server service.
7) Make sure that you are able to log into SysAid.

* Please note that it is best to use the "SA" user from the database server, since this user is usally not restricted by any password policies of the organization.
* Also it is best to have the database owned by the "SA" user.

SysAid - In RDS list, can not see the machine I have installed RDS software on

Problem: SysAid - In RDS list, can not see the machine I have installed RDS software on

Solution: On the machine I have installed RDS on, go to the folder -

C:\Program Files\SysAidRemoteDiscovery\root\WEF_INF\root, open the text file -

Discovery Services.properties

There are two lines containing the IP address of the SysAid server. The first one is with the port 8080, the second one without.

What we need to do is to just add ':8080' at the end of the second line of IP address.

Save it. Restart the RDS service.

Done.

SysAid Old Service Requests Not Show Up

Problem: After I re-installed SysAid, old service requests were all gone.

Solution: When I re-installed SysAid, I created a new database named 'SysAid'. But I saw that there were two databases within MS SQL Server Management Studio. One was 'SysAid', the other 'SysAid_cics'. I knew that our former database name was 'SysAid_cics'. I changed the database name in 'Program Files\SysAid Server\root\WEB-INF\conf\ServerConf.xml' from SysAid into SysAid_cics. Problem is gone.

SysAid server service can not be started

Edit the file ‘C:\Program Files\SysAidServer\conf\wrapper.conf

wrapper.java.maxmemory=1024 (Mr Kobi Versano of SysAid changed this from 2048 into 1024)
The SysAid server service then can be started.