October 7th, 2010
The Software Tool House Diary Editor allows you to edit any historical entry in any Remedy ARS Form’s Diary Field. Diary Editor functions by updating only the records’ diary field contents using a Merge. In effect, it is similar to exporting the records’ data, editing it manually (and carefully), and importing that data back into the record. All Remedy server authentications and workflow are adhered to. Merge filters are fired or can be inhibited.
The Diary Editor is licensed annually on a server-by-server basis. Licenses are free.
Limitation of Liability
This program is provided “as-is”. We are in no way liable for any losses arising from your use of this program. It is your responsibility to evaluate this program. It is your responsibility to backup and protect your data.
You need Administrator rights to use Diary Editor. Your Administrator can open it to all users.
You may download the Diary Editor anytime. Once you have filled in the License request form, you will receive a license key.
August 24th, 2010
Read the possible causes carefully, it clearly says “Refer to Installation Document” before you attempt”.
One big mistake what everyone tends to do is start doing things when they have to read/research first. For any successful remedy installation, we need to tune the system and database first. All these details are readily available in BMC documentation, don’t get scared of by seeing the number of pdf pages, instead skim through the parts which you don’t need to know. Like, if your OS is Windows, you don’t have to read everything about LINUX/UNIX.
Regarding the error, it is based on database and connectivity to the database. Connectivity to the database is essential for remedy server as all the actions that are performed are ultimately end up in it. First thing you need to do here is, try connecting to database using a client software, based up on the database you are using, use the clients like Toad, WINSQL, SQL Management tool or any other preferred. If you are able to connect to the database, then go to the database setting to open the TCP/IP port.
Error “TCP/IP connection to the host XYZ using port number 1433 failed.” is caused with SQL database because the TCP/IP settings are disabled.
Follow these steps to fix this issue:
Set your SQL Server connections to allow TCP/IP:
- Open the SQL Server Configuration Manager.
- Click Network Configuration for your SQL Server instance.
- Make sure that TCP/IP Protocol is enabled.
- View the TCP/IP Properties dialog box for your database instance, and make sure that the IP Addresses tab has a TCP Port number specified. (The default port is 1433.)
- Restart all SQL Server services to effect this change.
Just back a step on the remedy installer and click Next, it will detect the database instance, if not you can always manually.
If you still need help configuring TCP/IP ports, look here