INDSOFT INSTALLATION – TROUBLESHOOTING
Following are a few Tips which may be followed to resolve Connectivity Issues during Initial Setup of Indsoft.
The Installation of Indsoft Server has following Stages :
Installation of Interbase Server.
Installation of Datadirect ODBC driver Files.
Conversion of Legacy Data &
Uploading Converted Data into Template Database.
Once the above steps are successfully executed, users can log in to Indsoft through Default Users available and Update Initial masters as described in Installation Document.
Connectivity Issues can arise during any of the above steps, if the execution of Setup Program was not successful OR the Setup Source was corrupt OR Operating System Files were Corrupt or could not be updated by Setup Program.
To verify Successful Connectivity, few checks may be performed at the end of every Step.
Please ensure Local Area Network has been set up successfully , in case more than one PC is to be connected to Indsoft, and that TCP/IP setup is in Place . Please note the IP Addresses of both Server PC and Client PC(s) beforehand.
After Executing Step1.Bat i.e.
“Installation of Interbase Server/Client & Installation of Datadirect ODBC “ has been completed , Following may be verified.
In Server PC
Verify that an Entry as below exists in the “Services” file
(in Case of XP – under ‘C:\WINDOWS\system32\drivers\etc’ folder, in case of Win98 , under ‘C:\windows’ folder)
“gds_db 3050/tcp # InterBase Server”
If not , check if the services file is read only. If yes , remove read only tag and manually add the entry or Re-install Indsoft- Step1.bat.
Execute “Start Menu –> Programs -> Borland InterBase 7.5 Server [instance = gds_db] -> InterBase Server Manager [instance = gds_db]”
The Status Should Show “Running” . If Not Click “Start” Button.
When the Status Shows Running , Click on “Guardian Properties “. This Should Open another Window with entry showing as “Server Started”. If no such entry is shown or the Window does not pop-up then there might have been some error during installation or the Interbase License file is corrupted.
To Correct this, Stop & Close “Interbase Server Manager”. Delete Borland.lic file from “C:\Program Files\Borland\Interbase” folder. Now , Replace “reg624.slip” file from Installation Diskette (under “Final Installation” Folder) into this folder i.e. “C:\Program Files\Borland\Interbase”
Repeat Step 2., if Problem Persists , try Reinstallation to correct the error , or Contact IS Help Desk.
From Command Prompt ( C:\ ), issue following command :
C:\> Ping INDSERVER
The Output should be like :
“Reply from 127.0.0.1: bytes=32 time<1ms TTL=128”
If the above Fails, Open “c:\windows\system32\drivers\etc\hosts “ ( for XP ) or “c:\windows\hosts” (for Win98) and look for an entry like
127.0.0.1 Localhost Indserver
If no such entry is there, manually add the entry, and repeat above command.
If still the problem persists, contact Hardware support Engineer for OS related Calls.
If above all has successfully executed , logically , connectivity to Interbase Database through Indsoft Application should happen without fail. To check this, Execute Indsoft.exe under “C:\Indsoft folder” by double clicking on it. Login Screen Should open, which will mean that connectivity is through.
In Client PC
From Command Prompt ( C:\ ), issue following command :
C:\> Ping INDSERVER
“Reply from xxx.xxx.xxx.xxx: bytes=32 time<1ms TTL=128”
Where xxx.xxx.xxx.xxx is the IP address of the Server PC.
[run c:\> IPCONFIG (for XP) or c:\> WINIPCFG (for 98) to get the IP Address of Server PC]
If this fails , Check LAN Connection or Lookout for cable disconnection . If all is Ok , Still Ping fails , Call Hardware support Engineer to correct this.
Execute Indsoft by double clicking on C:\Indsoft\Indsoft.exe , Login Screen Should Appear ( when we have successfully established connection in Server PC ) . If No login Screen appears , or some Error Message is displayed , Check for Windows “Firewall” in Server PC. If Firewall is on , Make an exception in Firewall by allowing TCP/port no 3050 . Repeat above again. If Still the error remains , Call IS HELP Desk.
Note: We have received feedback from our field locations that many a times connectivity issues have been faced at different Sites due to Virus infected PCs . On Installation of Proper Antivirus Software , these issues could be resolved. Therefore , we recommend that proper Antivirus Software may be installed at Installation Sites in All PCs which should be regularly updated with update patches.
On successful completion of above Run “Step2.Bat” from Installation Folder for Data Conversion and Uploading into Indsoft Template Database.
Please note down the Drive Letter whatever has been entered as the Installation drive in server and client PC. Please ensure that proper backup is being taken every day end from the SERVER PC from the designated drive’s Indsoft Folder , once uploading of data is complete and Operation in INDSOFT Version 8 has Started.
hope...you are sucessfully done....wish you all the best
Following are a few Tips which may be followed to resolve Connectivity Issues during Initial Setup of Indsoft.
The Installation of Indsoft Server has following Stages :
Installation of Interbase Server.
Installation of Datadirect ODBC driver Files.
Conversion of Legacy Data &
Uploading Converted Data into Template Database.
Once the above steps are successfully executed, users can log in to Indsoft through Default Users available and Update Initial masters as described in Installation Document.
Connectivity Issues can arise during any of the above steps, if the execution of Setup Program was not successful OR the Setup Source was corrupt OR Operating System Files were Corrupt or could not be updated by Setup Program.
To verify Successful Connectivity, few checks may be performed at the end of every Step.
Please ensure Local Area Network has been set up successfully , in case more than one PC is to be connected to Indsoft, and that TCP/IP setup is in Place . Please note the IP Addresses of both Server PC and Client PC(s) beforehand.
After Executing Step1.Bat i.e.
“Installation of Interbase Server/Client & Installation of Datadirect ODBC “ has been completed , Following may be verified.
In Server PC
Verify that an Entry as below exists in the “Services” file
(in Case of XP – under ‘C:\WINDOWS\system32\drivers\etc’ folder, in case of Win98 , under ‘C:\windows’ folder)
“gds_db 3050/tcp # InterBase Server”
If not , check if the services file is read only. If yes , remove read only tag and manually add the entry or Re-install Indsoft- Step1.bat.
Execute “Start Menu –> Programs -> Borland InterBase 7.5 Server [instance = gds_db] -> InterBase Server Manager [instance = gds_db]”
The Status Should Show “Running” . If Not Click “Start” Button.
When the Status Shows Running , Click on “Guardian Properties “. This Should Open another Window with entry showing as “Server Started”. If no such entry is shown or the Window does not pop-up then there might have been some error during installation or the Interbase License file is corrupted.
To Correct this, Stop & Close “Interbase Server Manager”. Delete Borland.lic file from “C:\Program Files\Borland\Interbase” folder. Now , Replace “reg624.slip” file from Installation Diskette (under “Final Installation” Folder) into this folder i.e. “C:\Program Files\Borland\Interbase”
Repeat Step 2., if Problem Persists , try Reinstallation to correct the error , or Contact IS Help Desk.
From Command Prompt ( C:\ ), issue following command :
C:\> Ping INDSERVER
The Output should be like :
“Reply from 127.0.0.1: bytes=32 time<1ms TTL=128”
If the above Fails, Open “c:\windows\system32\drivers\etc\hosts “ ( for XP ) or “c:\windows\hosts” (for Win98) and look for an entry like
127.0.0.1 Localhost Indserver
If no such entry is there, manually add the entry, and repeat above command.
If still the problem persists, contact Hardware support Engineer for OS related Calls.
If above all has successfully executed , logically , connectivity to Interbase Database through Indsoft Application should happen without fail. To check this, Execute Indsoft.exe under “C:\Indsoft folder” by double clicking on it. Login Screen Should open, which will mean that connectivity is through.
In Client PC
From Command Prompt ( C:\ ), issue following command :
C:\> Ping INDSERVER
“Reply from xxx.xxx.xxx.xxx: bytes=32 time<1ms TTL=128”
Where xxx.xxx.xxx.xxx is the IP address of the Server PC.
[run c:\> IPCONFIG (for XP) or c:\> WINIPCFG (for 98) to get the IP Address of Server PC]
If this fails , Check LAN Connection or Lookout for cable disconnection . If all is Ok , Still Ping fails , Call Hardware support Engineer to correct this.
Execute Indsoft by double clicking on C:\Indsoft\Indsoft.exe , Login Screen Should Appear ( when we have successfully established connection in Server PC ) . If No login Screen appears , or some Error Message is displayed , Check for Windows “Firewall” in Server PC. If Firewall is on , Make an exception in Firewall by allowing TCP/port no 3050 . Repeat above again. If Still the error remains , Call IS HELP Desk.
Note: We have received feedback from our field locations that many a times connectivity issues have been faced at different Sites due to Virus infected PCs . On Installation of Proper Antivirus Software , these issues could be resolved. Therefore , we recommend that proper Antivirus Software may be installed at Installation Sites in All PCs which should be regularly updated with update patches.
On successful completion of above Run “Step2.Bat” from Installation Folder for Data Conversion and Uploading into Indsoft Template Database.
Please note down the Drive Letter whatever has been entered as the Installation drive in server and client PC. Please ensure that proper backup is being taken every day end from the SERVER PC from the designated drive’s Indsoft Folder , once uploading of data is complete and Operation in INDSOFT Version 8 has Started.
hope...you are sucessfully done....wish you all the best
