https://techwiki.neosys.com/api.php?action=feedcontributions&feedformat=atom&user=SunnyNEOSYS Technical Support Wiki - User contributions [en]2026-05-29T18:13:14ZUser contributionsMediaWiki 1.43.3https://techwiki.neosys.com/index.php?title=Installing_NEOSYS_Service&diff=719Installing NEOSYS Service2011-07-04T11:55:33Z<p>Sunny: /* Installing initial Database */</p>
<hr />
<div>= INSTALLING NEOSYS SERVICE =<br />
<br />
Reference to X:\ in the notes below denotes the actual drive letter and needs to be replaced (eg D:\)<br />
<br />
== Main installation: ==<br />
<br />
Make sure NOT TO COPY an existing NEOSYS installation to another location and ONLY do a <br />
completely new install with a fresh database, because copying a folder will copy a variety of <br />
hidden configurations. <br />
<br />
=== Installing NEOSYS on partitions ===<br />
Good server management practice is to have separate partitions for operating system (C:) and data partitions (D:)<br />
<br />
In the case of operating system reinstallation (which causes the loss of the C: partition) if NEOSYS programs and data were installed on D: can be preserved. If there is only one partition then NEOSYS programs and data will have to be backed up and restored.<br />
<br />
==== Multiple Partitions ====<br />
NEOSYS should be installed on a different partition rather than the C drive for reasons already explained above (eg. D drive)<br />
<br />
==== Single Partition ====<br />
If there is only one partition then you have to inform the client to take the effort to reinstall the operating system or using third party repartitioning tools to create separate partitions.<br />
<br />
=== Downloading and running installation files ===<br />
# http://www.neosys.com/support/neosys.exe ... and unzip/install to X:\neosys (or to X:\hosts\clientcd for multi-installation on one server)<br />
# http://www.neosys.com/support/neosys2.exe ... and install same as previous step.<br />
<br />
=== Creating shortcuts ===<br />
In x:\neosys (or x:\hosts\clientcd), make a shortcut called ‘Maintenance’ and link it to<br />
<br />
x:\neosys\neosys\adagency.bat (for Adagency install)<br />
<br />
or <br />
<br />
x:\neosys\neosys\accounts.bat (for Accounts install)<br />
<br />
=== Activating NEOSYS using authorization number ===<br />
<br />
Start NEOSYS Maintenance, select Initial Backup and it will give a “Computer Number” and ask for an “Authorisation No”<br />
<br />
Send the computer number to NEOSYS admin to get the authorization no.<br />
<br />
If you cannot get the authorization number immediately then you can close NEOSYS and when you reopen NEOSYS it will still give the same computer number and accept the same authorization number.<br />
<br />
=== Installing initial Database ===<br />
<br />
Download the initial database file from http://www.neosys.com/support/BACKUP.ZIP and place it in D drive (or any other drive) - but make sure that this file exists in the root folder i.e. D:\BACKUP.ZIP<br />
<br />
Follow the steps below:<br />
#Click on the Maintenance icon.<br />
#Select BASIC DATA SET and type in the NEOSYS username and password. (If the system does not prompt for a username and password,then go to Quit > Quit to next user and type the same in. If you do not enter with a username and password then NEOSYS will not allow you to restore the database). The first time when you enter maintenance you will get a command box (like when you do F5). If you do not get a command box, hit the F5 key and get it on the screen and hit ESC after you get it. <br />
#Now restore the BACKUP.ZIP (STARTUP DATABASE), to do so go to General > Backup & Data Management, select (the 4th option) Restore from disk or diskette. select D drive (or whichever drive you put the backup.zip file in) and follow the prompts ahead.<br />
#On every successful restore or creation of dataset, system will give you a message to switch to new database always '''say NO''' to this,because the switch to database option brings you back to the BASIC DATA SET. Hence press the ESC button, type EXIT on the F5 prompt.<br />
#Now startup maintenance again and you will find a new database "STARTUP DATABASE" select it and login with NEOSYS username and password. Once you enter you may find a prompt "TASK ADDED" follow the prompt and continue.<br />
#After you have logged in, go to General > Backup & Data Management > Delete a dataset and select the "BASIC DATASET" to delete, to confirm the delete system will ask you to enter the dataset code. Enter the code and delete the basis dataset.<br />
#Now create a new dataset for the client, go to general > Backup & Data management> Create a new dataset, select (6th option) and follow the instruction on how to setup database code from the following link "http://techwiki.neosys.com/index.php/Installing_NEOSYS_Service#Assigning_database_codes"<br />
#Once the client dataset is created,login to the clientdataset and follow the steps in above point6 and delete the STARTUP DATABASE. (while logging in to the client dataset, it ask " This database hsa been copied or the database name or code has been changed. Is this going to be a unique new master database?" select first option YES - Going to be a new independent database.<br />
#To check the list of dataset on the computer, go to go to General > Backup & Data Management > See a list of dataset in the computer(8th option).<br />
<br />
Note:<br />
#Sometimes it may tell you that you cannot use FILEMAN as you are logged in as MASTER. Hence you need to hit the ESC key, go to General > Backup & Data Management > Restore from disk or diskette, select C drive or whichever drive you put the backup.zip file in and follow the prompts ahead.<br />
#While doing the step no.2 if you get a message as below just hit enter or space and continue.<br />
<br />
[[File:Message while installing.jpg]]<br />
<br />
==== Assigning database codes ====<br />
It is necessary to make sure that the following guidelines are met while creating database codes:<br />
<br />
#The code should be within 8 letters<br />
#The client should be as recognisable as possible from the main database code<br />
#The test database code should end with the TEST word and it is not necessary that it must be recognisable<br />
#The test database code should always appear after the main database code at login<br />
<br />
Examples of wrong and right database codes:<br />
<br />
ALTO VISTA ADVERTISING<br />
ALTOVIST and XALTTEST - right AVISTA and AVTEST - wrong (AVISTA not "as recognisable as possible")<br />
<br />
CONTEXTURE ASSOCIATES<br />
CONTEXT and XCONTEST - right CONTEXT and CONTEST - wrong (CONTEST alphabetically first in the login screen database drop down)<br />
<br />
=== Creating a .CMD file to start NEOSYS Service: ===<br />
(Note: change x to the correct drive you have installed NEOSYS on)<br />
<br />
In x:\neosys create a file start MAIN-DATABASE-CODE.cmd (eg start ALTOVIST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>databasecode</b><br />
<br />
(where <b>databasecode</b> is the code of the database)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
In x:\neosys create a file start TEST-DATABASE-CODE.cmd (eg start AVTEST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>testdatabasecode</b><br />
<br />
(where <b>testdatabasecode</b> is the code of the testdatabase)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
TEST THAT THE FILES YOU HAVE CREATED CAN RUN SUCCESSFULLY<br />
<br />
ENSURE THAT YOU DO NOT CLOSE THE PROCESS WINDOWS BY USING THE X BUTTON. HIT ESC 3 TIMES ON EACH WINDOW.<br />
<br />
=== Differences for Pure Accounts Module Only Installations ===<br />
Accounts module only has a slightly different startup command. In the above, replace '''/system adagency''' with '''/system accounts''' to startup a service and use '''accounts.bat''' instead of '''adagency.bat''' to start up maintenance. Other than that, accounts module setup is identical. Pure accounts clients are very few and tend not to upgrade often so care needs to be taken when upgrading. Upgrade is perhaps surprisingly done using the adagency.exe file.<br />
<br />
=== Creating a .CMD file to copy maindata to testdata ===<br />
<br />
In x:\neosys create a file <B>copy MAINDATABASECODE to TESTDABASECODE.cmd</b><br />
<br />
xcopy x:\neosys\data\<i>maindatabasecode</i> x:\neosys\data\<i>testdatabasecode</i> /s /y<br />
<br />
eg. xcopy c:\neosys\data\<i>ALTOVIST</i> x:\neosys\data\<i>AVTEST</i> /s /y<br />
<br />
Run this file to test that it works fine.<br />
<br />
=== Setting up daily scheduled tasks ===<br />
<b>Automatic Schedules:</b><br />
NEOSYS automatically shuts down at 1am (was 2am) every morning for backup. It closes all the running processes and backups up to the selected drive.<br />
<br />
<b>Manually Configured Schedules:</b> to be done under Scheduled Tasks<br />
<br />
Note: Under Windows 2008 Standard you need to UNTICK highest privileges and UNTICK run whether user is logged in or not as shown in the screen shots that follow:<br />
<br />
1. Create a task to start one Main database process at 6:00 am daily.<br />
<br />
[[File:start1.jpg]]<br><br><br><br />
[[File:start2.jpg]]<br><br><br><br />
[[File:start3.jpg]]<br><br><br><br />
<br />
2. Create a second task to Copy Maindata to Testdata at 2:45 am daily.<br />
<br />
[[File:copy1.jpg]]<br><br><br><br />
[[File:copy2.jpg]]<br><br><br><br />
[[File:copy3.jpg]]<br><br><br><br />
<br />
<br />
(For multiple sites on the same computer put the second site starting five minutes later at 6:05am, third site starting five minutes earlier at 5:55am, the third site starting five minutes later at 6:10am and so on.)<br />
<br />
Once created, test them to see that they are working correctly by running them directly using right click- Run.<br />
<br />
[[File:task1.jpg]]<br><br><br><br />
<br />
(Use web access and go to Support Menu, System Configuration File to request 3 processes for main database and 1 for test database).<br />
<br />
Please note that test running “copy test data” should be avoided while users are online but there is no problem testing the “daily 6am startup task” at any time since it will just add an additional process.<br />
<br />
=== Configuring NEOSYS to start automatically on server start-up / reboot ===<br />
We no longer configure NEOSYS processes to start on reboot as we would like to know of the failures at the client side and hence whenever the server reboots we expect the client to inform us and we will start the process - or NEOSYS will start automatically next day at 6 am<br />
<br />
Unfortunately using this method the NEOSYS processes are not visible when you login as a user. <br />
<br />
[[Image:win_sch_task.jpg]]<br />
<br />
Schedule a task to run the main database file whenever the computer starts. In Windows 2008 you need to tick the options - Run whether user logged in or not and Run with highest privilege.<br />
<br />
Additional in Windows 2008: Tick Highest Priviledges and Run whether user logged in or not<br />
<br />
== Installing and upgrading NEOSYS pure accounting systems ==<br />
<br />
Basic installation using NEOSYS.EXE and upgrades using NEOSYS2.EXE are identical to the normal adagency installation process.<br />
<br />
Differences are as follows:<br />
<br />
# Maintenance shortcut to ACCOUNTS.BAT<br />
# Process startup file contains "/system ACCOUNTS" instead of "/system ADAGENCY"<br />
# Internet address is http://server/neosys/accounts.htm although it auto converts to http://server/neosys/default.htm??ACCOUNTS. Although not to be relied upon, the login page stores a cookie so even plain http://server/neosys or http://server/neosys/default.htm works thereafter until the cookie is lost. To get back to adagency login you use http://server/neosys/default.htm??ADAGENCY<br />
# BACKUP.ZIP files created by ADAGENCY systems and ACCOUNTS systems are slightly incompatible with the result that restoring one in the other type of system will not work. NEOSYS programmers can convert from one type to the other but it is almost never required since any ad agency that only requires accounts only module is given the adagency version of NEOSYS and accounting only clients becoming ad agencies never happened.</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Configuring_IIS&diff=712Configuring IIS2011-06-25T09:59:15Z<p>Sunny: </p>
<hr />
<div>After you have installed all the NEOSYS program files you need to configure IIS so that you can operate NEOSYS. Instructions are below.<br />
<br />
== Configuring IIS for windows 2003 ==<br />
<br />
'''Client Server:''' first step is to create a virtual directory called neosys liked to D:\neosys\neosys.net:<br />
<br />
'''NL1 Server:''' Create a website called "clientname" liked to D:\hosts\clientfolder\neosys.net <br />
<br />
[[image:figure1.jpg]]<br />
<br />
[[image:figure3.jpg]]<br />
<br />
In that folder > neosys > dll – change the Execute Permission to Scripts & Executables<br />
<br />
A new window will pop up "IP Address and Port Setting" after completion of the above step.<br />
<br />
'''Client Server:''' select *(All Unassigned)* from the drop down list of "Enter the IP address to use for the Web site" and keep the default port as 80. <br />
<br />
'''NL1 Server:''' Select the static Ip from the drop down list of "Enter the IP address to use for the Web site" and enter then next port available and click on next.<br />
<br />
[[image:Figure_2.jpg]]<br />
<br />
'''Client Server:''' Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data: <br />
<br />
'''Nl1 Server:''' Within the above clientwebsite folder create a virtual directory called data linked to D:\hosts\clientfolder\data:<br />
<br />
'''(I haven’t got the screenshot because I can only get it once I create the above)'''<br />
<br />
'''To allow file uploads''' <br />
<br />
'''Client server:''' create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
'''Nl1 Server:''' create a folder IMAGES under D:\hosts\clientfolder and within the client web site folder create a virtual directory called images linked to D:\hosts\clientfolder\images:<br />
<br />
'''(I haven’t got the screenshot because I can only get it once I create the above)'''<br />
<br />
== Configuring IIS for Windows 2008 ==<br />
<br />
==== Installing IIS ====<br />
<br />
First install IIS from Control Panel > Programs & Features > Turn Windows Features ON or OFF > Add Roles:<br />
<br />
[[image:iis1.jpg]]<br />
<br />
On the window that pops up click on next and you will get this screen, tick Web Server (IIS) - on the prompt click on Add Required Resources and then on Next:<br />
<br />
[[image:iis2.jpg]]<br />
<br />
On the next window, click on next until you get this window - tick ASP and ISAPI Extensions:<br />
<br />
[[image:iis3.jpg]]<br />
<br />
Click on Next and Finish<br />
<br />
==== Configuring IIS ====<br />
After successfully installing IIS, go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Internet Information Services (IIS) > Machine Name > Sites > Default Website:<br />
<br />
The first step is to create a virtual directory called neosys linked to D:\neosys\neosys.net:<br />
<br />
[[image:iis4.jpg]]<br />
<br />
Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data:<br />
<br />
[[image:iis5.jpg]]<br />
<br />
In the IIS Default Web Site create a another virtual directory called neosys.w3c linked to D:\neosys\neosys.w3c (only if timesheets for mac is required):<br />
<br />
[[image:iis6.jpg]]<br />
<br />
To allow file uploads – create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
[[image:iis7.jpg]]<br />
<br />
After you add all virtual directories the tree map of the Default Website should look as follows:<br />
<br />
[[image:iis8.jpg]]<br />
<br />
To configure file uploads besides adding the images directory, go under IIS > Default Website > neosys – click on Handler Mappings and delete the ISAPI you see there:<br />
<br />
[[image:iis9a.jpg]]<br />
<br />
Thereafter click on Add Script Map and fill in the details as follows – Request path: *.dll , Executable: D:\neosys\neosys.net\NEOSYS\dll\upload.dll , Name: ISAPI (once you click on OK click on YES to the confirmation box)<br />
<br />
[[image:iis9b.jpg]]<br />
<br />
Edit the hosts file under c:\windows\system32\drivers\etc\ - delete the # sign next to 127.0.0.1 localhost and incluide the # sign before ::1 localhost<br />
<br />
[[image:iis10.jpg]]</div>Sunnyhttps://techwiki.neosys.com/index.php?title=File:Figure3.jpg&diff=711File:Figure3.jpg2011-06-25T09:56:28Z<p>Sunny: </p>
<hr />
<div></div>Sunnyhttps://techwiki.neosys.com/index.php?title=Configuring_IIS&diff=710Configuring IIS2011-06-25T09:54:01Z<p>Sunny: </p>
<hr />
<div>After you have installed all the NEOSYS program files you need to configure IIS so that you can operate NEOSYS. Instructions are below.<br />
<br />
== Configuring IIS for windows 2003 ==<br />
<br />
'''Client Server:''' first step is to create a virtual directory called neosys liked to D:\neosys\neosys.net:<br />
<br />
'''NL1 Server:''' Create a website called "clientname" liked to D:\hosts\clientfolder\neosys.net <br />
<br />
[[image:figure1.jpg]]<br />
<br />
In that folder > neosys > dll – change the Execute Permission to Scripts & Executables<br />
<br />
A new window will pop up "IP Address and Port Setting" after completion of the above step.<br />
<br />
'''Client Server:''' select *(All Unassigned)* from the drop down list of "Enter the IP address to use for the Web site" and keep the default port as 80. <br />
<br />
'''NL1 Server:''' Select the static Ip from the drop down list of "Enter the IP address to use for the Web site" and enter then next port available and click on next.<br />
<br />
'''Client Server:''' Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data: <br />
<br />
'''Nl1 Server:''' Within the above clientwebsite folder create a virtual directory called data linked to D:\hosts\clientfolder\data:<br />
<br />
(I haven’t got the screenshot because I can only get it once I create the above)<br />
<br />
To allow file uploads <br />
<br />
'''Client server:''' create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
'''Nl1 Server:''' create a folder IMAGES under D:\hosts\clientfolder and within the client web site folder create a virtual directory called images linked to D:\hosts\clientfolder\images:<br />
<br />
== Configuring IIS for Windows 2008 ==<br />
<br />
==== Installing IIS ====<br />
<br />
First install IIS from Control Panel > Programs & Features > Turn Windows Features ON or OFF > Add Roles:<br />
<br />
[[image:iis1.jpg]]<br />
<br />
On the window that pops up click on next and you will get this screen, tick Web Server (IIS) - on the prompt click on Add Required Resources and then on Next:<br />
<br />
[[image:iis2.jpg]]<br />
<br />
On the next window, click on next until you get this window - tick ASP and ISAPI Extensions:<br />
<br />
[[image:iis3.jpg]]<br />
<br />
Click on Next and Finish<br />
<br />
==== Configuring IIS ====<br />
After successfully installing IIS, go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Internet Information Services (IIS) > Machine Name > Sites > Default Website:<br />
<br />
The first step is to create a virtual directory called neosys linked to D:\neosys\neosys.net:<br />
<br />
[[image:iis4.jpg]]<br />
<br />
Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data:<br />
<br />
[[image:iis5.jpg]]<br />
<br />
In the IIS Default Web Site create a another virtual directory called neosys.w3c linked to D:\neosys\neosys.w3c (only if timesheets for mac is required):<br />
<br />
[[image:iis6.jpg]]<br />
<br />
To allow file uploads – create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
[[image:iis7.jpg]]<br />
<br />
After you add all virtual directories the tree map of the Default Website should look as follows:<br />
<br />
[[image:iis8.jpg]]<br />
<br />
To configure file uploads besides adding the images directory, go under IIS > Default Website > neosys – click on Handler Mappings and delete the ISAPI you see there:<br />
<br />
[[image:iis9a.jpg]]<br />
<br />
Thereafter click on Add Script Map and fill in the details as follows – Request path: *.dll , Executable: D:\neosys\neosys.net\NEOSYS\dll\upload.dll , Name: ISAPI (once you click on OK click on YES to the confirmation box)<br />
<br />
[[image:iis9b.jpg]]<br />
<br />
Edit the hosts file under c:\windows\system32\drivers\etc\ - delete the # sign next to 127.0.0.1 localhost and incluide the # sign before ::1 localhost<br />
<br />
[[image:iis10.jpg]]</div>Sunnyhttps://techwiki.neosys.com/index.php?title=File:Figure_2.jpg&diff=709File:Figure 2.jpg2011-06-25T09:53:32Z<p>Sunny: </p>
<hr />
<div></div>Sunnyhttps://techwiki.neosys.com/index.php?title=Configuring_IIS&diff=708Configuring IIS2011-06-25T09:50:33Z<p>Sunny: </p>
<hr />
<div>After you have installed all the NEOSYS program files you need to configure IIS so that you can operate NEOSYS. Instructions are below.<br />
<br />
== Configuring IIS for windows 2003 ==<br />
<br />
'''Client Server:''' first step is to create a virtual directory called neosys liked to D:\neosys\neosys.net:<br />
<br />
'''NL1 Server:''' Create a website called "clientname" liked to D:\hosts\clientfolder\neosys.net <br />
<br />
In that folder > neosys > dll – change the Execute Permission to Scripts & Executables<br />
<br />
[[Image:Figure 3]] (not created as we need to do the installation)<br />
<br />
A new window will pop up "IP Address and Port Setting" after completion of the above step.<br />
<br />
'''Client Server:''' select *(All Unassigned)* from the drop down list of "Enter the IP address to use for the Web site" and keep the default port as 80. <br />
<br />
'''NL1 Server:''' Select the static Ip from the drop down list of "Enter the IP address to use for the Web site" and enter then next port available and click on next.<br />
<br />
'''Client Server:''' Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data: <br />
<br />
'''Nl1 Server:''' Within the above clientwebsite folder create a virtual directory called data linked to D:\hosts\clientfolder\data:<br />
<br />
(I haven’t got the screenshot because I can only get it once I create the above)<br />
<br />
To allow file uploads <br />
<br />
'''Client server:''' create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
'''Nl1 Server:''' create a folder IMAGES under D:\hosts\clientfolder and within the client web site folder create a virtual directory called images linked to D:\hosts\clientfolder\images:<br />
<br />
== Configuring IIS for Windows 2008 ==<br />
<br />
==== Installing IIS ====<br />
<br />
First install IIS from Control Panel > Programs & Features > Turn Windows Features ON or OFF > Add Roles:<br />
<br />
[[image:iis1.jpg]]<br />
<br />
On the window that pops up click on next and you will get this screen, tick Web Server (IIS) - on the prompt click on Add Required Resources and then on Next:<br />
<br />
[[image:iis2.jpg]]<br />
<br />
On the next window, click on next until you get this window - tick ASP and ISAPI Extensions:<br />
<br />
[[image:iis3.jpg]]<br />
<br />
Click on Next and Finish<br />
<br />
==== Configuring IIS ====<br />
After successfully installing IIS, go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Internet Information Services (IIS) > Machine Name > Sites > Default Website:<br />
<br />
The first step is to create a virtual directory called neosys linked to D:\neosys\neosys.net:<br />
<br />
[[image:iis4.jpg]]<br />
<br />
Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data:<br />
<br />
[[image:iis5.jpg]]<br />
<br />
In the IIS Default Web Site create a another virtual directory called neosys.w3c linked to D:\neosys\neosys.w3c (only if timesheets for mac is required):<br />
<br />
[[image:iis6.jpg]]<br />
<br />
To allow file uploads – create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
[[image:iis7.jpg]]<br />
<br />
After you add all virtual directories the tree map of the Default Website should look as follows:<br />
<br />
[[image:iis8.jpg]]<br />
<br />
To configure file uploads besides adding the images directory, go under IIS > Default Website > neosys – click on Handler Mappings and delete the ISAPI you see there:<br />
<br />
[[image:iis9a.jpg]]<br />
<br />
Thereafter click on Add Script Map and fill in the details as follows – Request path: *.dll , Executable: D:\neosys\neosys.net\NEOSYS\dll\upload.dll , Name: ISAPI (once you click on OK click on YES to the confirmation box)<br />
<br />
[[image:iis9b.jpg]]<br />
<br />
Edit the hosts file under c:\windows\system32\drivers\etc\ - delete the # sign next to 127.0.0.1 localhost and incluide the # sign before ::1 localhost<br />
<br />
[[image:iis10.jpg]]</div>Sunnyhttps://techwiki.neosys.com/index.php?title=File:Figure1.jpg&diff=707File:Figure1.jpg2011-06-25T09:46:49Z<p>Sunny: </p>
<hr />
<div></div>Sunnyhttps://techwiki.neosys.com/index.php?title=Configuring_IIS&diff=706Configuring IIS2011-06-25T09:45:52Z<p>Sunny: /* Configuring IIS for windows 2003 */</p>
<hr />
<div>After you have installed all the NEOSYS program files you need to configure IIS so that you can operate NEOSYS. Instructions are below.<br />
<br />
== Configuring IIS for windows 2003 ==<br />
<br />
'''Client Server:''' first step is to create a virtual directory called neosys liked to D:\neosys\neosys.net:<br />
<br />
'''NL1 Server:''' Create a website called "clientname" liked to D:\hosts\clientfolder\neosys.net <br />
<br />
[[Image:Figure1]]<br />
<br />
[[Image:Figure2]]<br />
<br />
In that folder > neosys > dll – change the Execute Permission to Scripts & Executables<br />
<br />
[[Image:Figure 3]] (not created as we need to do the installation)<br />
<br />
A new window will pop up "IP Address and Port Setting" after completion of the above step.<br />
<br />
'''Client Server:''' select *(All Unassigned)* from the drop down list of "Enter the IP address to use for the Web site" and keep the default port as 80. <br />
<br />
'''NL1 Server:''' Select the static Ip from the drop down list of "Enter the IP address to use for the Web site" and enter then next port available and click on next.<br />
<br />
[[Image:Figure4]]<br />
<br />
'''Client Server:''' Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data: <br />
<br />
'''Nl1 Server:''' Within the above clientwebsite folder create a virtual directory called data linked to D:\hosts\clientfolder\data:<br />
<br />
[[image:figure5]]<br />
<br />
(I haven’t got the screenshot because I can only get it once I create the above)<br />
<br />
To allow file uploads <br />
<br />
'''Client server:''' create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
'''Nl1 Server:''' create a folder IMAGES under D:\hosts\clientfolder and within the client web site folder create a virtual directory called images linked to D:\hosts\clientfolder\images:<br />
<br />
== Configuring IIS for Windows 2008 ==<br />
<br />
==== Installing IIS ====<br />
<br />
First install IIS from Control Panel > Programs & Features > Turn Windows Features ON or OFF > Add Roles:<br />
<br />
[[image:iis1.jpg]]<br />
<br />
On the window that pops up click on next and you will get this screen, tick Web Server (IIS) - on the prompt click on Add Required Resources and then on Next:<br />
<br />
[[image:iis2.jpg]]<br />
<br />
On the next window, click on next until you get this window - tick ASP and ISAPI Extensions:<br />
<br />
[[image:iis3.jpg]]<br />
<br />
Click on Next and Finish<br />
<br />
==== Configuring IIS ====<br />
After successfully installing IIS, go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Internet Information Services (IIS) > Machine Name > Sites > Default Website:<br />
<br />
The first step is to create a virtual directory called neosys linked to D:\neosys\neosys.net:<br />
<br />
[[image:iis4.jpg]]<br />
<br />
Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data:<br />
<br />
[[image:iis5.jpg]]<br />
<br />
In the IIS Default Web Site create a another virtual directory called neosys.w3c linked to D:\neosys\neosys.w3c (only if timesheets for mac is required):<br />
<br />
[[image:iis6.jpg]]<br />
<br />
To allow file uploads – create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
[[image:iis7.jpg]]<br />
<br />
After you add all virtual directories the tree map of the Default Website should look as follows:<br />
<br />
[[image:iis8.jpg]]<br />
<br />
To configure file uploads besides adding the images directory, go under IIS > Default Website > neosys – click on Handler Mappings and delete the ISAPI you see there:<br />
<br />
[[image:iis9a.jpg]]<br />
<br />
Thereafter click on Add Script Map and fill in the details as follows – Request path: *.dll , Executable: D:\neosys\neosys.net\NEOSYS\dll\upload.dll , Name: ISAPI (once you click on OK click on YES to the confirmation box)<br />
<br />
[[image:iis9b.jpg]]<br />
<br />
Edit the hosts file under c:\windows\system32\drivers\etc\ - delete the # sign next to 127.0.0.1 localhost and incluide the # sign before ::1 localhost<br />
<br />
[[image:iis10.jpg]]</div>Sunnyhttps://techwiki.neosys.com/index.php?title=File:Figure_1.jpg&diff=705File:Figure 1.jpg2011-06-25T09:43:22Z<p>Sunny: </p>
<hr />
<div></div>Sunnyhttps://techwiki.neosys.com/index.php?title=Configuring_IIS&diff=704Configuring IIS2011-06-25T09:38:47Z<p>Sunny: </p>
<hr />
<div>After you have installed all the NEOSYS program files you need to configure IIS so that you can operate NEOSYS. Instructions are below.<br />
<br />
== Configuring IIS for windows 2003 ==<br />
<br />
'''Client Server:''' first step is to create a virtual directory called neosys liked to D:\neosys\neosys.net:<br />
<br />
'''NL1 Server:''' Create a website called "clientname" liked to D:\hosts\clientfolder\neosys.net <br />
<br />
[[Image: Figure 1]]<br />
<br />
[[Image: Figure 2]]<br />
<br />
In that folder > neosys > dll – change the Execute Permission to Scripts & Executables<br />
<br />
[[Image:Figure 3]] (not created as we need to do the installation)<br />
<br />
A new window will pop up "IP Address and Port Setting" after completion of the above step.<br />
<br />
'''Client Server:''' select *(All Unassigned)* from the drop down list of "Enter the IP address to use for the Web site" and keep the default port as 80. <br />
<br />
'''NL1 Server:''' Select the static Ip from the drop down list of "Enter the IP address to use for the Web site" and enter then next port available and click on next.<br />
<br />
[[Image: Figure 4]]<br />
<br />
'''Client Server:''' Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data: <br />
<br />
'''Nl1 Server:''' Within the above clientwebsite folder create a virtual directory called data linked to D:\hosts\clientfolder\data:<br />
<br />
[[image: Figure 5]]<br />
<br />
(I haven’t got the screenshot because I can only get it once I create the above)<br />
<br />
To allow file uploads <br />
<br />
'''Client server:''' create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
'''Nl1 Server:''' create a folder IMAGES under D:\hosts\clientfolder and within the client web site folder create a virtual directory called images linked to D:\hosts\clientfolder\images:<br />
<br />
== Configuring IIS for Windows 2008 ==<br />
<br />
==== Installing IIS ====<br />
<br />
First install IIS from Control Panel > Programs & Features > Turn Windows Features ON or OFF > Add Roles:<br />
<br />
[[image:iis1.jpg]]<br />
<br />
On the window that pops up click on next and you will get this screen, tick Web Server (IIS) - on the prompt click on Add Required Resources and then on Next:<br />
<br />
[[image:iis2.jpg]]<br />
<br />
On the next window, click on next until you get this window - tick ASP and ISAPI Extensions:<br />
<br />
[[image:iis3.jpg]]<br />
<br />
Click on Next and Finish<br />
<br />
==== Configuring IIS ====<br />
After successfully installing IIS, go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Internet Information Services (IIS) > Machine Name > Sites > Default Website:<br />
<br />
The first step is to create a virtual directory called neosys linked to D:\neosys\neosys.net:<br />
<br />
[[image:iis4.jpg]]<br />
<br />
Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data:<br />
<br />
[[image:iis5.jpg]]<br />
<br />
In the IIS Default Web Site create a another virtual directory called neosys.w3c linked to D:\neosys\neosys.w3c (only if timesheets for mac is required):<br />
<br />
[[image:iis6.jpg]]<br />
<br />
To allow file uploads – create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
[[image:iis7.jpg]]<br />
<br />
After you add all virtual directories the tree map of the Default Website should look as follows:<br />
<br />
[[image:iis8.jpg]]<br />
<br />
To configure file uploads besides adding the images directory, go under IIS > Default Website > neosys – click on Handler Mappings and delete the ISAPI you see there:<br />
<br />
[[image:iis9a.jpg]]<br />
<br />
Thereafter click on Add Script Map and fill in the details as follows – Request path: *.dll , Executable: D:\neosys\neosys.net\NEOSYS\dll\upload.dll , Name: ISAPI (once you click on OK click on YES to the confirmation box)<br />
<br />
[[image:iis9b.jpg]]<br />
<br />
Edit the hosts file under c:\windows\system32\drivers\etc\ - delete the # sign next to 127.0.0.1 localhost and incluide the # sign before ::1 localhost<br />
<br />
[[image:iis10.jpg]]</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Configuring_IIS&diff=703Configuring IIS2011-06-23T17:05:28Z<p>Sunny: /* Configuring IIS */</p>
<hr />
<div>After you have installed all the NEOSYS program files you need to configure IIS so that you can operate NEOSYS. Instructions are below.<br />
<br />
== Configuring IIS for Windows 2008 ==<br />
<br />
==== Installing IIS ====<br />
<br />
First install IIS from Control Panel > Programs & Features > Turn Windows Features ON or OFF > Add Roles:<br />
<br />
[[image:iis1.jpg]]<br />
<br />
On the window that pops up click on next and you will get this screen, tick Web Server (IIS) - on the prompt click on Add Required Resources and then on Next:<br />
<br />
[[image:iis2.jpg]]<br />
<br />
On the next window, click on next until you get this window - tick ASP and ISAPI Extensions:<br />
<br />
[[image:iis3.jpg]]<br />
<br />
Click on Next and Finish<br />
<br />
==== Configuring IIS ====<br />
After successfully installing IIS, go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Internet Information Services (IIS) > Machine Name > Sites > Default Website:<br />
<br />
The first step is to create a virtual directory called neosys linked to D:\neosys\neosys.net:<br />
<br />
[[image:iis4.jpg]]<br />
<br />
Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data:<br />
<br />
[[image:iis5.jpg]]<br />
<br />
In the IIS Default Web Site create a another virtual directory called neosys.w3c linked to D:\neosys\neosys.w3c (only if timesheets for mac is required):<br />
<br />
[[image:iis6.jpg]]<br />
<br />
To allow file uploads – create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
[[image:iis7.jpg]]<br />
<br />
After you add all virtual directories the tree map of the Default Website should look as follows:<br />
<br />
[[image:iis8.jpg]]<br />
<br />
To configure file uploads besides adding the images directory, go under IIS > Default Website > neosys – click on Handler Mappings and delete the ISAPI you see there:<br />
<br />
[[image:iis9a.jpg]]<br />
<br />
Thereafter click on Add Script Map and fill in the details as follows – Request path: *.dll , Executable: D:\neosys\neosys.net\NEOSYS\dll\upload.dll , Name: ISAPI (once you click on OK click on YES to the confirmation box)<br />
<br />
[[image:iis9b.jpg]]<br />
<br />
Edit the hosts file under c:\windows\system32\drivers\etc\ - delete the # sign next to 127.0.0.1 localhost and incluide the # sign before ::1 localhost<br />
<br />
[[image:iis10.jpg]]</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Configuring_IIS&diff=702Configuring IIS2011-06-23T17:01:52Z<p>Sunny: /* Configuring IIS */</p>
<hr />
<div>After you have installed all the NEOSYS program files you need to configure IIS so that you can operate NEOSYS. Instructions are below.<br />
<br />
== Configuring IIS for Windows 2008 ==<br />
<br />
==== Installing IIS ====<br />
<br />
First install IIS from Control Panel > Programs & Features > Turn Windows Features ON or OFF > Add Roles:<br />
<br />
[[image:iis1.jpg]]<br />
<br />
On the window that pops up click on next and you will get this screen, tick Web Server (IIS) - on the prompt click on Add Required Resources and then on Next:<br />
<br />
[[image:iis2.jpg]]<br />
<br />
On the next window, click on next until you get this window - tick ASP and ISAPI Extensions:<br />
<br />
[[image:iis3.jpg]]<br />
<br />
Click on Next and Finish<br />
<br />
==== Configuring IIS ====<br />
After successfully installing IIS, go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Internet Information Services (IIS) > Machine Name > Sites > Default Website:<br />
<br />
===== Windows 2008 server =====<br />
The first step is to create a virtual directory called neosys linked to D:\neosys\neosys.net:<br />
<br />
[[image:iis4.jpg]]<br />
<br />
Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data:<br />
<br />
[[image:iis5.jpg]]<br />
<br />
In the IIS Default Web Site create a another virtual directory called neosys.w3c linked to D:\neosys\neosys.w3c (only if timesheets for mac is required):<br />
<br />
[[image:iis6.jpg]]<br />
<br />
To allow file uploads – create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
[[image:iis7.jpg]]<br />
<br />
After you add all virtual directories the tree map of the Default Website should look as follows:<br />
<br />
[[image:iis8.jpg]]<br />
<br />
To configure file uploads besides adding the images directory, go under IIS > Default Website > neosys – click on Handler Mappings and delete the ISAPI you see there:<br />
<br />
[[image:iis9a.jpg]]<br />
<br />
Thereafter click on Add Script Map and fill in the details as follows – Request path: *.dll , Executable: D:\neosys\neosys.net\NEOSYS\dll\upload.dll , Name: ISAPI (once you click on OK click on YES to the confirmation box)<br />
<br />
[[image:iis9b.jpg]]<br />
<br />
Edit the hosts file under c:\windows\system32\drivers\etc\ - delete the # sign next to 127.0.0.1 localhost and incluide the # sign before ::1 localhost<br />
<br />
[[image:iis10.jpg]]</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Configuring_IIS&diff=701Configuring IIS2011-06-23T16:56:59Z<p>Sunny: /* Windows 2003 server */</p>
<hr />
<div>After you have installed all the NEOSYS program files you need to configure IIS so that you can operate NEOSYS. Instructions are below.<br />
<br />
== Configuring IIS for Windows 2008 ==<br />
<br />
==== Installing IIS ====<br />
<br />
First install IIS from Control Panel > Programs & Features > Turn Windows Features ON or OFF > Add Roles:<br />
<br />
[[image:iis1.jpg]]<br />
<br />
On the window that pops up click on next and you will get this screen, tick Web Server (IIS) - on the prompt click on Add Required Resources and then on Next:<br />
<br />
[[image:iis2.jpg]]<br />
<br />
On the next window, click on next until you get this window - tick ASP and ISAPI Extensions:<br />
<br />
[[image:iis3.jpg]]<br />
<br />
Click on Next and Finish<br />
<br />
==== Configuring IIS ====<br />
After successfully installing IIS, go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Internet Information Services (IIS) > Machine Name > Sites > Default Website:<br />
<br />
===== Windows 2003 server =====<br />
<br />
'''Client Server:''' first step is to create a virtual directory called neosys liked to D:\neosys\neosys.net:<br />
<br />
'''NL1 Server:''' Create a website called "clientname" liked to D:\hosts\clientfolder\neosys.net <br />
<br />
[[Image: Figure 1]]<br />
<br />
[[Image: Figure 2]]<br />
<br />
In that folder > neosys > dll – change the Execute Permission to Scripts & Executables<br />
<br />
[[Image:Figure 3]] (not created as we need to do the installation)<br />
<br />
A new window will pop up "IP Address and Port Setting" after completion of the above step.<br />
<br />
'''Client Server:''' select *(All Unassigned)* from the drop down list of "Enter the IP address to use for the Web site" and keep the default port as 80. <br />
<br />
'''NL1 Server:''' Select the static Ip from the drop down list of "Enter the IP address to use for the Web site" and enter then next port available and click on next.<br />
<br />
[[Image: Figure 4]]<br />
<br />
'''Client Server:''' Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data: <br />
<br />
'''Nl1 Server:''' Within the above clientwebsite folder create a virtual directory called data linked to D:\hosts\clientfolder\data:<br />
<br />
[[image: Figure 5]]<br />
<br />
(I haven’t got the screenshot because I can only get it once I create the above)<br />
<br />
To allow file uploads <br />
<br />
'''Client server:''' create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
'''Nl1 Server:''' create a folder IMAGES under D:\hosts\clientfolder and within the client web site folder create a virtual directory called images linked to D:\hosts\clientfolder\images:<br />
<br />
===== Windows 2008 server =====<br />
The first step is to create a virtual directory called neosys linked to D:\neosys\neosys.net:<br />
<br />
[[image:iis4.jpg]]<br />
<br />
Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data:<br />
<br />
[[image:iis5.jpg]]<br />
<br />
In the IIS Default Web Site create a another virtual directory called neosys.w3c linked to D:\neosys\neosys.w3c (only if timesheets for mac is required):<br />
<br />
[[image:iis6.jpg]]<br />
<br />
To allow file uploads – create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
[[image:iis7.jpg]]<br />
<br />
After you add all virtual directories the tree map of the Default Website should look as follows:<br />
<br />
[[image:iis8.jpg]]<br />
<br />
To configure file uploads besides adding the images directory, go under IIS > Default Website > neosys – click on Handler Mappings and delete the ISAPI you see there:<br />
<br />
[[image:iis9a.jpg]]<br />
<br />
Thereafter click on Add Script Map and fill in the details as follows – Request path: *.dll , Executable: D:\neosys\neosys.net\NEOSYS\dll\upload.dll , Name: ISAPI (once you click on OK click on YES to the confirmation box)<br />
<br />
[[image:iis9b.jpg]]<br />
<br />
Edit the hosts file under c:\windows\system32\drivers\etc\ - delete the # sign next to 127.0.0.1 localhost and incluide the # sign before ::1 localhost<br />
<br />
[[image:iis10.jpg]]</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Configuring_IIS&diff=700Configuring IIS2011-06-23T16:56:02Z<p>Sunny: </p>
<hr />
<div>After you have installed all the NEOSYS program files you need to configure IIS so that you can operate NEOSYS. Instructions are below.<br />
<br />
== Configuring IIS for Windows 2008 ==<br />
<br />
==== Installing IIS ====<br />
<br />
First install IIS from Control Panel > Programs & Features > Turn Windows Features ON or OFF > Add Roles:<br />
<br />
[[image:iis1.jpg]]<br />
<br />
On the window that pops up click on next and you will get this screen, tick Web Server (IIS) - on the prompt click on Add Required Resources and then on Next:<br />
<br />
[[image:iis2.jpg]]<br />
<br />
On the next window, click on next until you get this window - tick ASP and ISAPI Extensions:<br />
<br />
[[image:iis3.jpg]]<br />
<br />
Click on Next and Finish<br />
<br />
==== Configuring IIS ====<br />
After successfully installing IIS, go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Internet Information Services (IIS) > Machine Name > Sites > Default Website:<br />
<br />
===== Windows 2003 server =====<br />
<br />
'''Client Server:''' first step is to create a virtual directory called neosys liked to D:\neosys\neosys.net:<br />
<br />
'''NL1 Server:''' Create a website called "clientname" liked to D:\hosts\clientfolder\neosys.net <br />
<br />
[[Image: Figure 1]]<br />
<br />
[[Image: Figure 2]]<br />
<br />
In that folder > neosys > dll – change the Execute Permission to Scripts & Executables<br />
<br />
[[Image:Figure 3]] (not created as we need to do the installation)<br />
<br />
A new window will pop up "IP Address and Port Setting" after completion of the above step.<br />
<br />
'''Client Server:''' select *(All Unassigned)* from the drop down list of "Enter the IP address to use for the Web site" and keep the default port as 80. <br />
<br />
'''NL1 Server:''' Select the static Ip from the drop down list of "Enter the IP address to use for the Web site" and enter then next port available and click on next.<br />
<br />
[[Image: Figure 4]]<br />
<br />
'''Client Server:''' Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data: <br />
<br />
'''Nl1 Server:''' Within the above clientwebsite folder create a virtual directory called data linked to D:\hosts\clientfolder\data:<br />
<br />
[[image: Figure 5]]<br />
<br />
(I haven’t got the screenshot because I can only get it once I create the above)<br />
<br />
To allow file uploads <br />
'''Client server:''' create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
'''Nl1 Server:''' create a folder IMAGES under D:\hosts\clientfolder and within the client web site folder create a virtual directory called images linked to D:\hosts\clientfolder\images:<br />
<br />
===== Windows 2008 server =====<br />
The first step is to create a virtual directory called neosys linked to D:\neosys\neosys.net:<br />
<br />
[[image:iis4.jpg]]<br />
<br />
Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data:<br />
<br />
[[image:iis5.jpg]]<br />
<br />
In the IIS Default Web Site create a another virtual directory called neosys.w3c linked to D:\neosys\neosys.w3c (only if timesheets for mac is required):<br />
<br />
[[image:iis6.jpg]]<br />
<br />
To allow file uploads – create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
[[image:iis7.jpg]]<br />
<br />
After you add all virtual directories the tree map of the Default Website should look as follows:<br />
<br />
[[image:iis8.jpg]]<br />
<br />
To configure file uploads besides adding the images directory, go under IIS > Default Website > neosys – click on Handler Mappings and delete the ISAPI you see there:<br />
<br />
[[image:iis9a.jpg]]<br />
<br />
Thereafter click on Add Script Map and fill in the details as follows – Request path: *.dll , Executable: D:\neosys\neosys.net\NEOSYS\dll\upload.dll , Name: ISAPI (once you click on OK click on YES to the confirmation box)<br />
<br />
[[image:iis9b.jpg]]<br />
<br />
Edit the hosts file under c:\windows\system32\drivers\etc\ - delete the # sign next to 127.0.0.1 localhost and incluide the # sign before ::1 localhost<br />
<br />
[[image:iis10.jpg]]</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Installing_NEOSYS_Service&diff=696Installing NEOSYS Service2011-06-23T14:22:57Z<p>Sunny: /* Installing initial Database */</p>
<hr />
<div>= INSTALLING NEOSYS SERVICE =<br />
<br />
Reference to X:\ in the notes below denotes the actual drive letter and needs to be replaced (eg D:\)<br />
<br />
== Main installation: ==<br />
<br />
Make sure NOT TO COPY an existing NEOSYS installation to another location and ONLY do a <br />
completely new install with a fresh database, because copying a folder will copy a variety of <br />
hidden configurations. <br />
<br />
=== Installing NEOSYS on partitions ===<br />
Good server management practice is to have separate partitions for operating system (C:) and data partitions (D:)<br />
<br />
In the case of operating system reinstallation (which causes the loss of the C: partition) if NEOSYS programs and data were installed on D: can be preserved. If there is only one partition then NEOSYS programs and data will have to be backed up and restored.<br />
<br />
==== Multiple Partitions ====<br />
NEOSYS should be installed on a different partition rather than the C drive for reasons already explained above (eg. D drive)<br />
<br />
==== Single Partition ====<br />
If there is only one partition then you have to inform the client to take the effort to reinstall the operating system or using third party repartitioning tools to create separate partitions.<br />
<br />
=== Downloading and running installation files ===<br />
# http://www.neosys.com/support/neosys.exe ... and unzip/install to X:\neosys (or to X:\hosts\clientcd for multi-installation on one server)<br />
# http://www.neosys.com/support/neosys2.exe ... and install same as previous step.<br />
<br />
=== Creating shortcuts ===<br />
In x:\neosys (or x:\hosts\clientcd), make a shortcut called ‘Maintenance’ and link it to<br />
<br />
x:\neosys\neosys\adagency.bat (for Adagency install)<br />
<br />
or <br />
<br />
x:\neosys\neosys\accounts.bat (for Accounts install)<br />
<br />
=== Activating NEOSYS using authorization number ===<br />
<br />
Start NEOSYS Maintenance, select Initial Backup and it will give a “Computer Number” and ask for an “Authorisation No”<br />
<br />
Send the computer number to NEOSYS admin to get the authorization no.<br />
<br />
If you cannot get the authorization number immediately then you can close NEOSYS and when you reopen NEOSYS it will still give the same computer number and accept the same authorization number.<br />
<br />
=== Installing initial Database ===<br />
<br />
Download the initial database file from http://www.neosys.com/support/BACKUP.ZIP and place it in D drive (or any other drive) - but make sure that this file exists in the root folder i.e. D:\BACKUP.ZIP<br />
<br />
Follow the steps below:<br />
#Click on the Maintenance icon.<br />
#Select BASIC DATA SET and type in the NEOSYS username and password. (If the system does not prompt for a username and password,then go to Quit > Quit to next user and type the same in. If you do not enter with a username and password then NEOSYS will not allow you to restore the database). The first time when you enter maintenance you will get a command box (like when you do F5). If you do not get a command box, hit the F5 key and get it on the screen and hit ESC after you get it. <br />
#Now restore the BACKUP.ZIP (STARTUP DATABASE), to do so go to General > Backup & Data Management, select (the 4th option) Restore from disk or diskette. select D drive (or whichever drive you put the backup.zip file in) and follow the prompts ahead.<br />
#On every successful restore or creation of dataset, system will give you a message to swithh to new database always '''say NO''' to this,because the switch to database option brings you back to the BASIC DATA SET. Hence press the ESC button, type EXIT on the F5 prompt.<br />
#Now startup maintenance again and you will find a new database "STARTUP DATABASE" select it and login with NEOSYS username and password. Once you enter you may find a prompt "TASK ADDED" follow the prompt and continue.<br />
#After you have logged in, go to General > Backup & Data Management > Delete a dataset and select the "BASIC DATASET" to delete, to confirm the delete system will ask you to enter the dataset code. Enter the code and delete the basis dataset.<br />
#Now create a new dataset for the client, go to general > Backup & Data management> Create a new dataset, select (6th option) and follow the instruction on how to setup database code from the following link "http://techwiki.neosys.com/index.php/Installing_NEOSYS_Service#Assigning_database_codes"<br />
#Once the client dataset is created,login to the clientdataset and follow the steps in above point6 and delete the STARTUP DATABASE. (while logging in to the client dataset, it ask " This database hsa been copied or the database name or code has been changed. Is this going to be a unique new master database?" select first option YES - Going to be a new independent database.<br />
#To check the list of dataset on the computer, go to go to General > Backup & Data Management > See a list of dataset in the computer(8th option).<br />
<br />
Note:<br />
#Sometimes it may tell you that you cannot use FILEMAN as you are logged in as MASTER. Hence you need to hit the ESC key, go to General > Backup & Data Management > Restore from disk or diskette, select C drive or whichever drive you put the backup.zip file in and follow the prompts ahead.<br />
#While doing the step no.2 if you get a message as below just hit enter or space and continue.<br />
<br />
[[File:Message while installing.jpg]]<br />
<br />
==== Assigning database codes ====<br />
It is necessary to make sure that the following guidelines are met while creating database codes:<br />
<br />
#The code should be within 8 letters<br />
#The client should be as recognisable as possible from the main database code<br />
#The test database code should end with the TEST word and it is not necessary that it must be recognisable<br />
#The test database code should always appear after the main database code at login<br />
<br />
Examples of wrong and right database codes:<br />
<br />
ALTO VISTA ADVERTISING<br />
ALTOVIST and XALTTEST - right AVISTA and AVTEST - wrong (AVISTA not "as recognisable as possible")<br />
<br />
CONTEXTURE ASSOCIATES<br />
CONTEXT and XCONTEST - right CONTEXT and CONTEST - wrong (CONTEST alphabetically first in the login screen database drop down)<br />
<br />
=== Creating a .CMD file to start NEOSYS Service: ===<br />
(Note: change x to the correct drive you have installed NEOSYS on)<br />
<br />
In x:\neosys create a file start MAIN-DATABASE-CODE.cmd (eg start ALTOVIST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>databasecode</b><br />
<br />
(where <b>databasecode</b> is the code of the database)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
In x:\neosys create a file start TEST-DATABASE-CODE.cmd (eg start AVTEST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>testdatabasecode</b><br />
<br />
(where <b>testdatabasecode</b> is the code of the testdatabase)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
TEST THAT THE FILES YOU HAVE CREATED CAN RUN SUCCESSFULLY<br />
<br />
ENSURE THAT YOU DO NOT CLOSE THE PROCESS WINDOWS BY USING THE X BUTTON. HIT ESC 3 TIMES ON EACH WINDOW.<br />
<br />
=== Differences for Pure Accounts Module Only Installations ===<br />
Accounts module only has a slightly different startup command. In the above, replace '''/system adagency''' with '''/system accounts''' to startup a service and use '''accounts.bat''' instead of '''adagency.bat''' to start up maintenance. Other than that, accounts module setup is identical. Pure accounts clients are very few and tend not to upgrade often so care needs to be taken when upgrading. Upgrade is perhaps surprisingly done using the adagency.exe file.<br />
<br />
=== Creating a .CMD file to copy maindata to testdata ===<br />
<br />
In x:\neosys create a file <B>copy MAINDATABASECODE to TESTDABASECODE.cmd</b><br />
<br />
xcopy x:\neosys\data\<i>maindatabasecode</i> x:\neosys\data\<i>testdatabasecode</i> /s /y<br />
<br />
eg. xcopy c:\neosys\data\<i>ALTOVIST</i> x:\neosys\data\<i>AVTEST</i> /s /y<br />
<br />
Run this file to test that it works fine.<br />
<br />
=== Setting up daily scheduled tasks ===<br />
<b>Automatic Schedules:</b><br />
NEOSYS automatically shuts down at 1am (was 2am) every morning for backup. It closes all the running processes and backups up to the selected drive.<br />
<br />
<b>Manually Configured Schedules:</b> to be done under Scheduled Tasks<br />
<br />
Note: Under Windows 2008 Standard you need to UNTICK highest privileges and UNTICK run whether user is logged in or not as shown in the screen shots that follow:<br />
<br />
1. Create a task to start one Main database process at 6:00 am daily.<br />
<br />
[[File:start1.jpg]]<br><br><br><br />
[[File:start2.jpg]]<br><br><br><br />
[[File:start3.jpg]]<br><br><br><br />
<br />
2. Create a second task to Copy Maindata to Testdata at 2:45 am daily.<br />
<br />
[[File:copy1.jpg]]<br><br><br><br />
[[File:copy2.jpg]]<br><br><br><br />
[[File:copy3.jpg]]<br><br><br><br />
<br />
<br />
(For multiple sites on the same computer put the second site starting five minutes later at 6:05am, third site starting five minutes earlier at 5:55am, the third site starting five minutes later at 6:10am and so on.)<br />
<br />
Once created, test them to see that they are working correctly by running them directly using right click- Run.<br />
<br />
[[File:task1.jpg]]<br><br><br><br />
<br />
(Use web access and go to Support Menu, System Configuration File to request 3 processes for main database and 1 for test database).<br />
<br />
Please note that test running “copy test data” should be avoided while users are online but there is no problem testing the “daily 6am startup task” at any time since it will just add an additional process.<br />
<br />
=== Configuring NEOSYS to start automatically on server start-up / reboot ===<br />
We no longer configure NEOSYS processes to start on reboot as we would like to know of the failures at the client side and hence whenever the server reboots we expect the client to inform us and we will start the process - or NEOSYS will start automatically next day at 6 am<br />
<br />
Unfortunately using this method the NEOSYS processes are not visible when you login as a user. <br />
<br />
[[Image:win_sch_task.jpg]]<br />
<br />
Schedule a task to run the main database file whenever the computer starts. In Windows 2008 you need to tick the options - Run whether user logged in or not and Run with highest privilege.<br />
<br />
Additional in Windows 2008: Tick Highest Priviledges and Run whether user logged in or not<br />
<br />
== Installing and upgrading NEOSYS pure accounting systems ==<br />
<br />
Basic installation using NEOSYS.EXE and upgrades using NEOSYS2.EXE are identical to the normal adagency installation process.<br />
<br />
Differences are as follows:<br />
<br />
# Maintenance shortcut to ACCOUNTS.BAT<br />
# Process startup file contains "/system ACCOUNTS" instead of "/system ADAGENCY"<br />
# Internet address is http://server/neosys/accounts.htm although it auto converts to http://server/neosys/default.htm??ACCOUNTS. Although not to be relied upon, the login page stores a cookie so even plain http://server/neosys or http://server/neosys/default.htm works thereafter until the cookie is lost. To get back to adagency login you use http://server/neosys/default.htm??ADAGENCY<br />
# BACKUP.ZIP files created by ADAGENCY systems and ACCOUNTS systems are slightly incompatible with the result that restoring one in the other type of system will not work. NEOSYS programmers can convert from one type to the other but it is almost never required since any ad agency that only requires accounts only module is given the adagency version of NEOSYS and accounting only clients becoming ad agencies never happened.</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Installing_NEOSYS_Service&diff=695Installing NEOSYS Service2011-06-23T14:12:48Z<p>Sunny: /* Installing initial Database */</p>
<hr />
<div>= INSTALLING NEOSYS SERVICE =<br />
<br />
Reference to X:\ in the notes below denotes the actual drive letter and needs to be replaced (eg D:\)<br />
<br />
== Main installation: ==<br />
<br />
Make sure NOT TO COPY an existing NEOSYS installation to another location and ONLY do a <br />
completely new install with a fresh database, because copying a folder will copy a variety of <br />
hidden configurations. <br />
<br />
=== Installing NEOSYS on partitions ===<br />
Good server management practice is to have separate partitions for operating system (C:) and data partitions (D:)<br />
<br />
In the case of operating system reinstallation (which causes the loss of the C: partition) if NEOSYS programs and data were installed on D: can be preserved. If there is only one partition then NEOSYS programs and data will have to be backed up and restored.<br />
<br />
==== Multiple Partitions ====<br />
NEOSYS should be installed on a different partition rather than the C drive for reasons already explained above (eg. D drive)<br />
<br />
==== Single Partition ====<br />
If there is only one partition then you have to inform the client to take the effort to reinstall the operating system or using third party repartitioning tools to create separate partitions.<br />
<br />
=== Downloading and running installation files ===<br />
# http://www.neosys.com/support/neosys.exe ... and unzip/install to X:\neosys (or to X:\hosts\clientcd for multi-installation on one server)<br />
# http://www.neosys.com/support/neosys2.exe ... and install same as previous step.<br />
<br />
=== Creating shortcuts ===<br />
In x:\neosys (or x:\hosts\clientcd), make a shortcut called ‘Maintenance’ and link it to<br />
<br />
x:\neosys\neosys\adagency.bat (for Adagency install)<br />
<br />
or <br />
<br />
x:\neosys\neosys\accounts.bat (for Accounts install)<br />
<br />
=== Activating NEOSYS using authorization number ===<br />
<br />
Start NEOSYS Maintenance, select Initial Backup and it will give a “Computer Number” and ask for an “Authorisation No”<br />
<br />
Send the computer number to NEOSYS admin to get the authorization no.<br />
<br />
If you cannot get the authorization number immediately then you can close NEOSYS and when you reopen NEOSYS it will still give the same computer number and accept the same authorization number.<br />
<br />
=== Installing initial Database ===<br />
<br />
Download the initial database file from http://www.neosys.com/support/BACKUP.ZIP and place it in D drive (or any other drive) - but make sure that this file exists in the root folder i.e. D:\BACKUP.ZIP<br />
<br />
Follow the steps below:<br />
#Click on the Maintenance icon.<br />
#Select BASIC DATA SET and type in the NEOSYS username and password. (If the system does not prompt for a username and password,then go to Quit > Quit to next user and type the same in. If you do not enter with a username and password then NEOSYS will not allow you to restore the database). The first time when you enter maintenance you will get a command box (like when you do F5). If you do not get a command box, hit the F5 key and get it on the screen and hit ESC after you get it. <br />
#Now restore the BACKUP.ZIP (STARTUP DATABASE), to do so go to General > Backup & Data Management, select (the 4th option) Restore from disk or diskette. select D drive (or whichever drive you put the backup.zip file in) and follow the prompts ahead.<br />
#On every successful restore or creation of dataset, system will give you a message to swithh to new database always '''say NO''' to this,because the switch to database option brings you back to the BASIC DATA SET. Hence press the ESC button, type EXIT on the F5 prompt.<br />
#Now startup maintenance again and you will find a new database "STARTUP DATABASE" select it and login with NEOSYS username and password. Once you enter you may find a prompt "TASK ADDED" follow the prompt and continue.<br />
#After you have logged in, go to General > Backup & Data Management > Delete a dataset and select the "BASIC DATASET" to delete, to confirm the delete system will ask you to enter the dataset code. Enter the code and delete the basis dataset.<br />
#Now create a new dataset for the client, go to general > Backup & Data management> Create a new dataset, select (6th option) and follow the instruction on how to setup database code from the following link "http://techwiki.neosys.com/index.php/Installing_NEOSYS_Service#Assigning_database_codes"<br />
#Once the client dataset is created,login to the clientdataset and follow the steps in above point6 and delete the STARTUP DATABASE.<br />
#To check the list of dataset on the computer, go to go to General > Backup & Data Management > See a list of dataset in the computer(8th option).<br />
<br />
Note:<br />
#Sometimes it may tell you that you cannot use FILEMAN as you are logged in as MASTER. Hence you need to hit the ESC key, go to General > Backup & Data Management > Restore from disk or diskette, select C drive or whichever drive you put the backup.zip file in and follow the prompts ahead.<br />
#While doing the step no.2 if you get a message as below just hit enter or space and continue.<br />
<br />
[[File:Message while installing.jpg]]<br />
<br />
==== Assigning database codes ====<br />
It is necessary to make sure that the following guidelines are met while creating database codes:<br />
<br />
#The code should be within 8 letters<br />
#The client should be as recognisable as possible from the main database code<br />
#The test database code should end with the TEST word and it is not necessary that it must be recognisable<br />
#The test database code should always appear after the main database code at login<br />
<br />
Examples of wrong and right database codes:<br />
<br />
ALTO VISTA ADVERTISING<br />
ALTOVIST and XALTTEST - right AVISTA and AVTEST - wrong (AVISTA not "as recognisable as possible")<br />
<br />
CONTEXTURE ASSOCIATES<br />
CONTEXT and XCONTEST - right CONTEXT and CONTEST - wrong (CONTEST alphabetically first in the login screen database drop down)<br />
<br />
=== Creating a .CMD file to start NEOSYS Service: ===<br />
(Note: change x to the correct drive you have installed NEOSYS on)<br />
<br />
In x:\neosys create a file start MAIN-DATABASE-CODE.cmd (eg start ALTOVIST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>databasecode</b><br />
<br />
(where <b>databasecode</b> is the code of the database)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
In x:\neosys create a file start TEST-DATABASE-CODE.cmd (eg start AVTEST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>testdatabasecode</b><br />
<br />
(where <b>testdatabasecode</b> is the code of the testdatabase)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
TEST THAT THE FILES YOU HAVE CREATED CAN RUN SUCCESSFULLY<br />
<br />
ENSURE THAT YOU DO NOT CLOSE THE PROCESS WINDOWS BY USING THE X BUTTON. HIT ESC 3 TIMES ON EACH WINDOW.<br />
<br />
=== Differences for Pure Accounts Module Only Installations ===<br />
Accounts module only has a slightly different startup command. In the above, replace '''/system adagency''' with '''/system accounts''' to startup a service and use '''accounts.bat''' instead of '''adagency.bat''' to start up maintenance. Other than that, accounts module setup is identical. Pure accounts clients are very few and tend not to upgrade often so care needs to be taken when upgrading. Upgrade is perhaps surprisingly done using the adagency.exe file.<br />
<br />
=== Creating a .CMD file to copy maindata to testdata ===<br />
<br />
In x:\neosys create a file <B>copy MAINDATABASECODE to TESTDABASECODE.cmd</b><br />
<br />
xcopy x:\neosys\data\<i>maindatabasecode</i> x:\neosys\data\<i>testdatabasecode</i> /s /y<br />
<br />
eg. xcopy c:\neosys\data\<i>ALTOVIST</i> x:\neosys\data\<i>AVTEST</i> /s /y<br />
<br />
Run this file to test that it works fine.<br />
<br />
=== Setting up daily scheduled tasks ===<br />
<b>Automatic Schedules:</b><br />
NEOSYS automatically shuts down at 1am (was 2am) every morning for backup. It closes all the running processes and backups up to the selected drive.<br />
<br />
<b>Manually Configured Schedules:</b> to be done under Scheduled Tasks<br />
<br />
Note: Under Windows 2008 Standard you need to UNTICK highest privileges and UNTICK run whether user is logged in or not as shown in the screen shots that follow:<br />
<br />
1. Create a task to start one Main database process at 6:00 am daily.<br />
<br />
[[File:start1.jpg]]<br><br><br><br />
[[File:start2.jpg]]<br><br><br><br />
[[File:start3.jpg]]<br><br><br><br />
<br />
2. Create a second task to Copy Maindata to Testdata at 2:45 am daily.<br />
<br />
[[File:copy1.jpg]]<br><br><br><br />
[[File:copy2.jpg]]<br><br><br><br />
[[File:copy3.jpg]]<br><br><br><br />
<br />
<br />
(For multiple sites on the same computer put the second site starting five minutes later at 6:05am, third site starting five minutes earlier at 5:55am, the third site starting five minutes later at 6:10am and so on.)<br />
<br />
Once created, test them to see that they are working correctly by running them directly using right click- Run.<br />
<br />
[[File:task1.jpg]]<br><br><br><br />
<br />
(Use web access and go to Support Menu, System Configuration File to request 3 processes for main database and 1 for test database).<br />
<br />
Please note that test running “copy test data” should be avoided while users are online but there is no problem testing the “daily 6am startup task” at any time since it will just add an additional process.<br />
<br />
=== Configuring NEOSYS to start automatically on server start-up / reboot ===<br />
We no longer configure NEOSYS processes to start on reboot as we would like to know of the failures at the client side and hence whenever the server reboots we expect the client to inform us and we will start the process - or NEOSYS will start automatically next day at 6 am<br />
<br />
Unfortunately using this method the NEOSYS processes are not visible when you login as a user. <br />
<br />
[[Image:win_sch_task.jpg]]<br />
<br />
Schedule a task to run the main database file whenever the computer starts. In Windows 2008 you need to tick the options - Run whether user logged in or not and Run with highest privilege.<br />
<br />
Additional in Windows 2008: Tick Highest Priviledges and Run whether user logged in or not<br />
<br />
== Installing and upgrading NEOSYS pure accounting systems ==<br />
<br />
Basic installation using NEOSYS.EXE and upgrades using NEOSYS2.EXE are identical to the normal adagency installation process.<br />
<br />
Differences are as follows:<br />
<br />
# Maintenance shortcut to ACCOUNTS.BAT<br />
# Process startup file contains "/system ACCOUNTS" instead of "/system ADAGENCY"<br />
# Internet address is http://server/neosys/accounts.htm although it auto converts to http://server/neosys/default.htm??ACCOUNTS. Although not to be relied upon, the login page stores a cookie so even plain http://server/neosys or http://server/neosys/default.htm works thereafter until the cookie is lost. To get back to adagency login you use http://server/neosys/default.htm??ADAGENCY<br />
# BACKUP.ZIP files created by ADAGENCY systems and ACCOUNTS systems are slightly incompatible with the result that restoring one in the other type of system will not work. NEOSYS programmers can convert from one type to the other but it is almost never required since any ad agency that only requires accounts only module is given the adagency version of NEOSYS and accounting only clients becoming ad agencies never happened.</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Installing_NEOSYS_Service&diff=694Installing NEOSYS Service2011-06-23T14:02:13Z<p>Sunny: /* Installing initial Database */</p>
<hr />
<div>= INSTALLING NEOSYS SERVICE =<br />
<br />
Reference to X:\ in the notes below denotes the actual drive letter and needs to be replaced (eg D:\)<br />
<br />
== Main installation: ==<br />
<br />
Make sure NOT TO COPY an existing NEOSYS installation to another location and ONLY do a <br />
completely new install with a fresh database, because copying a folder will copy a variety of <br />
hidden configurations. <br />
<br />
=== Installing NEOSYS on partitions ===<br />
Good server management practice is to have separate partitions for operating system (C:) and data partitions (D:)<br />
<br />
In the case of operating system reinstallation (which causes the loss of the C: partition) if NEOSYS programs and data were installed on D: can be preserved. If there is only one partition then NEOSYS programs and data will have to be backed up and restored.<br />
<br />
==== Multiple Partitions ====<br />
NEOSYS should be installed on a different partition rather than the C drive for reasons already explained above (eg. D drive)<br />
<br />
==== Single Partition ====<br />
If there is only one partition then you have to inform the client to take the effort to reinstall the operating system or using third party repartitioning tools to create separate partitions.<br />
<br />
=== Downloading and running installation files ===<br />
# http://www.neosys.com/support/neosys.exe ... and unzip/install to X:\neosys (or to X:\hosts\clientcd for multi-installation on one server)<br />
# http://www.neosys.com/support/neosys2.exe ... and install same as previous step.<br />
<br />
=== Creating shortcuts ===<br />
In x:\neosys (or x:\hosts\clientcd), make a shortcut called ‘Maintenance’ and link it to<br />
<br />
x:\neosys\neosys\adagency.bat (for Adagency install)<br />
<br />
or <br />
<br />
x:\neosys\neosys\accounts.bat (for Accounts install)<br />
<br />
=== Activating NEOSYS using authorization number ===<br />
<br />
Start NEOSYS Maintenance, select Initial Backup and it will give a “Computer Number” and ask for an “Authorisation No”<br />
<br />
Send the computer number to NEOSYS admin to get the authorization no.<br />
<br />
If you cannot get the authorization number immediately then you can close NEOSYS and when you reopen NEOSYS it will still give the same computer number and accept the same authorization number.<br />
<br />
=== Installing initial Database ===<br />
<br />
Download the initial database file from http://www.neosys.com/support/BACKUP.ZIP and place it in D drive (or any other drive) - but make sure that this file exists in the root folder i.e. D:\BACKUP.ZIP<br />
<br />
Follow the steps below:<br />
#Click on the Maintenance icon.<br />
#Select BASIC DATA SET and type in the NEOSYS username and password. (If the system does not prompt for a username and password,then go to Quit > Quit to next user and type the same in. If you do not enter with a username and password then NEOSYS will not allow you to restore the database). The first time when you enter maintenance you will get a command box (like when you do F5). If you do not get a command box, hit the F5 key and get it on the screen and hit ESC after you get it. <br />
#Now restore the BACKUP.ZIP (STARTUP DATABASE), to do so go to General > Backup & Data Management, select (the 4th option) Restore from disk or diskette. select D drive (or whichever drive you put the backup.zip file in) and follow the prompts ahead.<br />
#After you have restored the BACKUP.ZIP file, it will ask you to switch to this database '''say NO''', because the switch to database option brings you back to the BASIC DATA SET. Hence press the ESC button, type EXIT on the F5 prompt.<br />
#Now startup maintenance again and you will find a new database "STARTUP DATABASE" select it and login with NEOSYS username and password. Once you enter you may find a prompt "TASK ADDED" follow the prompt and continue.<br />
#After you have logged in, go to General > Backup & Data Management > Delete a dataset and select the "BASIC DATASET" to delete, to confirm the delete system will ask you to enter the dataset code. Enter the code and delete the basis dataset.<br />
#Now create a new dataset for the client, go to general > Backup & Data management> Create a new dataset, select (6th option) and follow the instruction on how to setup database code from the following link "http://techwiki.neosys.com/index.php/Installing_NEOSYS_Service#Assigning_database_codes"<br />
#Once the client dataset is created,login to the clientdataset and follow the steps in above point6 and delete the STARTUP DATABASE.<br />
#To check the list of dataset on the computer, go to go to General > Backup & Data Management > See a list of dataset in the computer(8th option).<br />
<br />
Note:<br />
#Sometimes it may tell you that you cannot use FILEMAN as you are logged in as MASTER. Hence you need to hit the ESC key, go to General > Backup & Data Management > Restore from disk or diskette, select C drive or whichever drive you put the backup.zip file in and follow the prompts ahead.<br />
#While doing the step no.2 if you get a message as below just hit enter or space and continue.<br />
<br />
[[File:Message while installing.jpg]]<br />
<br />
==== Assigning database codes ====<br />
It is necessary to make sure that the following guidelines are met while creating database codes:<br />
<br />
#The code should be within 8 letters<br />
#The client should be as recognisable as possible from the main database code<br />
#The test database code should end with the TEST word and it is not necessary that it must be recognisable<br />
#The test database code should always appear after the main database code at login<br />
<br />
Examples of wrong and right database codes:<br />
<br />
ALTO VISTA ADVERTISING<br />
ALTOVIST and XALTTEST - right AVISTA and AVTEST - wrong (AVISTA not "as recognisable as possible")<br />
<br />
CONTEXTURE ASSOCIATES<br />
CONTEXT and XCONTEST - right CONTEXT and CONTEST - wrong (CONTEST alphabetically first in the login screen database drop down)<br />
<br />
=== Creating a .CMD file to start NEOSYS Service: ===<br />
(Note: change x to the correct drive you have installed NEOSYS on)<br />
<br />
In x:\neosys create a file start MAIN-DATABASE-CODE.cmd (eg start ALTOVIST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>databasecode</b><br />
<br />
(where <b>databasecode</b> is the code of the database)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
In x:\neosys create a file start TEST-DATABASE-CODE.cmd (eg start AVTEST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>testdatabasecode</b><br />
<br />
(where <b>testdatabasecode</b> is the code of the testdatabase)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
TEST THAT THE FILES YOU HAVE CREATED CAN RUN SUCCESSFULLY<br />
<br />
ENSURE THAT YOU DO NOT CLOSE THE PROCESS WINDOWS BY USING THE X BUTTON. HIT ESC 3 TIMES ON EACH WINDOW.<br />
<br />
=== Differences for Pure Accounts Module Only Installations ===<br />
Accounts module only has a slightly different startup command. In the above, replace '''/system adagency''' with '''/system accounts''' to startup a service and use '''accounts.bat''' instead of '''adagency.bat''' to start up maintenance. Other than that, accounts module setup is identical. Pure accounts clients are very few and tend not to upgrade often so care needs to be taken when upgrading. Upgrade is perhaps surprisingly done using the adagency.exe file.<br />
<br />
=== Creating a .CMD file to copy maindata to testdata ===<br />
<br />
In x:\neosys create a file <B>copy MAINDATABASECODE to TESTDABASECODE.cmd</b><br />
<br />
xcopy x:\neosys\data\<i>maindatabasecode</i> x:\neosys\data\<i>testdatabasecode</i> /s /y<br />
<br />
eg. xcopy c:\neosys\data\<i>ALTOVIST</i> x:\neosys\data\<i>AVTEST</i> /s /y<br />
<br />
Run this file to test that it works fine.<br />
<br />
=== Setting up daily scheduled tasks ===<br />
<b>Automatic Schedules:</b><br />
NEOSYS automatically shuts down at 1am (was 2am) every morning for backup. It closes all the running processes and backups up to the selected drive.<br />
<br />
<b>Manually Configured Schedules:</b> to be done under Scheduled Tasks<br />
<br />
Note: Under Windows 2008 Standard you need to UNTICK highest privileges and UNTICK run whether user is logged in or not as shown in the screen shots that follow:<br />
<br />
1. Create a task to start one Main database process at 6:00 am daily.<br />
<br />
[[File:start1.jpg]]<br><br><br><br />
[[File:start2.jpg]]<br><br><br><br />
[[File:start3.jpg]]<br><br><br><br />
<br />
2. Create a second task to Copy Maindata to Testdata at 2:45 am daily.<br />
<br />
[[File:copy1.jpg]]<br><br><br><br />
[[File:copy2.jpg]]<br><br><br><br />
[[File:copy3.jpg]]<br><br><br><br />
<br />
<br />
(For multiple sites on the same computer put the second site starting five minutes later at 6:05am, third site starting five minutes earlier at 5:55am, the third site starting five minutes later at 6:10am and so on.)<br />
<br />
Once created, test them to see that they are working correctly by running them directly using right click- Run.<br />
<br />
[[File:task1.jpg]]<br><br><br><br />
<br />
(Use web access and go to Support Menu, System Configuration File to request 3 processes for main database and 1 for test database).<br />
<br />
Please note that test running “copy test data” should be avoided while users are online but there is no problem testing the “daily 6am startup task” at any time since it will just add an additional process.<br />
<br />
=== Configuring NEOSYS to start automatically on server start-up / reboot ===<br />
We no longer configure NEOSYS processes to start on reboot as we would like to know of the failures at the client side and hence whenever the server reboots we expect the client to inform us and we will start the process - or NEOSYS will start automatically next day at 6 am<br />
<br />
Unfortunately using this method the NEOSYS processes are not visible when you login as a user. <br />
<br />
[[Image:win_sch_task.jpg]]<br />
<br />
Schedule a task to run the main database file whenever the computer starts. In Windows 2008 you need to tick the options - Run whether user logged in or not and Run with highest privilege.<br />
<br />
Additional in Windows 2008: Tick Highest Priviledges and Run whether user logged in or not<br />
<br />
== Installing and upgrading NEOSYS pure accounting systems ==<br />
<br />
Basic installation using NEOSYS.EXE and upgrades using NEOSYS2.EXE are identical to the normal adagency installation process.<br />
<br />
Differences are as follows:<br />
<br />
# Maintenance shortcut to ACCOUNTS.BAT<br />
# Process startup file contains "/system ACCOUNTS" instead of "/system ADAGENCY"<br />
# Internet address is http://server/neosys/accounts.htm although it auto converts to http://server/neosys/default.htm??ACCOUNTS. Although not to be relied upon, the login page stores a cookie so even plain http://server/neosys or http://server/neosys/default.htm works thereafter until the cookie is lost. To get back to adagency login you use http://server/neosys/default.htm??ADAGENCY<br />
# BACKUP.ZIP files created by ADAGENCY systems and ACCOUNTS systems are slightly incompatible with the result that restoring one in the other type of system will not work. NEOSYS programmers can convert from one type to the other but it is almost never required since any ad agency that only requires accounts only module is given the adagency version of NEOSYS and accounting only clients becoming ad agencies never happened.</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Installing_NEOSYS_Service&diff=693Installing NEOSYS Service2011-06-23T13:47:21Z<p>Sunny: /* Installing initial Database */</p>
<hr />
<div>= INSTALLING NEOSYS SERVICE =<br />
<br />
Reference to X:\ in the notes below denotes the actual drive letter and needs to be replaced (eg D:\)<br />
<br />
== Main installation: ==<br />
<br />
Make sure NOT TO COPY an existing NEOSYS installation to another location and ONLY do a <br />
completely new install with a fresh database, because copying a folder will copy a variety of <br />
hidden configurations. <br />
<br />
=== Installing NEOSYS on partitions ===<br />
Good server management practice is to have separate partitions for operating system (C:) and data partitions (D:)<br />
<br />
In the case of operating system reinstallation (which causes the loss of the C: partition) if NEOSYS programs and data were installed on D: can be preserved. If there is only one partition then NEOSYS programs and data will have to be backed up and restored.<br />
<br />
==== Multiple Partitions ====<br />
NEOSYS should be installed on a different partition rather than the C drive for reasons already explained above (eg. D drive)<br />
<br />
==== Single Partition ====<br />
If there is only one partition then you have to inform the client to take the effort to reinstall the operating system or using third party repartitioning tools to create separate partitions.<br />
<br />
=== Downloading and running installation files ===<br />
# http://www.neosys.com/support/neosys.exe ... and unzip/install to X:\neosys (or to X:\hosts\clientcd for multi-installation on one server)<br />
# http://www.neosys.com/support/neosys2.exe ... and install same as previous step.<br />
<br />
=== Creating shortcuts ===<br />
In x:\neosys (or x:\hosts\clientcd), make a shortcut called ‘Maintenance’ and link it to<br />
<br />
x:\neosys\neosys\adagency.bat (for Adagency install)<br />
<br />
or <br />
<br />
x:\neosys\neosys\accounts.bat (for Accounts install)<br />
<br />
=== Activating NEOSYS using authorization number ===<br />
<br />
Start NEOSYS Maintenance, select Initial Backup and it will give a “Computer Number” and ask for an “Authorisation No”<br />
<br />
Send the computer number to NEOSYS admin to get the authorization no.<br />
<br />
If you cannot get the authorization number immediately then you can close NEOSYS and when you reopen NEOSYS it will still give the same computer number and accept the same authorization number.<br />
<br />
=== Installing initial Database ===<br />
<br />
Download the initial database file from http://www.neosys.com/support/BACKUP.ZIP and place it in D drive (or any other drive) - but make sure that this file exists in the root folder i.e. D:\BACKUP.ZIP<br />
<br />
Follow the steps below:<br />
#Click on the Maintenance icon.<br />
#Select BASIC DATA SET and type in the NEOSYS username and password. (If the system does not prompt for a username and password,then go to Quit > Quit to next user and type the same in. If you do not enter with a username and password then NEOSYS will not allow you to restore the database). The first time when you enter maintenance you will get a command box (like when you do F5). If you do not get a command box, hit the F5 key and get it on the screen and hit ESC after you get it. <br />
#Now restore the BACKUP.ZIP (STARTUP DATABASE), to do so go to General > Backup & Data Management, select (the 4th option) Restore from disk or diskette. select D drive (or whichever drive you put the backup.zip file in) and follow the prompts ahead.<br />
#After you have restored the BACKUP.ZIP file, it will ask you to switch to this database '''say NO''', because the switch to database option brings you back to the BASIC DATA SET. Hence press the ESC button, type EXIT on the F5 prompt.<br />
#Now startup maintenance again and you will find a new database "STARTUP DATABASE" select it and login with NEOSYS username and password.<br />
#After you have logged in, go to General > Backup & Data Management > Delete a dataset and select the "BASIC DATASET" to delete, to confirm the delete system will ask you to enter the dataset code. Enter the code and delete the basis dataset.<br />
#Now create a new dataset for the client, go to general > Backup & Data management> Create a new dataset, select (6th option) and follow the instruction on how to setup database code from the following link "http://techwiki.neosys.com/index.php/Installing_NEOSYS_Service#Assigning_database_codes"<br />
#Once the client dataset is created,login to the clientdataset and follow the steps in above point6 and delete the STARTUP DATABASE.<br />
#To check the list of dataset on the computer, go to go to General > Backup & Data Management > See a list of dataset in the computer(8th option).<br />
<br />
Note:<br />
#Sometimes it may tell you that you cannot use FILEMAN as you are logged in as MASTER. Hence you need to hit the ESC key, go to General > Backup & Data Management > Restore from disk or diskette, select C drive or whichever drive you put the backup.zip file in and follow the prompts ahead.<br />
#While doing the step no.2 if you get a message as below just hit enter or space and continue.<br />
<br />
[[File:Message while installing.jpg]]<br />
<br />
==== Assigning database codes ====<br />
It is necessary to make sure that the following guidelines are met while creating database codes:<br />
<br />
#The code should be within 8 letters<br />
#The client should be as recognisable as possible from the main database code<br />
#The test database code should end with the TEST word and it is not necessary that it must be recognisable<br />
#The test database code should always appear after the main database code at login<br />
<br />
Examples of wrong and right database codes:<br />
<br />
ALTO VISTA ADVERTISING<br />
ALTOVIST and XALTTEST - right AVISTA and AVTEST - wrong (AVISTA not "as recognisable as possible")<br />
<br />
CONTEXTURE ASSOCIATES<br />
CONTEXT and XCONTEST - right CONTEXT and CONTEST - wrong (CONTEST alphabetically first in the login screen database drop down)<br />
<br />
=== Creating a .CMD file to start NEOSYS Service: ===<br />
(Note: change x to the correct drive you have installed NEOSYS on)<br />
<br />
In x:\neosys create a file start MAIN-DATABASE-CODE.cmd (eg start ALTOVIST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>databasecode</b><br />
<br />
(where <b>databasecode</b> is the code of the database)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
In x:\neosys create a file start TEST-DATABASE-CODE.cmd (eg start AVTEST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>testdatabasecode</b><br />
<br />
(where <b>testdatabasecode</b> is the code of the testdatabase)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
TEST THAT THE FILES YOU HAVE CREATED CAN RUN SUCCESSFULLY<br />
<br />
ENSURE THAT YOU DO NOT CLOSE THE PROCESS WINDOWS BY USING THE X BUTTON. HIT ESC 3 TIMES ON EACH WINDOW.<br />
<br />
=== Differences for Pure Accounts Module Only Installations ===<br />
Accounts module only has a slightly different startup command. In the above, replace '''/system adagency''' with '''/system accounts''' to startup a service and use '''accounts.bat''' instead of '''adagency.bat''' to start up maintenance. Other than that, accounts module setup is identical. Pure accounts clients are very few and tend not to upgrade often so care needs to be taken when upgrading. Upgrade is perhaps surprisingly done using the adagency.exe file.<br />
<br />
=== Creating a .CMD file to copy maindata to testdata ===<br />
<br />
In x:\neosys create a file <B>copy MAINDATABASECODE to TESTDABASECODE.cmd</b><br />
<br />
xcopy x:\neosys\data\<i>maindatabasecode</i> x:\neosys\data\<i>testdatabasecode</i> /s /y<br />
<br />
eg. xcopy c:\neosys\data\<i>ALTOVIST</i> x:\neosys\data\<i>AVTEST</i> /s /y<br />
<br />
Run this file to test that it works fine.<br />
<br />
=== Setting up daily scheduled tasks ===<br />
<b>Automatic Schedules:</b><br />
NEOSYS automatically shuts down at 1am (was 2am) every morning for backup. It closes all the running processes and backups up to the selected drive.<br />
<br />
<b>Manually Configured Schedules:</b> to be done under Scheduled Tasks<br />
<br />
Note: Under Windows 2008 Standard you need to UNTICK highest privileges and UNTICK run whether user is logged in or not as shown in the screen shots that follow:<br />
<br />
1. Create a task to start one Main database process at 6:00 am daily.<br />
<br />
[[File:start1.jpg]]<br><br><br><br />
[[File:start2.jpg]]<br><br><br><br />
[[File:start3.jpg]]<br><br><br><br />
<br />
2. Create a second task to Copy Maindata to Testdata at 2:45 am daily.<br />
<br />
[[File:copy1.jpg]]<br><br><br><br />
[[File:copy2.jpg]]<br><br><br><br />
[[File:copy3.jpg]]<br><br><br><br />
<br />
<br />
(For multiple sites on the same computer put the second site starting five minutes later at 6:05am, third site starting five minutes earlier at 5:55am, the third site starting five minutes later at 6:10am and so on.)<br />
<br />
Once created, test them to see that they are working correctly by running them directly using right click- Run.<br />
<br />
[[File:task1.jpg]]<br><br><br><br />
<br />
(Use web access and go to Support Menu, System Configuration File to request 3 processes for main database and 1 for test database).<br />
<br />
Please note that test running “copy test data” should be avoided while users are online but there is no problem testing the “daily 6am startup task” at any time since it will just add an additional process.<br />
<br />
=== Configuring NEOSYS to start automatically on server start-up / reboot ===<br />
We no longer configure NEOSYS processes to start on reboot as we would like to know of the failures at the client side and hence whenever the server reboots we expect the client to inform us and we will start the process - or NEOSYS will start automatically next day at 6 am<br />
<br />
Unfortunately using this method the NEOSYS processes are not visible when you login as a user. <br />
<br />
[[Image:win_sch_task.jpg]]<br />
<br />
Schedule a task to run the main database file whenever the computer starts. In Windows 2008 you need to tick the options - Run whether user logged in or not and Run with highest privilege.<br />
<br />
Additional in Windows 2008: Tick Highest Priviledges and Run whether user logged in or not<br />
<br />
== Installing and upgrading NEOSYS pure accounting systems ==<br />
<br />
Basic installation using NEOSYS.EXE and upgrades using NEOSYS2.EXE are identical to the normal adagency installation process.<br />
<br />
Differences are as follows:<br />
<br />
# Maintenance shortcut to ACCOUNTS.BAT<br />
# Process startup file contains "/system ACCOUNTS" instead of "/system ADAGENCY"<br />
# Internet address is http://server/neosys/accounts.htm although it auto converts to http://server/neosys/default.htm??ACCOUNTS. Although not to be relied upon, the login page stores a cookie so even plain http://server/neosys or http://server/neosys/default.htm works thereafter until the cookie is lost. To get back to adagency login you use http://server/neosys/default.htm??ADAGENCY<br />
# BACKUP.ZIP files created by ADAGENCY systems and ACCOUNTS systems are slightly incompatible with the result that restoring one in the other type of system will not work. NEOSYS programmers can convert from one type to the other but it is almost never required since any ad agency that only requires accounts only module is given the adagency version of NEOSYS and accounting only clients becoming ad agencies never happened.</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Installing_NEOSYS_Service&diff=692Installing NEOSYS Service2011-06-23T13:46:55Z<p>Sunny: /* Installing initial Database */</p>
<hr />
<div>= INSTALLING NEOSYS SERVICE =<br />
<br />
Reference to X:\ in the notes below denotes the actual drive letter and needs to be replaced (eg D:\)<br />
<br />
== Main installation: ==<br />
<br />
Make sure NOT TO COPY an existing NEOSYS installation to another location and ONLY do a <br />
completely new install with a fresh database, because copying a folder will copy a variety of <br />
hidden configurations. <br />
<br />
=== Installing NEOSYS on partitions ===<br />
Good server management practice is to have separate partitions for operating system (C:) and data partitions (D:)<br />
<br />
In the case of operating system reinstallation (which causes the loss of the C: partition) if NEOSYS programs and data were installed on D: can be preserved. If there is only one partition then NEOSYS programs and data will have to be backed up and restored.<br />
<br />
==== Multiple Partitions ====<br />
NEOSYS should be installed on a different partition rather than the C drive for reasons already explained above (eg. D drive)<br />
<br />
==== Single Partition ====<br />
If there is only one partition then you have to inform the client to take the effort to reinstall the operating system or using third party repartitioning tools to create separate partitions.<br />
<br />
=== Downloading and running installation files ===<br />
# http://www.neosys.com/support/neosys.exe ... and unzip/install to X:\neosys (or to X:\hosts\clientcd for multi-installation on one server)<br />
# http://www.neosys.com/support/neosys2.exe ... and install same as previous step.<br />
<br />
=== Creating shortcuts ===<br />
In x:\neosys (or x:\hosts\clientcd), make a shortcut called ‘Maintenance’ and link it to<br />
<br />
x:\neosys\neosys\adagency.bat (for Adagency install)<br />
<br />
or <br />
<br />
x:\neosys\neosys\accounts.bat (for Accounts install)<br />
<br />
=== Activating NEOSYS using authorization number ===<br />
<br />
Start NEOSYS Maintenance, select Initial Backup and it will give a “Computer Number” and ask for an “Authorisation No”<br />
<br />
Send the computer number to NEOSYS admin to get the authorization no.<br />
<br />
If you cannot get the authorization number immediately then you can close NEOSYS and when you reopen NEOSYS it will still give the same computer number and accept the same authorization number.<br />
<br />
=== Installing initial Database ===<br />
<br />
Download the initial database file from http://www.neosys.com/support/BACKUP.ZIP and place it in D drive (or any other drive) - but make sure that this file exists in the root folder i.e. D:\BACKUP.ZIP<br />
<br />
Follow the steps below:<br />
#Click on the Maintenance icon.<br />
#Select BASIC DATA SET and type in the NEOSYS username and password. (If the system does not prompt for a username and password,then go to Quit > Quit to next user and type the same in. If you do not enter with a username and password then NEOSYS will not allow you to restore the database). The first time when you enter maintenance you will get a command box (like when you do F5). If you do not get a command box, hit the F5 key and get it on the screen and hit ESC after you get it. <br />
#Now restore the BACKUP.ZIP (STARTUP DATABASE), to do so go to General > Backup & Data Management, select (the 4th option) Restore from disk or diskette. select D drive (or whichever drive you put the backup.zip file in) and follow the prompts ahead.<br />
#After you have restored the BACKUP.ZIP file, it will ask you to switch to this database '''say NO''', because the switch to database option brings you back to the BASIC DATA SET. Hence press the ESC button, type EXIT on the F5 prompt.<br />
#Now startup maintenance again and you will find a new database "STARTUP DATABASE" select it and login with NEOSYS username and password.<br />
#After you have logged in, go to General > Backup & Data Management > Delete a dataset and select the "BASIC DATASET" to delete, to confirm the delete system will ask you to enter the dataset code. Enter the code and delete the basis dataset.<br />
#Now create a new dataset for the client, go to general > Backup & Data management> Create a new dataset, select (6th option) and follow the instruction on how to setup database code from the following link "http://techwiki.neosys.com/index.php/Installing_NEOSYS_Service#Assigning_database_codes"<br />
#Once the client dataset is created,login to the clientdataset and follow the steps in above point6 and delete the STARTUP DATABASE.<br />
#To check the list of dataset on the computer, go to go to General > Backup & Data Management > See a list of dataset in the computer(8th option).<br />
<br />
Note:<br />
#Sometimes it may tell you that you cannot use FILEMAN as you are logged in as MASTER. Hence you need to hit the ESC key, go to General > Backup & Data Management > Restore from disk or diskette, select C drive or whichever drive you put the backup.zip file in and follow the prompts ahead.<br />
#While doing the step no.2 if you get a message as below just hit enter or space and continue.<br />
<br />
[[File:Message while installing.jpg]]<br />
<br />
==== Assigning database codes ====<br />
It is necessary to make sure that the following guidelines are met while creating database codes:<br />
<br />
#The code should be within 8 letters<br />
#The client should be as recognisable as possible from the main database code<br />
#The test database code should end with the TEST word and it is not necessary that it must be recognisable<br />
#The test database code should always appear after the main database code at login<br />
<br />
Examples of wrong and right database codes:<br />
<br />
ALTO VISTA ADVERTISING<br />
ALTOVIST and XALTTEST - right AVISTA and AVTEST - wrong (AVISTA not "as recognisable as possible")<br />
<br />
CONTEXTURE ASSOCIATES<br />
CONTEXT and XCONTEST - right CONTEXT and CONTEST - wrong (CONTEST alphabetically first in the login screen database drop down)<br />
<br />
=== Creating a .CMD file to start NEOSYS Service: ===<br />
(Note: change x to the correct drive you have installed NEOSYS on)<br />
<br />
In x:\neosys create a file start MAIN-DATABASE-CODE.cmd (eg start ALTOVIST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>databasecode</b><br />
<br />
(where <b>databasecode</b> is the code of the database)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
In x:\neosys create a file start TEST-DATABASE-CODE.cmd (eg start AVTEST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>testdatabasecode</b><br />
<br />
(where <b>testdatabasecode</b> is the code of the testdatabase)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
TEST THAT THE FILES YOU HAVE CREATED CAN RUN SUCCESSFULLY<br />
<br />
ENSURE THAT YOU DO NOT CLOSE THE PROCESS WINDOWS BY USING THE X BUTTON. HIT ESC 3 TIMES ON EACH WINDOW.<br />
<br />
=== Differences for Pure Accounts Module Only Installations ===<br />
Accounts module only has a slightly different startup command. In the above, replace '''/system adagency''' with '''/system accounts''' to startup a service and use '''accounts.bat''' instead of '''adagency.bat''' to start up maintenance. Other than that, accounts module setup is identical. Pure accounts clients are very few and tend not to upgrade often so care needs to be taken when upgrading. Upgrade is perhaps surprisingly done using the adagency.exe file.<br />
<br />
=== Creating a .CMD file to copy maindata to testdata ===<br />
<br />
In x:\neosys create a file <B>copy MAINDATABASECODE to TESTDABASECODE.cmd</b><br />
<br />
xcopy x:\neosys\data\<i>maindatabasecode</i> x:\neosys\data\<i>testdatabasecode</i> /s /y<br />
<br />
eg. xcopy c:\neosys\data\<i>ALTOVIST</i> x:\neosys\data\<i>AVTEST</i> /s /y<br />
<br />
Run this file to test that it works fine.<br />
<br />
=== Setting up daily scheduled tasks ===<br />
<b>Automatic Schedules:</b><br />
NEOSYS automatically shuts down at 1am (was 2am) every morning for backup. It closes all the running processes and backups up to the selected drive.<br />
<br />
<b>Manually Configured Schedules:</b> to be done under Scheduled Tasks<br />
<br />
Note: Under Windows 2008 Standard you need to UNTICK highest privileges and UNTICK run whether user is logged in or not as shown in the screen shots that follow:<br />
<br />
1. Create a task to start one Main database process at 6:00 am daily.<br />
<br />
[[File:start1.jpg]]<br><br><br><br />
[[File:start2.jpg]]<br><br><br><br />
[[File:start3.jpg]]<br><br><br><br />
<br />
2. Create a second task to Copy Maindata to Testdata at 2:45 am daily.<br />
<br />
[[File:copy1.jpg]]<br><br><br><br />
[[File:copy2.jpg]]<br><br><br><br />
[[File:copy3.jpg]]<br><br><br><br />
<br />
<br />
(For multiple sites on the same computer put the second site starting five minutes later at 6:05am, third site starting five minutes earlier at 5:55am, the third site starting five minutes later at 6:10am and so on.)<br />
<br />
Once created, test them to see that they are working correctly by running them directly using right click- Run.<br />
<br />
[[File:task1.jpg]]<br><br><br><br />
<br />
(Use web access and go to Support Menu, System Configuration File to request 3 processes for main database and 1 for test database).<br />
<br />
Please note that test running “copy test data” should be avoided while users are online but there is no problem testing the “daily 6am startup task” at any time since it will just add an additional process.<br />
<br />
=== Configuring NEOSYS to start automatically on server start-up / reboot ===<br />
We no longer configure NEOSYS processes to start on reboot as we would like to know of the failures at the client side and hence whenever the server reboots we expect the client to inform us and we will start the process - or NEOSYS will start automatically next day at 6 am<br />
<br />
Unfortunately using this method the NEOSYS processes are not visible when you login as a user. <br />
<br />
[[Image:win_sch_task.jpg]]<br />
<br />
Schedule a task to run the main database file whenever the computer starts. In Windows 2008 you need to tick the options - Run whether user logged in or not and Run with highest privilege.<br />
<br />
Additional in Windows 2008: Tick Highest Priviledges and Run whether user logged in or not<br />
<br />
== Installing and upgrading NEOSYS pure accounting systems ==<br />
<br />
Basic installation using NEOSYS.EXE and upgrades using NEOSYS2.EXE are identical to the normal adagency installation process.<br />
<br />
Differences are as follows:<br />
<br />
# Maintenance shortcut to ACCOUNTS.BAT<br />
# Process startup file contains "/system ACCOUNTS" instead of "/system ADAGENCY"<br />
# Internet address is http://server/neosys/accounts.htm although it auto converts to http://server/neosys/default.htm??ACCOUNTS. Although not to be relied upon, the login page stores a cookie so even plain http://server/neosys or http://server/neosys/default.htm works thereafter until the cookie is lost. To get back to adagency login you use http://server/neosys/default.htm??ADAGENCY<br />
# BACKUP.ZIP files created by ADAGENCY systems and ACCOUNTS systems are slightly incompatible with the result that restoring one in the other type of system will not work. NEOSYS programmers can convert from one type to the other but it is almost never required since any ad agency that only requires accounts only module is given the adagency version of NEOSYS and accounting only clients becoming ad agencies never happened.</div>Sunnyhttps://techwiki.neosys.com/index.php?title=File:Message_while_installing.jpg&diff=691File:Message while installing.jpg2011-06-23T13:45:09Z<p>Sunny: </p>
<hr />
<div></div>Sunnyhttps://techwiki.neosys.com/index.php?title=Installing_NEOSYS_Service&diff=690Installing NEOSYS Service2011-06-23T13:08:19Z<p>Sunny: /* Installing initial Database */</p>
<hr />
<div>= INSTALLING NEOSYS SERVICE =<br />
<br />
Reference to X:\ in the notes below denotes the actual drive letter and needs to be replaced (eg D:\)<br />
<br />
== Main installation: ==<br />
<br />
Make sure NOT TO COPY an existing NEOSYS installation to another location and ONLY do a <br />
completely new install with a fresh database, because copying a folder will copy a variety of <br />
hidden configurations. <br />
<br />
=== Installing NEOSYS on partitions ===<br />
Good server management practice is to have separate partitions for operating system (C:) and data partitions (D:)<br />
<br />
In the case of operating system reinstallation (which causes the loss of the C: partition) if NEOSYS programs and data were installed on D: can be preserved. If there is only one partition then NEOSYS programs and data will have to be backed up and restored.<br />
<br />
==== Multiple Partitions ====<br />
NEOSYS should be installed on a different partition rather than the C drive for reasons already explained above (eg. D drive)<br />
<br />
==== Single Partition ====<br />
If there is only one partition then you have to inform the client to take the effort to reinstall the operating system or using third party repartitioning tools to create separate partitions.<br />
<br />
=== Downloading and running installation files ===<br />
# http://www.neosys.com/support/neosys.exe ... and unzip/install to X:\neosys (or to X:\hosts\clientcd for multi-installation on one server)<br />
# http://www.neosys.com/support/neosys2.exe ... and install same as previous step.<br />
<br />
=== Creating shortcuts ===<br />
In x:\neosys (or x:\hosts\clientcd), make a shortcut called ‘Maintenance’ and link it to<br />
<br />
x:\neosys\neosys\adagency.bat (for Adagency install)<br />
<br />
or <br />
<br />
x:\neosys\neosys\accounts.bat (for Accounts install)<br />
<br />
=== Activating NEOSYS using authorization number ===<br />
<br />
Start NEOSYS Maintenance, select Initial Backup and it will give a “Computer Number” and ask for an “Authorisation No”<br />
<br />
Send the computer number to NEOSYS admin to get the authorization no.<br />
<br />
If you cannot get the authorization number immediately then you can close NEOSYS and when you reopen NEOSYS it will still give the same computer number and accept the same authorization number.<br />
<br />
=== Installing initial Database ===<br />
<br />
Download the initial database file from http://www.neosys.com/support/BACKUP.ZIP and place it in D drive (or any other drive) - but make sure that this file exists in the root folder i.e. D:\BACKUP.ZIP<br />
<br />
Follow the steps below:<br />
#Click on the Maintenance icon.<br />
#Select BASIC DATA SET and type in the NEOSYS username and password. (If the system does not prompt for a username and password,then go to Quit > Quit to next user and type the same in. If you do not enter with a username and password then NEOSYS will not allow you to restore the database). The first time when you enter maintenance you will get a command box (like when you do F5). If you do not get a command box, hit the F5 key and get it on the screen and hit ESC after you get it. <br />
#Now restore the BACKUP.ZIP (STARTUP DATABASE), to do so go to General > Backup & Data Management, select (the 4th option) Restore from disk or diskette. select D drive (or whichever drive you put the backup.zip file in) and follow the prompts ahead.<br />
#After you have restored the BACKUP.ZIP file, it will ask you to switch to this database '''say NO''', because the switch to database option brings you back to the BASIC DATA SET. Hence press the ESC button, type EXIT on the F5 prompt.<br />
#Now startup maintenance again and you will find a new database "STARTUP DATABASE" select it and login with NEOSYS username and password.<br />
#After you have logged in, go to General > Backup & Data Management > Delete a dataset and select the "BASIC DATASET" to delete, to confirm the delete system will ask you to enter the dataset code. Enter the code and delete the basis dataset.<br />
#Now create a new dataset for the client, go to general > Backup & Data management> Create a new dataset, select (6th option) and follow the instruction on how to setup database code from the following link "http://techwiki.neosys.com/index.php/Installing_NEOSYS_Service#Assigning_database_codes"<br />
#Once the client dataset is created,login to the clientdataset and follow the steps in above point6 and delete the STARTUP DATABASE.<br />
#To check the list of dataset on the computer, go to go to General > Backup & Data Management > See a list of dataset in the computer(8th option).<br />
<br />
Note:Sometimes it may tell you that you cannot use FILEMAN as you are logged in as MASTER. Hence you need to hit the ESC key, go to General > Backup & Data Management > Restore from disk or diskette, select C drive (or whichever drive you put the backup.zip file in) and follow the prompts ahead.<br />
<br />
<br />
==== Assigning database codes ====<br />
It is necessary to make sure that the following guidelines are met while creating database codes:<br />
<br />
#The code should be within 8 letters<br />
#The client should be as recognisable as possible from the main database code<br />
#The test database code should end with the TEST word and it is not necessary that it must be recognisable<br />
#The test database code should always appear after the main database code at login<br />
<br />
Examples of wrong and right database codes:<br />
<br />
ALTO VISTA ADVERTISING<br />
ALTOVIST and XALTTEST - right AVISTA and AVTEST - wrong (AVISTA not "as recognisable as possible")<br />
<br />
CONTEXTURE ASSOCIATES<br />
CONTEXT and XCONTEST - right CONTEXT and CONTEST - wrong (CONTEST alphabetically first in the login screen database drop down)<br />
<br />
=== Creating a .CMD file to start NEOSYS Service: ===<br />
(Note: change x to the correct drive you have installed NEOSYS on)<br />
<br />
In x:\neosys create a file start MAIN-DATABASE-CODE.cmd (eg start ALTOVIST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>databasecode</b><br />
<br />
(where <b>databasecode</b> is the code of the database)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
In x:\neosys create a file start TEST-DATABASE-CODE.cmd (eg start AVTEST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>testdatabasecode</b><br />
<br />
(where <b>testdatabasecode</b> is the code of the testdatabase)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
TEST THAT THE FILES YOU HAVE CREATED CAN RUN SUCCESSFULLY<br />
<br />
ENSURE THAT YOU DO NOT CLOSE THE PROCESS WINDOWS BY USING THE X BUTTON. HIT ESC 3 TIMES ON EACH WINDOW.<br />
<br />
=== Differences for Pure Accounts Module Only Installations ===<br />
Accounts module only has a slightly different startup command. In the above, replace '''/system adagency''' with '''/system accounts''' to startup a service and use '''accounts.bat''' instead of '''adagency.bat''' to start up maintenance. Other than that, accounts module setup is identical. Pure accounts clients are very few and tend not to upgrade often so care needs to be taken when upgrading. Upgrade is perhaps surprisingly done using the adagency.exe file.<br />
<br />
=== Creating a .CMD file to copy maindata to testdata ===<br />
<br />
In x:\neosys create a file <B>copy MAINDATABASECODE to TESTDABASECODE.cmd</b><br />
<br />
xcopy x:\neosys\data\<i>maindatabasecode</i> x:\neosys\data\<i>testdatabasecode</i> /s /y<br />
<br />
eg. xcopy c:\neosys\data\<i>ALTOVIST</i> x:\neosys\data\<i>AVTEST</i> /s /y<br />
<br />
Run this file to test that it works fine.<br />
<br />
=== Setting up daily scheduled tasks ===<br />
<b>Automatic Schedules:</b><br />
NEOSYS automatically shuts down at 1am (was 2am) every morning for backup. It closes all the running processes and backups up to the selected drive.<br />
<br />
<b>Manually Configured Schedules:</b> to be done under Scheduled Tasks<br />
<br />
Note: Under Windows 2008 Standard you need to UNTICK highest privileges and UNTICK run whether user is logged in or not as shown in the screen shots that follow:<br />
<br />
1. Create a task to start one Main database process at 6:00 am daily.<br />
<br />
[[File:start1.jpg]]<br><br><br><br />
[[File:start2.jpg]]<br><br><br><br />
[[File:start3.jpg]]<br><br><br><br />
<br />
2. Create a second task to Copy Maindata to Testdata at 2:45 am daily.<br />
<br />
[[File:copy1.jpg]]<br><br><br><br />
[[File:copy2.jpg]]<br><br><br><br />
[[File:copy3.jpg]]<br><br><br><br />
<br />
<br />
(For multiple sites on the same computer put the second site starting five minutes later at 6:05am, third site starting five minutes earlier at 5:55am, the third site starting five minutes later at 6:10am and so on.)<br />
<br />
Once created, test them to see that they are working correctly by running them directly using right click- Run.<br />
<br />
[[File:task1.jpg]]<br><br><br><br />
<br />
(Use web access and go to Support Menu, System Configuration File to request 3 processes for main database and 1 for test database).<br />
<br />
Please note that test running “copy test data” should be avoided while users are online but there is no problem testing the “daily 6am startup task” at any time since it will just add an additional process.<br />
<br />
=== Configuring NEOSYS to start automatically on server start-up / reboot ===<br />
We no longer configure NEOSYS processes to start on reboot as we would like to know of the failures at the client side and hence whenever the server reboots we expect the client to inform us and we will start the process - or NEOSYS will start automatically next day at 6 am<br />
<br />
Unfortunately using this method the NEOSYS processes are not visible when you login as a user. <br />
<br />
[[Image:win_sch_task.jpg]]<br />
<br />
Schedule a task to run the main database file whenever the computer starts. In Windows 2008 you need to tick the options - Run whether user logged in or not and Run with highest privilege.<br />
<br />
Additional in Windows 2008: Tick Highest Priviledges and Run whether user logged in or not<br />
<br />
== Installing and upgrading NEOSYS pure accounting systems ==<br />
<br />
Basic installation using NEOSYS.EXE and upgrades using NEOSYS2.EXE are identical to the normal adagency installation process.<br />
<br />
Differences are as follows:<br />
<br />
# Maintenance shortcut to ACCOUNTS.BAT<br />
# Process startup file contains "/system ACCOUNTS" instead of "/system ADAGENCY"<br />
# Internet address is http://server/neosys/accounts.htm although it auto converts to http://server/neosys/default.htm??ACCOUNTS. Although not to be relied upon, the login page stores a cookie so even plain http://server/neosys or http://server/neosys/default.htm works thereafter until the cookie is lost. To get back to adagency login you use http://server/neosys/default.htm??ADAGENCY<br />
# BACKUP.ZIP files created by ADAGENCY systems and ACCOUNTS systems are slightly incompatible with the result that restoring one in the other type of system will not work. NEOSYS programmers can convert from one type to the other but it is almost never required since any ad agency that only requires accounts only module is given the adagency version of NEOSYS and accounting only clients becoming ad agencies never happened.</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Installing_NEOSYS_Service&diff=689Installing NEOSYS Service2011-06-23T12:38:09Z<p>Sunny: /* Installing initial Database */</p>
<hr />
<div>= INSTALLING NEOSYS SERVICE =<br />
<br />
Reference to X:\ in the notes below denotes the actual drive letter and needs to be replaced (eg D:\)<br />
<br />
== Main installation: ==<br />
<br />
Make sure NOT TO COPY an existing NEOSYS installation to another location and ONLY do a <br />
completely new install with a fresh database, because copying a folder will copy a variety of <br />
hidden configurations. <br />
<br />
=== Installing NEOSYS on partitions ===<br />
Good server management practice is to have separate partitions for operating system (C:) and data partitions (D:)<br />
<br />
In the case of operating system reinstallation (which causes the loss of the C: partition) if NEOSYS programs and data were installed on D: can be preserved. If there is only one partition then NEOSYS programs and data will have to be backed up and restored.<br />
<br />
==== Multiple Partitions ====<br />
NEOSYS should be installed on a different partition rather than the C drive for reasons already explained above (eg. D drive)<br />
<br />
==== Single Partition ====<br />
If there is only one partition then you have to inform the client to take the effort to reinstall the operating system or using third party repartitioning tools to create separate partitions.<br />
<br />
=== Downloading and running installation files ===<br />
# http://www.neosys.com/support/neosys.exe ... and unzip/install to X:\neosys (or to X:\hosts\clientcd for multi-installation on one server)<br />
# http://www.neosys.com/support/neosys2.exe ... and install same as previous step.<br />
<br />
=== Creating shortcuts ===<br />
In x:\neosys (or x:\hosts\clientcd), make a shortcut called ‘Maintenance’ and link it to<br />
<br />
x:\neosys\neosys\adagency.bat (for Adagency install)<br />
<br />
or <br />
<br />
x:\neosys\neosys\accounts.bat (for Accounts install)<br />
<br />
=== Activating NEOSYS using authorization number ===<br />
<br />
Start NEOSYS Maintenance, select Initial Backup and it will give a “Computer Number” and ask for an “Authorisation No”<br />
<br />
Send the computer number to NEOSYS admin to get the authorization no.<br />
<br />
If you cannot get the authorization number immediately then you can close NEOSYS and when you reopen NEOSYS it will still give the same computer number and accept the same authorization number.<br />
<br />
=== Installing initial Database ===<br />
<br />
Download the initial database file from http://www.neosys.com/support/BACKUP.ZIP and place it in D drive (or any other drive) - but make sure that this file exists in the root folder i.e. D:\BACKUP.ZIP<br />
<br />
Follow the steps below:<br />
#Click on the Maintenance icon.<br />
#Select BASIC DATA SET and type in the NEOSYS username and password. (If the system does not prompt for a username and password,then go to Quit > Quit to next user and type the same in. If you do not enter with a username and password then NEOSYS will not allow you to restore the database). The first time when you enter maintenance you will get a command box (like when you do F5). If you do not get a command box, hit the F5 key and get it on the screen and hit ESC after you get it. <br />
#Now restore the BACKUP.ZIP (STARTUP DATABSE), to do so go to General > Backup & Data Management, select (the 4th option) Restore from disk or diskette. select D drive (or whichever drive you put the backup.zip file in) and follow the prompts ahead.<br />
#After you have restored the BACKUP.ZIP file, it will ask you to switch to this database '''say NO''', because the switch to database option brings you back to the BASIC DATA SET. Hence press the ESC button, type EXIT on the F5 prompt <br />
#Now startup maintenance again and this time select the STARTUP DATABASE. After you have logged in, go to General > Backup & Data Management > Delete a data set and delete the BASIC DATA SET.<br />
<br />
Note:<br />
Sometimes it may tell you that you cannot use FILEMAN as you are logged in as MASTER. Hence you need to hit the ESC key, go to General > Backup & Data Management > Restore from disk or diskette, select C drive (or whichever drive you put the backup.zip file in) and follow the prompts ahead.<br />
<br />
<br />
==== Assigning database codes ====<br />
It is necessary to make sure that the following guidelines are met while creating database codes:<br />
<br />
#The code should be within 8 letters<br />
#The client should be as recognisable as possible from the main database code<br />
#The test database code should end with the TEST word and it is not necessary that it must be recognisable<br />
#The test database code should always appear after the main database code at login<br />
<br />
Examples of wrong and right database codes:<br />
<br />
ALTO VISTA ADVERTISING<br />
ALTOVIST and XALTTEST - right AVISTA and AVTEST - wrong (AVISTA not "as recognisable as possible")<br />
<br />
CONTEXTURE ASSOCIATES<br />
CONTEXT and XCONTEST - right CONTEXT and CONTEST - wrong (CONTEST alphabetically first in the login screen database drop down)<br />
<br />
=== Creating a .CMD file to start NEOSYS Service: ===<br />
(Note: change x to the correct drive you have installed NEOSYS on)<br />
<br />
In x:\neosys create a file start MAIN-DATABASE-CODE.cmd (eg start ALTOVIST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>databasecode</b><br />
<br />
(where <b>databasecode</b> is the code of the database)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
In x:\neosys create a file start TEST-DATABASE-CODE.cmd (eg start AVTEST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>testdatabasecode</b><br />
<br />
(where <b>testdatabasecode</b> is the code of the testdatabase)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
TEST THAT THE FILES YOU HAVE CREATED CAN RUN SUCCESSFULLY<br />
<br />
ENSURE THAT YOU DO NOT CLOSE THE PROCESS WINDOWS BY USING THE X BUTTON. HIT ESC 3 TIMES ON EACH WINDOW.<br />
<br />
=== Differences for Pure Accounts Module Only Installations ===<br />
Accounts module only has a slightly different startup command. In the above, replace '''/system adagency''' with '''/system accounts''' to startup a service and use '''accounts.bat''' instead of '''adagency.bat''' to start up maintenance. Other than that, accounts module setup is identical. Pure accounts clients are very few and tend not to upgrade often so care needs to be taken when upgrading. Upgrade is perhaps surprisingly done using the adagency.exe file.<br />
<br />
=== Creating a .CMD file to copy maindata to testdata ===<br />
<br />
In x:\neosys create a file <B>copy MAINDATABASECODE to TESTDABASECODE.cmd</b><br />
<br />
xcopy x:\neosys\data\<i>maindatabasecode</i> x:\neosys\data\<i>testdatabasecode</i> /s /y<br />
<br />
eg. xcopy c:\neosys\data\<i>ALTOVIST</i> x:\neosys\data\<i>AVTEST</i> /s /y<br />
<br />
Run this file to test that it works fine.<br />
<br />
=== Setting up daily scheduled tasks ===<br />
<b>Automatic Schedules:</b><br />
NEOSYS automatically shuts down at 1am (was 2am) every morning for backup. It closes all the running processes and backups up to the selected drive.<br />
<br />
<b>Manually Configured Schedules:</b> to be done under Scheduled Tasks<br />
<br />
Note: Under Windows 2008 Standard you need to UNTICK highest privileges and UNTICK run whether user is logged in or not as shown in the screen shots that follow:<br />
<br />
1. Create a task to start one Main database process at 6:00 am daily.<br />
<br />
[[File:start1.jpg]]<br><br><br><br />
[[File:start2.jpg]]<br><br><br><br />
[[File:start3.jpg]]<br><br><br><br />
<br />
2. Create a second task to Copy Maindata to Testdata at 2:45 am daily.<br />
<br />
[[File:copy1.jpg]]<br><br><br><br />
[[File:copy2.jpg]]<br><br><br><br />
[[File:copy3.jpg]]<br><br><br><br />
<br />
<br />
(For multiple sites on the same computer put the second site starting five minutes later at 6:05am, third site starting five minutes earlier at 5:55am, the third site starting five minutes later at 6:10am and so on.)<br />
<br />
Once created, test them to see that they are working correctly by running them directly using right click- Run.<br />
<br />
[[File:task1.jpg]]<br><br><br><br />
<br />
(Use web access and go to Support Menu, System Configuration File to request 3 processes for main database and 1 for test database).<br />
<br />
Please note that test running “copy test data” should be avoided while users are online but there is no problem testing the “daily 6am startup task” at any time since it will just add an additional process.<br />
<br />
=== Configuring NEOSYS to start automatically on server start-up / reboot ===<br />
We no longer configure NEOSYS processes to start on reboot as we would like to know of the failures at the client side and hence whenever the server reboots we expect the client to inform us and we will start the process - or NEOSYS will start automatically next day at 6 am<br />
<br />
Unfortunately using this method the NEOSYS processes are not visible when you login as a user. <br />
<br />
[[Image:win_sch_task.jpg]]<br />
<br />
Schedule a task to run the main database file whenever the computer starts. In Windows 2008 you need to tick the options - Run whether user logged in or not and Run with highest privilege.<br />
<br />
Additional in Windows 2008: Tick Highest Priviledges and Run whether user logged in or not<br />
<br />
== Installing and upgrading NEOSYS pure accounting systems ==<br />
<br />
Basic installation using NEOSYS.EXE and upgrades using NEOSYS2.EXE are identical to the normal adagency installation process.<br />
<br />
Differences are as follows:<br />
<br />
# Maintenance shortcut to ACCOUNTS.BAT<br />
# Process startup file contains "/system ACCOUNTS" instead of "/system ADAGENCY"<br />
# Internet address is http://server/neosys/accounts.htm although it auto converts to http://server/neosys/default.htm??ACCOUNTS. Although not to be relied upon, the login page stores a cookie so even plain http://server/neosys or http://server/neosys/default.htm works thereafter until the cookie is lost. To get back to adagency login you use http://server/neosys/default.htm??ADAGENCY<br />
# BACKUP.ZIP files created by ADAGENCY systems and ACCOUNTS systems are slightly incompatible with the result that restoring one in the other type of system will not work. NEOSYS programmers can convert from one type to the other but it is almost never required since any ad agency that only requires accounts only module is given the adagency version of NEOSYS and accounting only clients becoming ad agencies never happened.</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Installing_NEOSYS_Service&diff=688Installing NEOSYS Service2011-06-23T12:09:16Z<p>Sunny: /* Installing initial Database */</p>
<hr />
<div>= INSTALLING NEOSYS SERVICE =<br />
<br />
Reference to X:\ in the notes below denotes the actual drive letter and needs to be replaced (eg D:\)<br />
<br />
== Main installation: ==<br />
<br />
Make sure NOT TO COPY an existing NEOSYS installation to another location and ONLY do a <br />
completely new install with a fresh database, because copying a folder will copy a variety of <br />
hidden configurations. <br />
<br />
=== Installing NEOSYS on partitions ===<br />
Good server management practice is to have separate partitions for operating system (C:) and data partitions (D:)<br />
<br />
In the case of operating system reinstallation (which causes the loss of the C: partition) if NEOSYS programs and data were installed on D: can be preserved. If there is only one partition then NEOSYS programs and data will have to be backed up and restored.<br />
<br />
==== Multiple Partitions ====<br />
NEOSYS should be installed on a different partition rather than the C drive for reasons already explained above (eg. D drive)<br />
<br />
==== Single Partition ====<br />
If there is only one partition then you have to inform the client to take the effort to reinstall the operating system or using third party repartitioning tools to create separate partitions.<br />
<br />
=== Downloading and running installation files ===<br />
# http://www.neosys.com/support/neosys.exe ... and unzip/install to X:\neosys (or to X:\hosts\clientcd for multi-installation on one server)<br />
# http://www.neosys.com/support/neosys2.exe ... and install same as previous step.<br />
<br />
=== Creating shortcuts ===<br />
In x:\neosys (or x:\hosts\clientcd), make a shortcut called ‘Maintenance’ and link it to<br />
<br />
x:\neosys\neosys\adagency.bat (for Adagency install)<br />
<br />
or <br />
<br />
x:\neosys\neosys\accounts.bat (for Accounts install)<br />
<br />
=== Activating NEOSYS using authorization number ===<br />
<br />
Start NEOSYS Maintenance, select Initial Backup and it will give a “Computer Number” and ask for an “Authorisation No”<br />
<br />
Send the computer number to NEOSYS admin to get the authorization no.<br />
<br />
If you cannot get the authorization number immediately then you can close NEOSYS and when you reopen NEOSYS it will still give the same computer number and accept the same authorization number.<br />
<br />
=== Installing initial Database ===<br />
<br />
Download the initial database file from http://www.neosys.com/support/BACKUP.ZIP and place it in D drive (or any other drive) - but make sure that this file exists in the root folder i.e. D:\BACKUP.ZIP<br />
<br />
Follow the steps below:<br />
#Click on the Maintenance icon.<br />
#Select BASIC DATA SET and type in the admin username and password. (If the system does not prompt for a username and password,then go to Quit > Quit to next user and type the same in)<br />
#If you do not enter with a username and password then NEOSYS will not allow you to restore the database. <br />
#The first time when you enter maintenance you will get a command box (like when you do F5). If you do not get a command box, hit the F5 key to get one<br />
#Go to General > Backup & Data Management, select Restore from disk or diskette (which is no 4), select D drive (or whichever drive you put the backup.zip file in) and follow the prompts ahead.<br />
#After you have restored the BACKUP.ZIP file, it will ask you to switch to this database, say NO (because the switch to database option here brings you back to the BASIC DATA SET. Hence press the ESC button, type EXIT on the F5 prompt)<br />
#Now startup maintenance again and this time select the STARTUP DATABASE. After you have logged in, go to General > Backup & Data Management > Delete a data set and delete the BASIC DATA SET.<br />
<br />
Note:<br />
Sometimes it may tell you that you cannot use FILEMAN as you are logged in as MASTER. Hence you need to hit the ESC key, go to General > Backup & Data Management > Restore from disk or diskette, select C drive (or whichever drive you put the backup.zip file in) and follow the prompts ahead.<br />
<br />
<br />
==== Assigning database codes ====<br />
It is necessary to make sure that the following guidelines are met while creating database codes:<br />
<br />
#The code should be within 8 letters<br />
#The client should be as recognisable as possible from the main database code<br />
#The test database code should end with the TEST word and it is not necessary that it must be recognisable<br />
#The test database code should always appear after the main database code at login<br />
<br />
Examples of wrong and right database codes:<br />
<br />
ALTO VISTA ADVERTISING<br />
ALTOVIST and XALTTEST - right AVISTA and AVTEST - wrong (AVISTA not "as recognisable as possible")<br />
<br />
CONTEXTURE ASSOCIATES<br />
CONTEXT and XCONTEST - right CONTEXT and CONTEST - wrong (CONTEST alphabetically first in the login screen database drop down)<br />
<br />
=== Creating a .CMD file to start NEOSYS Service: ===<br />
(Note: change x to the correct drive you have installed NEOSYS on)<br />
<br />
In x:\neosys create a file start MAIN-DATABASE-CODE.cmd (eg start ALTOVIST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>databasecode</b><br />
<br />
(where <b>databasecode</b> is the code of the database)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
In x:\neosys create a file start TEST-DATABASE-CODE.cmd (eg start AVTEST.cmd)<br />
<br />
x:<br />
cd \neosys\neosys<br />
Start neosys.js /system ADAGENCY /database <b>testdatabasecode</b><br />
<br />
(where <b>testdatabasecode</b> is the code of the testdatabase)<br />
(also you need to replace ADAGENCY with ACCOUNTS if this is an accounts only installation)<br />
<br />
TEST THAT THE FILES YOU HAVE CREATED CAN RUN SUCCESSFULLY<br />
<br />
ENSURE THAT YOU DO NOT CLOSE THE PROCESS WINDOWS BY USING THE X BUTTON. HIT ESC 3 TIMES ON EACH WINDOW.<br />
<br />
=== Differences for Pure Accounts Module Only Installations ===<br />
Accounts module only has a slightly different startup command. In the above, replace '''/system adagency''' with '''/system accounts''' to startup a service and use '''accounts.bat''' instead of '''adagency.bat''' to start up maintenance. Other than that, accounts module setup is identical. Pure accounts clients are very few and tend not to upgrade often so care needs to be taken when upgrading. Upgrade is perhaps surprisingly done using the adagency.exe file.<br />
<br />
=== Creating a .CMD file to copy maindata to testdata ===<br />
<br />
In x:\neosys create a file <B>copy MAINDATABASECODE to TESTDABASECODE.cmd</b><br />
<br />
xcopy x:\neosys\data\<i>maindatabasecode</i> x:\neosys\data\<i>testdatabasecode</i> /s /y<br />
<br />
eg. xcopy c:\neosys\data\<i>ALTOVIST</i> x:\neosys\data\<i>AVTEST</i> /s /y<br />
<br />
Run this file to test that it works fine.<br />
<br />
=== Setting up daily scheduled tasks ===<br />
<b>Automatic Schedules:</b><br />
NEOSYS automatically shuts down at 1am (was 2am) every morning for backup. It closes all the running processes and backups up to the selected drive.<br />
<br />
<b>Manually Configured Schedules:</b> to be done under Scheduled Tasks<br />
<br />
Note: Under Windows 2008 Standard you need to UNTICK highest privileges and UNTICK run whether user is logged in or not as shown in the screen shots that follow:<br />
<br />
1. Create a task to start one Main database process at 6:00 am daily.<br />
<br />
[[File:start1.jpg]]<br><br><br><br />
[[File:start2.jpg]]<br><br><br><br />
[[File:start3.jpg]]<br><br><br><br />
<br />
2. Create a second task to Copy Maindata to Testdata at 2:45 am daily.<br />
<br />
[[File:copy1.jpg]]<br><br><br><br />
[[File:copy2.jpg]]<br><br><br><br />
[[File:copy3.jpg]]<br><br><br><br />
<br />
<br />
(For multiple sites on the same computer put the second site starting five minutes later at 6:05am, third site starting five minutes earlier at 5:55am, the third site starting five minutes later at 6:10am and so on.)<br />
<br />
Once created, test them to see that they are working correctly by running them directly using right click- Run.<br />
<br />
[[File:task1.jpg]]<br><br><br><br />
<br />
(Use web access and go to Support Menu, System Configuration File to request 3 processes for main database and 1 for test database).<br />
<br />
Please note that test running “copy test data” should be avoided while users are online but there is no problem testing the “daily 6am startup task” at any time since it will just add an additional process.<br />
<br />
=== Configuring NEOSYS to start automatically on server start-up / reboot ===<br />
We no longer configure NEOSYS processes to start on reboot as we would like to know of the failures at the client side and hence whenever the server reboots we expect the client to inform us and we will start the process - or NEOSYS will start automatically next day at 6 am<br />
<br />
Unfortunately using this method the NEOSYS processes are not visible when you login as a user. <br />
<br />
[[Image:win_sch_task.jpg]]<br />
<br />
Schedule a task to run the main database file whenever the computer starts. In Windows 2008 you need to tick the options - Run whether user logged in or not and Run with highest privilege.<br />
<br />
Additional in Windows 2008: Tick Highest Priviledges and Run whether user logged in or not<br />
<br />
== Installing and upgrading NEOSYS pure accounting systems ==<br />
<br />
Basic installation using NEOSYS.EXE and upgrades using NEOSYS2.EXE are identical to the normal adagency installation process.<br />
<br />
Differences are as follows:<br />
<br />
# Maintenance shortcut to ACCOUNTS.BAT<br />
# Process startup file contains "/system ACCOUNTS" instead of "/system ADAGENCY"<br />
# Internet address is http://server/neosys/accounts.htm although it auto converts to http://server/neosys/default.htm??ACCOUNTS. Although not to be relied upon, the login page stores a cookie so even plain http://server/neosys or http://server/neosys/default.htm works thereafter until the cookie is lost. To get back to adagency login you use http://server/neosys/default.htm??ADAGENCY<br />
# BACKUP.ZIP files created by ADAGENCY systems and ACCOUNTS systems are slightly incompatible with the result that restoring one in the other type of system will not work. NEOSYS programmers can convert from one type to the other but it is almost never required since any ad agency that only requires accounts only module is given the adagency version of NEOSYS and accounting only clients becoming ad agencies never happened.</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Handling_damaged_files&diff=683Handling damaged files2011-05-24T13:53:54Z<p>Sunny: /* Fixing damaged file that have a process to recreate them */</p>
<hr />
<div>== Symptoms ==<br />
<br />
"A Damaged file has been found..... ((the rest of this message to be completed)) <br />
Group format Error:<br />
OS File : BOOKING.TEXTS<br />
Group# : 00000932<br />
Record length incorrect or frame linkage error.<br />
<br />
== Cause ==<br />
Rare but nasty problem on server 99% caused by power failure, killing NEOSYS or server hardware or operating system failure.<br />
<br />
*Did somebody kill NEOSYS processes to reboot the server or any other reason?<br />
*Was there a power cut?<br />
*Any expected or unexpected reboots in the server log? (see Event Viewer > System Log)<br />
*Enough disk free space especially on servers not dedicated to NEOSYS?<br />
*Third party software running on NEOSYS server?<br />
*RAID installed on the server?<br />
*Did windows update happen?<br />
<br />
== Solution==<br />
<br />
Damaged files, when detected, cause an immediate termination of the currently executing program/user request and a restart of the process is involved. Some damaged files are automatically fixed during restart. Although the process "restarts" it may be internally corrupted in some way and it is advisable to close it completely and start or allow another process to start automatically.<br><br><br />
However, the solution always depends on the cause and usually often requires aggressive interrogation to discover the cause.<br />
<br />
== Recovery==<br />
<br />
It is URGENT to stop using NEOSYS and fix the damaged file because it will cause NEOSYS to crash everytime it happens to update that part of the file. NEOSYS crashing while updating often produces unrecoverable inconsistencies in the database that can only be fixed by programmers sitting for hours trying to edit the database .... or by restoring from a backup causing loss of work.<br />
<br />
See the following sections how to patch the damaged files.<br />
<br />
== Files that are automatically fixed ==<br />
<br />
*LISTS<br />
*LOCKS<br />
*!INDEXING<br />
<br />
The above files are automatically checked for corruption (and initialised to empty if so) when you <br />
startup a NEOSYS process and do not require any manual intervention apart from locating and eliminating the initial cause of the damage.<br />
<br />
If the !INDEXING file was damaged then you should also do REINDEXALL to reinstate any possibly missing index entries, but since this will take a long time<br />
you should do this when everybody is off the system in the evening probably. A few missing index entries may only mean some records missing from some reports which may or may not be seriously inconvenient. It is a temporary file that should not hold any records for longer than it takes to update the various indexes immediately when the user saves any document.<br />
<br />
Each process has its own LISTS file, so damage is limited to one process for the LISTS file. The process number can be seen in the error message. for example:<br />
<br />
Process=7<br />
<br />
You can also see the process number on the server screen. For example here is a process 2.<br />
<br />
13:17:31 TESTDB NEOS0002 0 Listening 7 hours, 49 mins ...<br />
<br />
The LISTS file is a temporary file for sorting records into order for reports, popups etc. Therefore any damage usually causes no real inconvenience apart from the failed report or popup on which the user might receive the "damaged LISTS file" message.<br />
<br />
The error message would appear as follows :<br />
<br />
SYSTEM ERROR:<br />
An internal file LISTS was found<br />
to be damaged and has been patched.<br />
INFORM YOUR TECHNICAL SUPPORT<br><br />
SOME DATA HAS PROBABLY BEEN LOST<br />
AND THE NEOSYS SYSTEM MAY MALFUNCTION<br><br />
Server=NEOSYS-SERVER<br />
Install=D:\NEOSYS\NEOSYS\<br />
Version=17:16:04 23 JAN 2011<br />
Database=1D68EE63 ADLINED<br />
Process=2<br />
<br />
The error could also appear as follows :<br />
<br />
A DAMAGED FILE HAS BEEN FOUND.<br />
YOU MUST GIVE THE FOLLOWING MESSAGE TO TECHNICAL SUPPORT NOW.<br />
DO NOT CONTINUE USING THE SYSTEM!<br><br />
Group Format Error:<br />
File : LISTS<br />
Group # : 00000014<br />
Record length incorrect or frame linkage error.<br />
Server=NEOSYS-SERVER<br />
Install=D:\NEOSYS\NEOSYS\<br />
Version=17:16:04 23 JAN 2011<br />
Database=1D68EE63 ADLINED<br />
Process=2<br />
<br />
Please note that both the above messages mean the same.<br />
<br />
== Fixing damaged file that have a process to recreate them ==<br />
<br />
Below files can be recreated from the maintenance mode.<br />
<br />
ADS file can be recreated with F5 CREATEADS<br />
<br />
ANALYSIS file can be recreated with F5 CREATEANALYSIS<br />
<br />
BRANDS files can be recreated with F5 CREATEBRANDS<br />
<br />
If the file is actually damaged it might be necessary to initialise it first using CLEARFILE filename.<br />
<br />
The following is an example of the error in the ADS File at the time of backup.<br />
<br />
Group Format Error:<br />
OS File : ADS<br />
Group # : 00009543<br />
Record length incorrect or frame linkage error.<br />
217 files checked.<br />
Failed with 1 errors<br />
!!! DANGER !!!<br />
!!! DAMAGED FILES HAVE BEEN FOUND IN THE NEOSYS SYSTEM !!!<br />
!!! BACKUP NOT DONE !!!<br />
<br />
Error while writing data.<br />
You have attempted to write to a read-only file.<br />
- or -<br />
access to the file has been denied by the operating system.<br />
(operating system file name: "ADS")<br />
<br />
Explanation: The last four lines are very rare and can be seen with the above error messages in the backup email. The above message indicates that external application is trying to access the backup files at the time of backup.<br />
<br />
Before doing the solution below, please check the number of damaged files on the database by running CHK.FILES in maintenance mode. [CHK.FILES can be done when users are online]<br />
<br />
Solution<br />
<br />
'''NOTE:''' Stop all the processes before doing the below procedure.<br />
<br />
Procedure to run CREATESADS is as under <br />
<br />
Login to maintenance<br />
<br />
F5<br />
CREATEXXXX<br />
<br />
(XXXX = ADS, ANALYSIS OR BRANDS)<br />
<br />
Select the option appropriate option and start the procedure and hit ENTER<br />
<br />
To verify if the above is done successfully and check if the damage files is fixed in the database run CHK.FILES or CHK.FILES FILENAME(Recommended)from this link: http://techwiki.neosys.com/index.php/Troubleshooting_NEOSYS_Generally#Checking_for_corrupt_database_files<br />
<br />
== Fixing damaged index files (names starting with !) ==<br />
<br />
Whilst backing up or using NEOSYS the following error message might appear:<br />
<br />
"A Damaged file has been found.....<br />
Group format Error:<br />
OS File : !ADS<br />
Group# : 00000932<br />
Record length incorrect or frame linkage error.<br />
<br />
#Ensure that no-one is using NEOSYS<br />
#Log into NEOSYS on the server<br />
#Press F5 to get a TCL command box<br />
#Type REINDEXADS and press enter.<br />
#Wait until it finishes and you get back to the command box<br />
#Type OFF in the command box and you will quit NEOSYS.<br />
<br />
Other reindex commands are:<br />
<br />
*REINDEXACCOUNTS recreates !ACCOUNTS, !BATCHES and !VOUCHERS<br />
*REINDEXADDRESSES <br />
*REINDEXADS<br />
*REINDEXBOOKINGS recreates !BOOKING.ORDERS<br />
*REINDEXBRANDS<br />
*REINDEXCLIENTS<br />
*REINDEXINVS recreates !INVOICES<br />
*REINDEXJOBS<br />
*REINDEXMATERIALS<br />
*REINDEXPLANS<br />
*REINDEXPRODINVS recreates !PRODUCTION.INVOICES<br />
*REINDEXPRODORDERS recreates !PRODUCTION.ORDERS<br />
*REINDEXRATECARDS<br />
*REINDEXSCHEDULES<br />
*REINDEXSUPPLIERS<br />
*REINDEXTIMESHEETS<br />
*REINDEXVEHICLES<br />
<br />
REINDEXMEDIA does all the following<br />
*REINDEXPLANS<br />
*REINDEXSCHEDULES<br />
*REINDEXADS<br />
*REINDEXMATERIALS<br />
*REINDEXBOOKINGS<br />
<br />
REINDEXFILES does all the following<br />
*REINDEXCLIENTS<br />
*REINDEXBRANDS<br />
*REINDEXSUPPLIERS<br />
*REINDEXVEHICLES<br />
*REINDEXRATECARDS<br />
<br />
REINDEXPRODUCTION does all the following<br />
*REINDEXJOBS<br />
*REINDEXPRODORDERS<br />
*REINDEXPRODINVS<br />
*REINDEXTIMESHEETS<br />
<br />
REINDEXALL does all the following<br />
*REINDEXMEDIA<br />
*REINDEXPRODUCTION<br />
*REINDEXFILES<br />
*REINDEXINVS<br />
*REINDEXACCOUNTS<br />
*REINDEXADDRESSES<br />
<br />
== Fixing damaged files that have no process for recreating them ==<br />
<br />
Some damaged files can be rebuilt using NEOSYS utilities especially index files with filenames starting with !. Other damaged files like ''LOG20xx'' can be “fixed” to prevent NEOSYS crashes as follows <i>but some records will most probably be lost</i>. Depending on the file loss of a few records may not be too bad compared to restoring a database but the client should be informed and make the decision. Depending on the file it is usually best to lose the records. We can make a list of files that one can afford to lose records and those files that can be rebuilt programmatically from other files. Booking order texts they can lose records but inform them and especially the numbers mentioned in FIXFILE<br />
<br />
FIXFILE will not run if there are neosys services still running so before doing the FIXFILE command, shut down services from the Support menu or with the Global command:<br />
<br />
'''NOTE:''' If there are multiple datasets running on the server. Shut down the particular dataset which has got the problem:<br />
<br />
F5<br />
<br />
FIXFILE filename<br />
<br />
(Select option 1 to update the file)<br />
<br />
In case you get any Overwrite messages – type YES, as these are the actual files being updated.<br />
<br />
The only alternative is restore from a previous backup in this case losing a days work. Nasty, and even worse, it will be impossible to reproduce the days work and especially the exact serial numbers of critical documents like orders, invoices, receipts and payments advices.<br />
<br />
<br />
=== Using FIXFILE to repair corrupted files ===<br />
<br />
BEWARE: FIXFILE causes loss of data. If the data is critical then use of FIXFILE can be totally catastrophic without any warning.<br />
<br />
Using FIXFILE on some files is a guaranteed way to cause complete chaos for the users without them being aware of it until too late to do anything about it.<br />
<br />
Corrupt files will cause programs to abort every time they try to update that section of the file. Aborting programs causes possibly horrendous inconsistency in the database so it is important to stop all user activity and fix the corrupt file immediately.<br />
<br />
You can freely use FIXFILE on any file but it works by deleting any problematic data so cannot realistically be used on some files at all.<br />
<br />
FIXFILE cannot and does not recover any corrupted records therefore, for those files that have specific programs to rebuild them, FIXFILE is not the correct option.<br />
<br />
Why use FIXFILE at all since it causes loss of data?<br />
<br />
Many files do not have programs to rebuild them and for some of those files, using FIXFILE is a quick way to get the system back in operation BUT with missing records. Missing records causes various degrees of failure ranging from the odd document missing, totally misleading information like wrong account balances, or any kind of system failure.<br />
<br />
FIXFILE does not fix the consistency of information in the database. When the database is is being updated with a transaction, usually a series of files are updated for the one transaction. A damaged file causes the update program to abort in the middle of the series of updates. Therefore some of the updates are done and the remaining updates are not done. This means that the data in the database (even after fixing the corrupt file) is inconsistent.<br />
<br />
FIXFILE merely fixes the technical structure of the file so that any further program accesses to that portion of the file do not cause immediate program termination and consequent likely catastrophic database inconsistency.<br />
<br />
You must prevent anyone from accessing NEOSYS while FIXFILE is running.<br />
<br />
=== Fixing Damaged DEFINITIONS file ===<br />
<br />
==== Non-Solution ====<br />
<br />
You will probably not be able to login if the DEFINITIONS FILE is damaged. You can press Alt+S and type EXECUTE to get a TCL command box but this still doesnt help because you cannot use FIXFILE on DEFINITIONS.<br />
<br />
CAUTION: DO NOT USE FIXFILE TO TRY AND FIX THE DEFINITIONS FILE.<br />
<br />
DOUBLE CAUTION: IN CASE YOU DECIDE TO IGNORE THIS EXPECT ALL KINDS OF HORRIBLE PROBLEMS IN THE DATABASE REQUIRING A COMPLETE RESTORE FROM A GOOD BACKUP AFTER A FEW DAYS OF PAIN BECAUSE RANDOM OLD DATABASE UPGRADE/CONVERSIONS WILL BE PERFORMED *AGAIN* WITHOUT YOU KNOWING IT.<br />
<br />
==== Partial Restore ====<br />
<br />
You can copy recent DEFINITIONS.LK and DEFINITIONS.OV files from the DATA\datasetcode\GENERAL folder.<br />
<br />
CAUTION: All changes done in the Configuration File, Authorisation File, Users File and various other changes will be reverted to the date of the DEFINITIONS files being restored. If you are restoring from last nights backup or testdata then this will not be much but could cause serious confusion to people who have changed their passwords etc.<br />
<br />
==== Full Restore ====<br />
<br />
Restore from your latest backup losing all work done since that time and date.<br />
<br />
=== Preventing users from accessing NEOSYS in order to do maintenance or repairs ===<br />
<br />
On most systems you can simply stop the NEOSYS processes. On other systems where NEOSYS processes are automatically started in response to requests from the web, you need to disable the autostart by one of the following methods<br />
<br />
# Stop the autostart program/script<br />
# Put a file called NET.CFG with a single line saying AUTOSTART=NO in the neosys\neosys folder<br />
# Stop the IIS server<br />
# Stop/Pause the particular web in question<br />
<br />
== Dealing with damaged files that cannot be fixed ==<br />
<br />
If programmers are unable to fix the damage in a reasonably period of time and the damage is caused due to matters beyond NEOSYS control such as non-dedicated servers and power failures then data must be restored and client advised why they are going to suffer loss of data.<br />
<br />
THIS DOES NOT RELEASE NEOSYS SUPPORT STAFF FROM THE OBLIGATION TO PROACTIVELY INFORM THE CLIENT OF MEASURES TO PREVENT THE RECURRENCE OF THE EVENT.<br />
<br />
The following are the steps to follow:<br />
<br />
# Ascertain the cause of the damage to the database by looking at the internal logs<br />
# Create a new database from the damaged one as it will contain the up to date but damaged database.<br />
# Restore the database from the backup media so that the database is in the last good known state. <br />
# The client can see what work was done over the past couple of days from the damaged database and it will assist them to redo the work in the currently restored out of date main database.<br />
# Next discuss with the client about the cause of the damage and (a) what to do to prevent the damage occurring again (b) to agree a procedure to perform a manual backup in case the automatic one is not performed for any reason overnight.</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Handling_damaged_files&diff=682Handling damaged files2011-05-24T09:49:30Z<p>Sunny: /* Fixing damaged file that have a process to recreate them */</p>
<hr />
<div>== Symptoms ==<br />
<br />
"A Damaged file has been found..... ((the rest of this message to be completed)) <br />
Group format Error:<br />
OS File : BOOKING.TEXTS<br />
Group# : 00000932<br />
Record length incorrect or frame linkage error.<br />
<br />
== Cause ==<br />
Rare but nasty problem on server 99% caused by power failure, killing NEOSYS or server hardware or operating system failure.<br />
<br />
*Did somebody kill NEOSYS processes to reboot the server or any other reason?<br />
*Was there a power cut?<br />
*Any expected or unexpected reboots in the server log? (see Event Viewer > System Log)<br />
*Enough disk free space especially on servers not dedicated to NEOSYS?<br />
*Third party software running on NEOSYS server?<br />
*RAID installed on the server?<br />
*Did windows update happen?<br />
<br />
== Solution==<br />
<br />
Damaged files, when detected, cause an immediate termination of the currently executing program/user request and a restart of the process is involved. Some damaged files are automatically fixed during restart. Although the process "restarts" it may be internally corrupted in some way and it is advisable to close it completely and start or allow another process to start automatically.<br><br><br />
However, the solution always depends on the cause and usually often requires aggressive interrogation to discover the cause.<br />
<br />
== Recovery==<br />
<br />
It is URGENT to stop using NEOSYS and fix the damaged file because it will cause NEOSYS to crash everytime it happens to update that part of the file. NEOSYS crashing while updating often produces unrecoverable inconsistencies in the database that can only be fixed by programmers sitting for hours trying to edit the database .... or by restoring from a backup causing loss of work.<br />
<br />
See the following sections how to patch the damaged files.<br />
<br />
== Files that are automatically fixed ==<br />
<br />
*LISTS<br />
*LOCKS<br />
*!INDEXING<br />
<br />
The above files are automatically checked for corruption (and initialised to empty if so) when you <br />
startup a NEOSYS process and do not require any manual intervention apart from locating and eliminating the initial cause of the damage.<br />
<br />
If the !INDEXING file was damaged then you should also do REINDEXALL to reinstate any possibly missing index entries, but since this will take a long time<br />
you should do this when everybody is off the system in the evening probably. A few missing index entries may only mean some records missing from some reports which may or may not be seriously inconvenient. It is a temporary file that should not hold any records for longer than it takes to update the various indexes immediately when the user saves any document.<br />
<br />
Each process has its own LISTS file, so damage is limited to one process for the LISTS file. The process number can be seen in the error message. for example:<br />
<br />
Process=7<br />
<br />
You can also see the process number on the server screen. For example here is a process 2.<br />
<br />
13:17:31 TESTDB NEOS0002 0 Listening 7 hours, 49 mins ...<br />
<br />
The LISTS file is a temporary file for sorting records into order for reports, popups etc. Therefore any damage usually causes no real inconvenience apart from the failed report or popup on which the user might receive the "damaged LISTS file" message.<br />
<br />
The error message would appear as follows :<br />
<br />
SYSTEM ERROR:<br />
An internal file LISTS was found<br />
to be damaged and has been patched.<br />
INFORM YOUR TECHNICAL SUPPORT<br><br />
SOME DATA HAS PROBABLY BEEN LOST<br />
AND THE NEOSYS SYSTEM MAY MALFUNCTION<br><br />
Server=NEOSYS-SERVER<br />
Install=D:\NEOSYS\NEOSYS\<br />
Version=17:16:04 23 JAN 2011<br />
Database=1D68EE63 ADLINED<br />
Process=2<br />
<br />
The error could also appear as follows :<br />
<br />
A DAMAGED FILE HAS BEEN FOUND.<br />
YOU MUST GIVE THE FOLLOWING MESSAGE TO TECHNICAL SUPPORT NOW.<br />
DO NOT CONTINUE USING THE SYSTEM!<br><br />
Group Format Error:<br />
File : LISTS<br />
Group # : 00000014<br />
Record length incorrect or frame linkage error.<br />
Server=NEOSYS-SERVER<br />
Install=D:\NEOSYS\NEOSYS\<br />
Version=17:16:04 23 JAN 2011<br />
Database=1D68EE63 ADLINED<br />
Process=2<br />
<br />
Please note that both the above messages mean the same.<br />
<br />
== Fixing damaged file that have a process to recreate them ==<br />
<br />
Below files can be recreated from the maintenance mode.<br />
<br />
ADS file can be recreated with F5 CREATEADS<br />
<br />
ANALYSIS file can be recreated with F5 CREATEANALYSIS<br />
<br />
BRANDS files can be recreated with F5 CREATEBRANDS<br />
<br />
If the file is actually damaged it might be necessary to initialise it first using CLEARFILE filename.<br />
<br />
'''Symptoms'''<br />
<br />
While backup up the following error might appear<br />
Group Format Error:<br />
OS File : ADS<br />
Group # : 00009543<br />
Record length incorrect or frame linkage error.<br />
217 files checked.<br />
Failed with 1 errors<br />
!!! DANGER !!!<br />
!!! DAMAGED FILES HAVE BEEN FOUND IN THE NEOSYS SYSTEM !!!<br />
!!! BACKUP NOT DONE !!!<br />
<br />
Explanation: An AD file is damaged while doing a nightly backup.<br />
<br />
Error while writing data.<br />
You have attempted to write to a read-only file.<br />
- or -<br />
access to the file has been denied by the operating system.<br />
(operating system file name: "ADS")<br />
<br />
Explanation: This message is very rare and can be seen with the above error messages in the backup email. The above message says, some thing is trying to access the files at the time of backup.<br />
<br />
Before doing the solution below, please check the number of damaged files for the database by running CHK.FILES in maintenance mode. [This can be done when users are online]<br />
<br />
Solution<br />
<br />
'''NOTE:''' Stop all the processes before doing the below procedure.<br />
<br />
Procedure to run CREATESADS is as under <br />
<br />
Login to maintenance<br />
<br />
F5<br />
CREATEXXXX<br />
<br />
(XXXX = ADS, ANALYSIS OR BRANDS)<br />
<br />
Select the option appropriate option and start the procedure and hit ENTER<br />
<br />
To verify if the above is done successfully and check if the damage files is fixed in the database run CHK.FILES or CHK.FILES FILENAME(Recommended)from this link: http://techwiki.neosys.com/index.php/Troubleshooting_NEOSYS_Generally#Checking_for_corrupt_database_files<br />
<br />
== Fixing damaged index files (names starting with !) ==<br />
<br />
Whilst backing up or using NEOSYS the following error message might appear:<br />
<br />
"A Damaged file has been found.....<br />
Group format Error:<br />
OS File : !ADS<br />
Group# : 00000932<br />
Record length incorrect or frame linkage error.<br />
<br />
#Ensure that no-one is using NEOSYS<br />
#Log into NEOSYS on the server<br />
#Press F5 to get a TCL command box<br />
#Type REINDEXADS and press enter.<br />
#Wait until it finishes and you get back to the command box<br />
#Type OFF in the command box and you will quit NEOSYS.<br />
<br />
Other reindex commands are:<br />
<br />
*REINDEXACCOUNTS recreates !ACCOUNTS, !BATCHES and !VOUCHERS<br />
*REINDEXADDRESSES <br />
*REINDEXADS<br />
*REINDEXBOOKINGS recreates !BOOKING.ORDERS<br />
*REINDEXBRANDS<br />
*REINDEXCLIENTS<br />
*REINDEXINVS recreates !INVOICES<br />
*REINDEXJOBS<br />
*REINDEXMATERIALS<br />
*REINDEXPLANS<br />
*REINDEXPRODINVS recreates !PRODUCTION.INVOICES<br />
*REINDEXPRODORDERS recreates !PRODUCTION.ORDERS<br />
*REINDEXRATECARDS<br />
*REINDEXSCHEDULES<br />
*REINDEXSUPPLIERS<br />
*REINDEXTIMESHEETS<br />
*REINDEXVEHICLES<br />
<br />
REINDEXMEDIA does all the following<br />
*REINDEXPLANS<br />
*REINDEXSCHEDULES<br />
*REINDEXADS<br />
*REINDEXMATERIALS<br />
*REINDEXBOOKINGS<br />
<br />
REINDEXFILES does all the following<br />
*REINDEXCLIENTS<br />
*REINDEXBRANDS<br />
*REINDEXSUPPLIERS<br />
*REINDEXVEHICLES<br />
*REINDEXRATECARDS<br />
<br />
REINDEXPRODUCTION does all the following<br />
*REINDEXJOBS<br />
*REINDEXPRODORDERS<br />
*REINDEXPRODINVS<br />
*REINDEXTIMESHEETS<br />
<br />
REINDEXALL does all the following<br />
*REINDEXMEDIA<br />
*REINDEXPRODUCTION<br />
*REINDEXFILES<br />
*REINDEXINVS<br />
*REINDEXACCOUNTS<br />
*REINDEXADDRESSES<br />
<br />
== Fixing damaged files that have no process for recreating them ==<br />
<br />
Some damaged files can be rebuilt using NEOSYS utilities especially index files with filenames starting with !. Other damaged files like ''LOG20xx'' can be “fixed” to prevent NEOSYS crashes as follows <i>but some records will most probably be lost</i>. Depending on the file loss of a few records may not be too bad compared to restoring a database but the client should be informed and make the decision. Depending on the file it is usually best to lose the records. We can make a list of files that one can afford to lose records and those files that can be rebuilt programmatically from other files. Booking order texts they can lose records but inform them and especially the numbers mentioned in FIXFILE<br />
<br />
FIXFILE will not run if there are neosys services still running so before doing the FIXFILE command, shut down services from the Support menu or with the Global command:<br />
<br />
'''NOTE:''' If there are multiple datasets running on the server. Shut down the particular dataset which has got the problem:<br />
<br />
F5<br />
<br />
FIXFILE filename<br />
<br />
(Select option 1 to update the file)<br />
<br />
In case you get any Overwrite messages – type YES, as these are the actual files being updated.<br />
<br />
The only alternative is restore from a previous backup in this case losing a days work. Nasty, and even worse, it will be impossible to reproduce the days work and especially the exact serial numbers of critical documents like orders, invoices, receipts and payments advices.<br />
<br />
<br />
=== Using FIXFILE to repair corrupted files ===<br />
<br />
BEWARE: FIXFILE causes loss of data. If the data is critical then use of FIXFILE can be totally catastrophic without any warning.<br />
<br />
Using FIXFILE on some files is a guaranteed way to cause complete chaos for the users without them being aware of it until too late to do anything about it.<br />
<br />
Corrupt files will cause programs to abort every time they try to update that section of the file. Aborting programs causes possibly horrendous inconsistency in the database so it is important to stop all user activity and fix the corrupt file immediately.<br />
<br />
You can freely use FIXFILE on any file but it works by deleting any problematic data so cannot realistically be used on some files at all.<br />
<br />
FIXFILE cannot and does not recover any corrupted records therefore, for those files that have specific programs to rebuild them, FIXFILE is not the correct option.<br />
<br />
Why use FIXFILE at all since it causes loss of data?<br />
<br />
Many files do not have programs to rebuild them and for some of those files, using FIXFILE is a quick way to get the system back in operation BUT with missing records. Missing records causes various degrees of failure ranging from the odd document missing, totally misleading information like wrong account balances, or any kind of system failure.<br />
<br />
FIXFILE does not fix the consistency of information in the database. When the database is is being updated with a transaction, usually a series of files are updated for the one transaction. A damaged file causes the update program to abort in the middle of the series of updates. Therefore some of the updates are done and the remaining updates are not done. This means that the data in the database (even after fixing the corrupt file) is inconsistent.<br />
<br />
FIXFILE merely fixes the technical structure of the file so that any further program accesses to that portion of the file do not cause immediate program termination and consequent likely catastrophic database inconsistency.<br />
<br />
You must prevent anyone from accessing NEOSYS while FIXFILE is running.<br />
<br />
=== Fixing Damaged DEFINITIONS file ===<br />
<br />
==== Non-Solution ====<br />
<br />
You will probably not be able to login if the DEFINITIONS FILE is damaged. You can press Alt+S and type EXECUTE to get a TCL command box but this still doesnt help because you cannot use FIXFILE on DEFINITIONS.<br />
<br />
CAUTION: DO NOT USE FIXFILE TO TRY AND FIX THE DEFINITIONS FILE.<br />
<br />
DOUBLE CAUTION: IN CASE YOU DECIDE TO IGNORE THIS EXPECT ALL KINDS OF HORRIBLE PROBLEMS IN THE DATABASE REQUIRING A COMPLETE RESTORE FROM A GOOD BACKUP AFTER A FEW DAYS OF PAIN BECAUSE RANDOM OLD DATABASE UPGRADE/CONVERSIONS WILL BE PERFORMED *AGAIN* WITHOUT YOU KNOWING IT.<br />
<br />
==== Partial Restore ====<br />
<br />
You can copy recent DEFINITIONS.LK and DEFINITIONS.OV files from the DATA\datasetcode\GENERAL folder.<br />
<br />
CAUTION: All changes done in the Configuration File, Authorisation File, Users File and various other changes will be reverted to the date of the DEFINITIONS files being restored. If you are restoring from last nights backup or testdata then this will not be much but could cause serious confusion to people who have changed their passwords etc.<br />
<br />
==== Full Restore ====<br />
<br />
Restore from your latest backup losing all work done since that time and date.<br />
<br />
=== Preventing users from accessing NEOSYS in order to do maintenance or repairs ===<br />
<br />
On most systems you can simply stop the NEOSYS processes. On other systems where NEOSYS processes are automatically started in response to requests from the web, you need to disable the autostart by one of the following methods<br />
<br />
# Stop the autostart program/script<br />
# Put a file called NET.CFG with a single line saying AUTOSTART=NO in the neosys\neosys folder<br />
# Stop the IIS server<br />
# Stop/Pause the particular web in question<br />
<br />
== Dealing with damaged files that cannot be fixed ==<br />
<br />
If programmers are unable to fix the damage in a reasonably period of time and the damage is caused due to matters beyond NEOSYS control such as non-dedicated servers and power failures then data must be restored and client advised why they are going to suffer loss of data.<br />
<br />
THIS DOES NOT RELEASE NEOSYS SUPPORT STAFF FROM THE OBLIGATION TO PROACTIVELY INFORM THE CLIENT OF MEASURES TO PREVENT THE RECURRENCE OF THE EVENT.<br />
<br />
The following are the steps to follow:<br />
<br />
# Ascertain the cause of the damage to the database by looking at the internal logs<br />
# Create a new database from the damaged one as it will contain the up to date but damaged database.<br />
# Restore the database from the backup media so that the database is in the last good known state. <br />
# The client can see what work was done over the past couple of days from the damaged database and it will assist them to redo the work in the currently restored out of date main database.<br />
# Next discuss with the client about the cause of the damage and (a) what to do to prevent the damage occurring again (b) to agree a procedure to perform a manual backup in case the automatic one is not performed for any reason overnight.</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Handling_damaged_files&diff=681Handling damaged files2011-05-24T08:01:16Z<p>Sunny: /* Cause */</p>
<hr />
<div>== Symptoms ==<br />
<br />
"A Damaged file has been found..... ((the rest of this message to be completed)) <br />
Group format Error:<br />
OS File : BOOKING.TEXTS<br />
Group# : 00000932<br />
Record length incorrect or frame linkage error.<br />
<br />
== Cause ==<br />
Rare but nasty problem on server 99% caused by power failure, killing NEOSYS or server hardware or operating system failure.<br />
<br />
*Did somebody kill NEOSYS processes to reboot the server or any other reason?<br />
*Was there a power cut?<br />
*Any expected or unexpected reboots in the server log? (see Event Viewer > System Log)<br />
*Enough disk free space especially on servers not dedicated to NEOSYS?<br />
*Third party software running on NEOSYS server?<br />
*RAID installed on the server?<br />
*Did windows update happen?<br />
<br />
== Solution==<br />
<br />
Damaged files, when detected, cause an immediate termination of the currently executing program/user request and a restart of the process is involved. Some damaged files are automatically fixed during restart. Although the process "restarts" it may be internally corrupted in some way and it is advisable to close it completely and start or allow another process to start automatically.<br><br><br />
However, the solution always depends on the cause and usually often requires aggressive interrogation to discover the cause.<br />
<br />
== Recovery==<br />
<br />
It is URGENT to stop using NEOSYS and fix the damaged file because it will cause NEOSYS to crash everytime it happens to update that part of the file. NEOSYS crashing while updating often produces unrecoverable inconsistencies in the database that can only be fixed by programmers sitting for hours trying to edit the database .... or by restoring from a backup causing loss of work.<br />
<br />
See the following sections how to patch the damaged files.<br />
<br />
== Files that are automatically fixed ==<br />
<br />
*LISTS<br />
*LOCKS<br />
*!INDEXING<br />
<br />
The above files are automatically checked for corruption (and initialised to empty if so) when you <br />
startup a NEOSYS process and do not require any manual intervention apart from locating and eliminating the initial cause of the damage.<br />
<br />
If the !INDEXING file was damaged then you should also do REINDEXALL to reinstate any possibly missing index entries, but since this will take a long time<br />
you should do this when everybody is off the system in the evening probably. A few missing index entries may only mean some records missing from some reports which may or may not be seriously inconvenient. It is a temporary file that should not hold any records for longer than it takes to update the various indexes immediately when the user saves any document.<br />
<br />
Each process has its own LISTS file, so damage is limited to one process for the LISTS file. The process number can be seen in the error message. for example:<br />
<br />
Process=7<br />
<br />
You can also see the process number on the server screen. For example here is a process 2.<br />
<br />
13:17:31 TESTDB NEOS0002 0 Listening 7 hours, 49 mins ...<br />
<br />
The LISTS file is a temporary file for sorting records into order for reports, popups etc. Therefore any damage usually causes no real inconvenience apart from the failed report or popup on which the user might receive the "damaged LISTS file" message.<br />
<br />
The error message would appear as follows :<br />
<br />
SYSTEM ERROR:<br />
An internal file LISTS was found<br />
to be damaged and has been patched.<br />
INFORM YOUR TECHNICAL SUPPORT<br><br />
SOME DATA HAS PROBABLY BEEN LOST<br />
AND THE NEOSYS SYSTEM MAY MALFUNCTION<br><br />
Server=NEOSYS-SERVER<br />
Install=D:\NEOSYS\NEOSYS\<br />
Version=17:16:04 23 JAN 2011<br />
Database=1D68EE63 ADLINED<br />
Process=2<br />
<br />
The error could also appear as follows :<br />
<br />
A DAMAGED FILE HAS BEEN FOUND.<br />
YOU MUST GIVE THE FOLLOWING MESSAGE TO TECHNICAL SUPPORT NOW.<br />
DO NOT CONTINUE USING THE SYSTEM!<br><br />
Group Format Error:<br />
File : LISTS<br />
Group # : 00000014<br />
Record length incorrect or frame linkage error.<br />
Server=NEOSYS-SERVER<br />
Install=D:\NEOSYS\NEOSYS\<br />
Version=17:16:04 23 JAN 2011<br />
Database=1D68EE63 ADLINED<br />
Process=2<br />
<br />
Please note that both the above messages mean the same.<br />
<br />
== Fixing damaged file that have a process to recreate them ==<br />
<br />
ADS file can be recreated with F5 CREATEADS<br />
<br />
ANALYSIS file can be recreated with F5 CREATEANALYSIS<br />
<br />
BRANDS files can be recreated with F5 CREATEBRANDS<br />
<br />
If the file is actually damaged it might be necessary to initialise it first using CLEARFILE filename.<br />
<br />
Procedure to run CREATEXXXX (Where XXXX = ADS, ANALYSIS OR BRANDS)<br />
<br />
NOTE: Stop all the processes before doing the below procedure.<br />
<br />
Login to maintenance<br />
<br />
F5<br />
CREATEXXXX<br />
<br />
Triggering this will give you three options:<br />
<br />
a) Recreate the XXXX file<br />
<br />
b) Check the XXXX file<br />
<br />
c) Re-index the XXXX file<br />
<br />
Select the first option to "RECREATE THE XXXX FILE" and wait until it completes.<br />
<br />
To verify if the above is done successfully run CHK.FILES (Recommended)in maintenance mode to check for corrupt files.<br />
<br />
F5<br />
CHK.FILES<br />
<br />
Alternatively if you know the name of the file that is damaged/corrupt, you could do the following<br />
<br />
(XXXX = File name)<br />
<br />
F5<br />
CHK.FILES XXXX<br />
<br />
== Fixing damaged index files (names starting with !) ==<br />
<br />
Whilst backing up or using NEOSYS the following error message might appear:<br />
<br />
"A Damaged file has been found.....<br />
Group format Error:<br />
OS File : !ADS<br />
Group# : 00000932<br />
Record length incorrect or frame linkage error.<br />
<br />
#Ensure that no-one is using NEOSYS<br />
#Log into NEOSYS on the server<br />
#Press F5 to get a TCL command box<br />
#Type REINDEXADS and press enter.<br />
#Wait until it finishes and you get back to the command box<br />
#Type OFF in the command box and you will quit NEOSYS.<br />
<br />
Other reindex commands are:<br />
<br />
*REINDEXACCOUNTS recreates !ACCOUNTS, !BATCHES and !VOUCHERS<br />
*REINDEXADDRESSES <br />
*REINDEXADS<br />
*REINDEXBOOKINGS recreates !BOOKING.ORDERS<br />
*REINDEXBRANDS<br />
*REINDEXCLIENTS<br />
*REINDEXINVS recreates !INVOICES<br />
*REINDEXJOBS<br />
*REINDEXMATERIALS<br />
*REINDEXPLANS<br />
*REINDEXPRODINVS recreates !PRODUCTION.INVOICES<br />
*REINDEXPRODORDERS recreates !PRODUCTION.ORDERS<br />
*REINDEXRATECARDS<br />
*REINDEXSCHEDULES<br />
*REINDEXSUPPLIERS<br />
*REINDEXTIMESHEETS<br />
*REINDEXVEHICLES<br />
<br />
REINDEXMEDIA does all the following<br />
*REINDEXPLANS<br />
*REINDEXSCHEDULES<br />
*REINDEXADS<br />
*REINDEXMATERIALS<br />
*REINDEXBOOKINGS<br />
<br />
REINDEXFILES does all the following<br />
*REINDEXCLIENTS<br />
*REINDEXBRANDS<br />
*REINDEXSUPPLIERS<br />
*REINDEXVEHICLES<br />
*REINDEXRATECARDS<br />
<br />
REINDEXPRODUCTION does all the following<br />
*REINDEXJOBS<br />
*REINDEXPRODORDERS<br />
*REINDEXPRODINVS<br />
*REINDEXTIMESHEETS<br />
<br />
REINDEXALL does all the following<br />
*REINDEXMEDIA<br />
*REINDEXPRODUCTION<br />
*REINDEXFILES<br />
*REINDEXINVS<br />
*REINDEXACCOUNTS<br />
*REINDEXADDRESSES<br />
<br />
== Fixing damaged files that have no process for recreating them ==<br />
<br />
Some damaged files can be rebuilt using NEOSYS utilities especially index files with filenames starting with !. Other damaged files like ''LOG20xx'' can be “fixed” to prevent NEOSYS crashes as follows <i>but some records will most probably be lost</i>. Depending on the file loss of a few records may not be too bad compared to restoring a database but the client should be informed and make the decision. Depending on the file it is usually best to lose the records. We can make a list of files that one can afford to lose records and those files that can be rebuilt programmatically from other files. Booking order texts they can lose records but inform them and especially the numbers mentioned in FIXFILE<br />
<br />
FIXFILE will not run if there are neosys services still running so before doing the FIXFILE command, shut down services from the Support menu or with the Global command:<br />
<br />
'''NOTE:''' If there are multiple datasets running on the server. Shut down the particular dataset which has got the problem:<br />
<br />
F5<br />
<br />
FIXFILE filename<br />
<br />
(Select option 1 to update the file)<br />
<br />
In case you get any Overwrite messages – type YES, as these are the actual files being updated.<br />
<br />
The only alternative is restore from a previous backup in this case losing a days work. Nasty, and even worse, it will be impossible to reproduce the days work and especially the exact serial numbers of critical documents like orders, invoices, receipts and payments advices.<br />
<br />
<br />
=== Using FIXFILE to repair corrupted files ===<br />
<br />
BEWARE: FIXFILE causes loss of data. If the data is critical then use of FIXFILE can be totally catastrophic without any warning.<br />
<br />
Using FIXFILE on some files is a guaranteed way to cause complete chaos for the users without them being aware of it until too late to do anything about it.<br />
<br />
Corrupt files will cause programs to abort every time they try to update that section of the file. Aborting programs causes possibly horrendous inconsistency in the database so it is important to stop all user activity and fix the corrupt file immediately.<br />
<br />
You can freely use FIXFILE on any file but it works by deleting any problematic data so cannot realistically be used on some files at all.<br />
<br />
FIXFILE cannot and does not recover any corrupted records therefore, for those files that have specific programs to rebuild them, FIXFILE is not the correct option.<br />
<br />
Why use FIXFILE at all since it causes loss of data?<br />
<br />
Many files do not have programs to rebuild them and for some of those files, using FIXFILE is a quick way to get the system back in operation BUT with missing records. Missing records causes various degrees of failure ranging from the odd document missing, totally misleading information like wrong account balances, or any kind of system failure.<br />
<br />
FIXFILE does not fix the consistency of information in the database. When the database is is being updated with a transaction, usually a series of files are updated for the one transaction. A damaged file causes the update program to abort in the middle of the series of updates. Therefore some of the updates are done and the remaining updates are not done. This means that the data in the database (even after fixing the corrupt file) is inconsistent.<br />
<br />
FIXFILE merely fixes the technical structure of the file so that any further program accesses to that portion of the file do not cause immediate program termination and consequent likely catastrophic database inconsistency.<br />
<br />
You must prevent anyone from accessing NEOSYS while FIXFILE is running.<br />
<br />
=== Fixing Damaged DEFINITIONS file ===<br />
<br />
==== Non-Solution ====<br />
<br />
You will probably not be able to login if the DEFINITIONS FILE is damaged. You can press Alt+S and type EXECUTE to get a TCL command box but this still doesnt help because you cannot use FIXFILE on DEFINITIONS.<br />
<br />
CAUTION: DO NOT USE FIXFILE TO TRY AND FIX THE DEFINITIONS FILE.<br />
<br />
DOUBLE CAUTION: IN CASE YOU DECIDE TO IGNORE THIS EXPECT ALL KINDS OF HORRIBLE PROBLEMS IN THE DATABASE REQUIRING A COMPLETE RESTORE FROM A GOOD BACKUP AFTER A FEW DAYS OF PAIN BECAUSE RANDOM OLD DATABASE UPGRADE/CONVERSIONS WILL BE PERFORMED *AGAIN* WITHOUT YOU KNOWING IT.<br />
<br />
==== Partial Restore ====<br />
<br />
You can copy recent DEFINITIONS.LK and DEFINITIONS.OV files from the DATA\datasetcode\GENERAL folder.<br />
<br />
CAUTION: All changes done in the Configuration File, Authorisation File, Users File and various other changes will be reverted to the date of the DEFINITIONS files being restored. If you are restoring from last nights backup or testdata then this will not be much but could cause serious confusion to people who have changed their passwords etc.<br />
<br />
==== Full Restore ====<br />
<br />
Restore from your latest backup losing all work done since that time and date.<br />
<br />
=== Preventing users from accessing NEOSYS in order to do maintenance or repairs ===<br />
<br />
On most systems you can simply stop the NEOSYS processes. On other systems where NEOSYS processes are automatically started in response to requests from the web, you need to disable the autostart by one of the following methods<br />
<br />
# Stop the autostart program/script<br />
# Put a file called NET.CFG with a single line saying AUTOSTART=NO in the neosys\neosys folder<br />
# Stop the IIS server<br />
# Stop/Pause the particular web in question<br />
<br />
== Dealing with damaged files that cannot be fixed ==<br />
<br />
If programmers are unable to fix the damage in a reasonably period of time and the damage is caused due to matters beyond NEOSYS control such as non-dedicated servers and power failures then data must be restored and client advised why they are going to suffer loss of data.<br />
<br />
THIS DOES NOT RELEASE NEOSYS SUPPORT STAFF FROM THE OBLIGATION TO PROACTIVELY INFORM THE CLIENT OF MEASURES TO PREVENT THE RECURRENCE OF THE EVENT.<br />
<br />
The following are the steps to follow:<br />
<br />
# Ascertain the cause of the damage to the database by looking at the internal logs<br />
# Create a new database from the damaged one as it will contain the up to date but damaged database.<br />
# Restore the database from the backup media so that the database is in the last good known state. <br />
# The client can see what work was done over the past couple of days from the damaged database and it will assist them to redo the work in the currently restored out of date main database.<br />
# Next discuss with the client about the cause of the damage and (a) what to do to prevent the damage occurring again (b) to agree a procedure to perform a manual backup in case the automatic one is not performed for any reason overnight.</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Handling_damaged_files&diff=680Handling damaged files2011-05-23T08:19:00Z<p>Sunny: /* Fixing damaged file that have a process to recreate them */</p>
<hr />
<div>== Symptoms ==<br />
<br />
"A Damaged file has been found..... ((the rest of this message to be completed)) <br />
Group format Error:<br />
OS File : BOOKING.TEXTS<br />
Group# : 00000932<br />
Record length incorrect or frame linkage error.<br />
<br />
== Cause ==<br />
Rare but nasty problem on server 99% caused by power failure, killing NEOSYS or server hardware or operating system failure.<br />
<br />
*Did somebody kill NEOSYS processes to reboot the server or any other reason?<br />
*Was there a power cut?<br />
*Any expected or unexpected reboots in the server log? (see Event Viewer > System Log)<br />
*Enough disk free space especially on servers not dedicated to NEOSYS?<br />
<br />
== Solution==<br />
<br />
Damaged files, when detected, cause an immediate termination of the currently executing program/user request and a restart of the process is involved. Some damaged files are automatically fixed during restart. Although the process "restarts" it may be internally corrupted in some way and it is advisable to close it completely and start or allow another process to start automatically.<br><br><br />
However, the solution always depends on the cause and usually often requires aggressive interrogation to discover the cause.<br />
<br />
== Recovery==<br />
<br />
It is URGENT to stop using NEOSYS and fix the damaged file because it will cause NEOSYS to crash everytime it happens to update that part of the file. NEOSYS crashing while updating often produces unrecoverable inconsistencies in the database that can only be fixed by programmers sitting for hours trying to edit the database .... or by restoring from a backup causing loss of work.<br />
<br />
See the following sections how to patch the damaged files.<br />
<br />
== Files that are automatically fixed ==<br />
<br />
*LISTS<br />
*LOCKS<br />
*!INDEXING<br />
<br />
The above files are automatically checked for corruption (and initialised to empty if so) when you <br />
startup a NEOSYS process and do not require any manual intervention apart from locating and eliminating the initial cause of the damage.<br />
<br />
If the !INDEXING file was damaged then you should also do REINDEXALL to reinstate any possibly missing index entries, but since this will take a long time<br />
you should do this when everybody is off the system in the evening probably. A few missing index entries may only mean some records missing from some reports which may or may not be seriously inconvenient. It is a temporary file that should not hold any records for longer than it takes to update the various indexes immediately when the user saves any document.<br />
<br />
Each process has its own LISTS file, so damage is limited to one process for the LISTS file. The process number can be seen in the error message. for example:<br />
<br />
Process=7<br />
<br />
You can also see the process number on the server screen. For example here is a process 2.<br />
<br />
13:17:31 TESTDB NEOS0002 0 Listening 7 hours, 49 mins ...<br />
<br />
The LISTS file is a temporary file for sorting records into order for reports, popups etc. Therefore any damage usually causes no real inconvenience apart from the failed report or popup on which the user might receive the "damaged LISTS file" message.<br />
<br />
The error message would appear as follows :<br />
<br />
SYSTEM ERROR:<br />
An internal file LISTS was found<br />
to be damaged and has been patched.<br />
INFORM YOUR TECHNICAL SUPPORT<br><br />
SOME DATA HAS PROBABLY BEEN LOST<br />
AND THE NEOSYS SYSTEM MAY MALFUNCTION<br><br />
Server=NEOSYS-SERVER<br />
Install=D:\NEOSYS\NEOSYS\<br />
Version=17:16:04 23 JAN 2011<br />
Database=1D68EE63 ADLINED<br />
Process=2<br />
<br />
The error could also appear as follows :<br />
<br />
A DAMAGED FILE HAS BEEN FOUND.<br />
YOU MUST GIVE THE FOLLOWING MESSAGE TO TECHNICAL SUPPORT NOW.<br />
DO NOT CONTINUE USING THE SYSTEM!<br><br />
Group Format Error:<br />
File : LISTS<br />
Group # : 00000014<br />
Record length incorrect or frame linkage error.<br />
Server=NEOSYS-SERVER<br />
Install=D:\NEOSYS\NEOSYS\<br />
Version=17:16:04 23 JAN 2011<br />
Database=1D68EE63 ADLINED<br />
Process=2<br />
<br />
Please note that both the above messages mean the same.<br />
<br />
== Fixing damaged file that have a process to recreate them ==<br />
<br />
ADS file can be recreated with F5 CREATEADS<br />
<br />
ANALYSIS file can be recreated with F5 CREATEANALYSIS<br />
<br />
BRANDS files can be recreated with F5 CREATEBRANDS<br />
<br />
If the file is actually damaged it might be necessary to initialise it first using CLEARFILE filename.<br />
<br />
Procedure to run CREATEXXXX (Where XXXX = ADS, ANALYSIS OR BRANDS)<br />
<br />
NOTE: Stop all the processes before doing the below procedure.<br />
<br />
Login to maintenance<br />
<br />
F5<br />
CREATEXXXX<br />
<br />
Triggering this will give you three options:<br />
<br />
a) Recreate the XXXX file<br />
<br />
b) Check the XXXX file<br />
<br />
c) Re-index the XXXX file<br />
<br />
Select the first option to "RECREATE THE XXXX FILE" and wait until it completes.<br />
<br />
To verify if the above is done successfully run CHK.FILES (Recommended)in maintenance mode to check for corrupt files.<br />
<br />
F5<br />
CHK.FILES<br />
<br />
Alternatively if you know the name of the file that is damaged/corrupt, you could do the following<br />
<br />
(XXXX = File name)<br />
<br />
F5<br />
CHK.FILES XXXX<br />
<br />
== Fixing damaged index files (names starting with !) ==<br />
<br />
Whilst backing up or using NEOSYS the following error message might appear:<br />
<br />
"A Damaged file has been found.....<br />
Group format Error:<br />
OS File : !ADS<br />
Group# : 00000932<br />
Record length incorrect or frame linkage error.<br />
<br />
#Ensure that no-one is using NEOSYS<br />
#Log into NEOSYS on the server<br />
#Press F5 to get a TCL command box<br />
#Type REINDEXADS and press enter.<br />
#Wait until it finishes and you get back to the command box<br />
#Type OFF in the command box and you will quit NEOSYS.<br />
<br />
Other reindex commands are:<br />
<br />
*REINDEXACCOUNTS recreates !ACCOUNTS, !BATCHES and !VOUCHERS<br />
*REINDEXADDRESSES <br />
*REINDEXADS<br />
*REINDEXBOOKINGS recreates !BOOKING.ORDERS<br />
*REINDEXBRANDS<br />
*REINDEXCLIENTS<br />
*REINDEXINVS recreates !INVOICES<br />
*REINDEXJOBS<br />
*REINDEXMATERIALS<br />
*REINDEXPLANS<br />
*REINDEXPRODINVS recreates !PRODUCTION.INVOICES<br />
*REINDEXPRODORDERS recreates !PRODUCTION.ORDERS<br />
*REINDEXRATECARDS<br />
*REINDEXSCHEDULES<br />
*REINDEXSUPPLIERS<br />
*REINDEXTIMESHEETS<br />
*REINDEXVEHICLES<br />
<br />
REINDEXMEDIA does all the following<br />
*REINDEXPLANS<br />
*REINDEXSCHEDULES<br />
*REINDEXADS<br />
*REINDEXMATERIALS<br />
*REINDEXBOOKINGS<br />
<br />
REINDEXFILES does all the following<br />
*REINDEXCLIENTS<br />
*REINDEXBRANDS<br />
*REINDEXSUPPLIERS<br />
*REINDEXVEHICLES<br />
*REINDEXRATECARDS<br />
<br />
REINDEXPRODUCTION does all the following<br />
*REINDEXJOBS<br />
*REINDEXPRODORDERS<br />
*REINDEXPRODINVS<br />
*REINDEXTIMESHEETS<br />
<br />
REINDEXALL does all the following<br />
*REINDEXMEDIA<br />
*REINDEXPRODUCTION<br />
*REINDEXFILES<br />
*REINDEXINVS<br />
*REINDEXACCOUNTS<br />
*REINDEXADDRESSES<br />
<br />
== Fixing damaged files that have no process for recreating them ==<br />
<br />
Some damaged files can be rebuilt using NEOSYS utilities especially index files with filenames starting with !. Other damaged files like ''LOG20xx'' can be “fixed” to prevent NEOSYS crashes as follows <i>but some records will most probably be lost</i>. Depending on the file loss of a few records may not be too bad compared to restoring a database but the client should be informed and make the decision. Depending on the file it is usually best to lose the records. We can make a list of files that one can afford to lose records and those files that can be rebuilt programmatically from other files. Booking order texts they can lose records but inform them and especially the numbers mentioned in FIXFILE<br />
<br />
FIXFILE will not run if there are neosys services still running so before doing the FIXFILE command, shut down services from the Support menu or with the Global command:<br />
<br />
'''NOTE:''' If there are multiple datasets running on the server. Shut down the particular dataset which has got the problem:<br />
<br />
F5<br />
<br />
FIXFILE filename<br />
<br />
(Select option 1 to update the file)<br />
<br />
In case you get any Overwrite messages – type YES, as these are the actual files being updated.<br />
<br />
The only alternative is restore from a previous backup in this case losing a days work. Nasty, and even worse, it will be impossible to reproduce the days work and especially the exact serial numbers of critical documents like orders, invoices, receipts and payments advices.<br />
<br />
<br />
=== Using FIXFILE to repair corrupted files ===<br />
<br />
BEWARE: FIXFILE causes loss of data. If the data is critical then use of FIXFILE can be totally catastrophic without any warning.<br />
<br />
Using FIXFILE on some files is a guaranteed way to cause complete chaos for the users without them being aware of it until too late to do anything about it.<br />
<br />
Corrupt files will cause programs to abort every time they try to update that section of the file. Aborting programs causes possibly horrendous inconsistency in the database so it is important to stop all user activity and fix the corrupt file immediately.<br />
<br />
You can freely use FIXFILE on any file but it works by deleting any problematic data so cannot realistically be used on some files at all.<br />
<br />
FIXFILE cannot and does not recover any corrupted records therefore, for those files that have specific programs to rebuild them, FIXFILE is not the correct option.<br />
<br />
Why use FIXFILE at all since it causes loss of data?<br />
<br />
Many files do not have programs to rebuild them and for some of those files, using FIXFILE is a quick way to get the system back in operation BUT with missing records. Missing records causes various degrees of failure ranging from the odd document missing, totally misleading information like wrong account balances, or any kind of system failure.<br />
<br />
FIXFILE does not fix the consistency of information in the database. When the database is is being updated with a transaction, usually a series of files are updated for the one transaction. A damaged file causes the update program to abort in the middle of the series of updates. Therefore some of the updates are done and the remaining updates are not done. This means that the data in the database (even after fixing the corrupt file) is inconsistent.<br />
<br />
FIXFILE merely fixes the technical structure of the file so that any further program accesses to that portion of the file do not cause immediate program termination and consequent likely catastrophic database inconsistency.<br />
<br />
You must prevent anyone from accessing NEOSYS while FIXFILE is running.<br />
<br />
=== Fixing Damaged DEFINITIONS file ===<br />
<br />
==== Non-Solution ====<br />
<br />
You will probably not be able to login if the DEFINITIONS FILE is damaged. You can press Alt+S and type EXECUTE to get a TCL command box but this still doesnt help because you cannot use FIXFILE on DEFINITIONS.<br />
<br />
CAUTION: DO NOT USE FIXFILE TO TRY AND FIX THE DEFINITIONS FILE.<br />
<br />
DOUBLE CAUTION: IN CASE YOU DECIDE TO IGNORE THIS EXPECT ALL KINDS OF HORRIBLE PROBLEMS IN THE DATABASE REQUIRING A COMPLETE RESTORE FROM A GOOD BACKUP AFTER A FEW DAYS OF PAIN BECAUSE RANDOM OLD DATABASE UPGRADE/CONVERSIONS WILL BE PERFORMED *AGAIN* WITHOUT YOU KNOWING IT.<br />
<br />
==== Partial Restore ====<br />
<br />
You can copy recent DEFINITIONS.LK and DEFINITIONS.OV files from the DATA\datasetcode\GENERAL folder.<br />
<br />
CAUTION: All changes done in the Configuration File, Authorisation File, Users File and various other changes will be reverted to the date of the DEFINITIONS files being restored. If you are restoring from last nights backup or testdata then this will not be much but could cause serious confusion to people who have changed their passwords etc.<br />
<br />
==== Full Restore ====<br />
<br />
Restore from your latest backup losing all work done since that time and date.<br />
<br />
=== Preventing users from accessing NEOSYS in order to do maintenance or repairs ===<br />
<br />
On most systems you can simply stop the NEOSYS processes. On other systems where NEOSYS processes are automatically started in response to requests from the web, you need to disable the autostart by one of the following methods<br />
<br />
# Stop the autostart program/script<br />
# Put a file called NET.CFG with a single line saying AUTOSTART=NO in the neosys\neosys folder<br />
# Stop the IIS server<br />
# Stop/Pause the particular web in question<br />
<br />
== Dealing with damaged files that cannot be fixed ==<br />
<br />
If programmers are unable to fix the damage in a reasonably period of time and the damage is caused due to matters beyond NEOSYS control such as non-dedicated servers and power failures then data must be restored and client advised why they are going to suffer loss of data.<br />
<br />
THIS DOES NOT RELEASE NEOSYS SUPPORT STAFF FROM THE OBLIGATION TO PROACTIVELY INFORM THE CLIENT OF MEASURES TO PREVENT THE RECURRENCE OF THE EVENT.<br />
<br />
The following are the steps to follow:<br />
<br />
# Ascertain the cause of the damage to the database by looking at the internal logs<br />
# Create a new database from the damaged one as it will contain the up to date but damaged database.<br />
# Restore the database from the backup media so that the database is in the last good known state. <br />
# The client can see what work was done over the past couple of days from the damaged database and it will assist them to redo the work in the currently restored out of date main database.<br />
# Next discuss with the client about the cause of the damage and (a) what to do to prevent the damage occurring again (b) to agree a procedure to perform a manual backup in case the automatic one is not performed for any reason overnight.</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Configuring_NEOSYS_Generally&diff=678Configuring NEOSYS Generally2011-05-16T07:06:18Z<p>Sunny: /* Clearing files in database (done when you want to clean an old database) */</p>
<hr />
<div>=== Clearing files in database (done when you want to clean an old database) ===<br />
<br />
This is to be done incase you want to clean an old database or clean a training database so that a client can enter fresh data. These commands DO NOT clear down the whole database and hence for new installations you need to download a fresh BACKUP.ZIP file from the NEOSYS website.<br />
<br />
Clear data F5 CLEAROP (only clears transactions not reference files)<br />
<br />
Clear suppliers F5 CLEARFILE SUPPLIERS<br />
<br />
Clear Vehicles F5 CLEARFILE VEHICLES<br />
<br />
Flush Index F5 FLUSH.INDEX<br />
<br />
Clear all F5 CLEARALL (rather nasty command because clears all reference files as well)<br />
<br />
Clear Payment Instruction F5 CLEARFIELD CLIENTS PAYMENT_INSTRUCTIONS (only clears the payment instruction from the client and brand file)<br />
<br />
=== Configuring backup procedures ===<br />
<br />
See the System Configuration File on the NEOSYS Support Menu.<br />
<br />
==== Non-Liability for Backup ====<br />
<br />
{{Non-Liability For Backup}}<br />
<br />
==== Backing up the Images folder ====<br />
<br />
The Images folder under the NEOSYS installation is used to upload images/artworks/files from the Job File section and hence needs to be backed up. NEOSYS will automatically backup this Images folder to the USB drive or other location (specified for the usual data backup) once a week. To configure this backup, RSYNC needs to have been installed during the initial installation.<br />
<br />
In case we need to configure the Images folder backup at another location other than the usual daily backup location than we need to edit:<br />
<br />
line 12 - and specify the Drive of the location to be backed up to. eg. E or F<br />
<br />
=== Copying a single record from one database to another ===<br />
<br />
You need to know the file name and record key of the record to be copied.<br />
<br />
In this case the file is DEFINITIONS and the key is AGENCY.PARAMS<br />
<br />
You can invent any old style 8.3 filename instead of C:\AGP.DAT in the following example<br />
<br />
On the source computer:<br />
<br />
F5<br />
COPY DEFINITIONS AGENCY.PARAMS TO: (DOS C:\AGP.DAT)<br />
<br />
On the target computer:<br />
<br />
F5<br />
COPY DOS C:\AGP.DAT (ON) TO: (DEFINITIONS AGENCY.PARAMS)<br />
<br />
The (O) option is required to force overwrite of the existing <br />
<br />
The (N) option means only copy if the target already exists. It is advisable to use it when you know that the target already exists to avoid misspellings in the command. It must be omitted if the target doesnt exist.<br />
<br />
== Allowing users temporary login as NEOSYS in maintenance mode ==<br />
<br />
#Get them to login with any name even NEOSYS<br />
#Get the to enter "?" for the pass without the quotes<br />
#NEOSYS will give them a lock like "NEOSYS 123456" which they must give you. You should not log out until the next step is completed<br />
#Follow the NEOSYS lock/key procedure using the full contents of the lock including the user name<br />
(to allow access EXCEPT access to authorisation screen use a special number (not documented here) as the last number of the initial command)<br />
#Give them the key and get them to enter and proceed<br />
<br />
== Configuring upload of photoshop "cs2" jpg files ==<br />
<br />
Photoshop version "cs2" produces jpg files that cannot be viewed in Internet Explorer.<br />
<br />
A solution is to rename the files extension from .jpg to .psjpg before uploading.<br />
<br />
"psjpg" files are an invention of NEOSYS and IIS must be configured to handle .psjpg files as follows:<br />
<br />
Windows Server 2003 (doesnt work on XP)<br />
<br />
#Computer Management, Internet Information Server, Properties<br />
#Click MIME Types<br />
#Click New<br />
#Extension: psjpg<br />
#MIME Type: application/photoshop<br />
#Click OK,OK,OK<br />
#Restart IIS (Right click, All Tasks, Restart)<br />
<br />
== Enabling backup servers to access backed-up servers ==<br />
<br />
This relates to a common procedure used by NEOSYS to provide automatic nightly synchronisation/backups between servers for multi-office configurations. For more information see<br />
http://itwiki.neosys.com/index.php/Setting_up_remote_backup<br />
<br />
Αccording to this procedure, backup processes are actually initiated and run on a "backup server" using a "pull" concept. The "backed-up server" serves the data (usually using an rsync service) to the backup server on request. They do not use a "push" concept.<br />
<br />
This means that backup servers need to be able to automatically login to the backed-up servers. On most backup servers a NEOSYS cygwin script called autologin.sh has been installed. This helps you configure the backup server and backed-up server.<br />
<br />
Normally you only need to run autologin.sh once per pair of backup and backed-up servers but sometimes the configuration is lost (particularly when NEOSYS is upgraded) and it must be repeated.<br />
<br />
=== Using autologin.sh ===<br />
<br />
#Asks you for the username and hostname<br />
#Copies an identity file from the backup server to the backed up server.<br><b>This requires you to enter the administrator or root password.</b><br />
#Logs you in to the backed up server's cygwin/bash command line.<br><b>This requires you to enter the password again.</b><br />
#YOU then type a series of commands to install the identity file and finally exit the command console.<br>The series of commands that you must type are shown on screen by autologin.sh<br />
#Logs you in to the backed up server's cygwin/bash command line.<br><b>This time, you should NOT be required to enter a password.</b><br />
#YOU type "exit" to quit the backed up server's command line.<br />
<br />
=== Running ./autologin.sh ===<br />
<br />
In cygwin on the backup server, type<br />
<br />
./autologin.sh<br />
<br />
... and follow instructions on screen. The system will ask you once the password to the target server to transfer an identity file and once again to access the command line of the target server from where you must follow a set of instructions in order to load the identity file properly.<br />
<br />
The username is usually administrator for windows server targets.<br />
<br />
The hostname can be found in backup email logs or in the CONFIG.CMD file in the backup server.<br />
<br />
There are often two alternative hostnames. Try the first one first. If you succeed with the first then there is no need to try the second.<br />
<br />
Sometimes one of the host names is based on alternative network access methods like hamachi which uses ip addresses starting with "5." and requires hamachi service to be running in both servers and this sometimes is dependent on being logged in and correct setup of hamachi. You can ping the host names to discover the ip numbers of course.<br />
<br />
Follow the instructions on the screen VERY carefully.<br />
<br />
=== The edit step ===<br />
<br />
The last step will enter the nano editor where you should do the following:<br />
<br />
If present, delete the word neosys near the end of the last line of the file. The last bit of the last line will refer to some user and host that you are enabling access FROM<br />
<br />
BE CAREFUL NOT TO TRIGGER THE AUTOMATIC LINE BREAKING IN NANO because line breaking into two or more lines is automatically triggered when you add characters to long lines. it is not triggered if you just delete characters. If you do cause a line break then quit the editor WITHOUT saving and try again or then use the editor to rejoin the two lines. Note that pressing Alt+L will turn long line breaking off and on which avoids the problem in the first place.<br />
<br />
Press Ctrl+X to exit the editor</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Moving_NEOSYS&diff=676Moving NEOSYS2011-05-12T14:13:14Z<p>Sunny: </p>
<hr />
<div>=== Moving NEOSYS to new servers ===<br />
<br />
Make sure you disable old systems BEFORE you enable new systems.<br />
<br />
You cannot count on users to pay attention to WHICH system they are using so its up to you to prevent access to the old system PRIOR to opening a new system for them.<br />
<br />
Failure to follow this procedure OFTEN results in chaos in the clients procedures. Missing invoices, etc etc etc.<br />
<br />
<br />
==== Changing drive letter to match old drive letter ====<br />
<br />
[[Image:changepartitiondriveletter.png]]<br />
<br />
<br />
==== Backup and restore of IIS configuration ====<br />
<br />
[[Image:backupiis.png]]<br />
<br />
<br />
==== How to deauthorisation a NEOSYS installation ====<br />
<br />
Deauthorisation removes the authorisation and gives a pair of "authorisation numbers" that can be run through a check to prove that deauthorisation has been done.<br />
<br />
After deauthorisation you cannot use NEOSYS. If you try then it will ask for authorisation again and you cannot use the original authorisation number to reauthorise it.<br />
<br />
In NEOSYS Maintenance mode press F5 then type<br />
<br />
DEAUTHORISE<br />
<br />
... and answer all the questions properly.<br />
<br />
At the final stage it will give you the "deauthorisation numbers" which consist of the original computer number plus another number. These numbers should not be lost and should be given to NEOSYS who will verify they are correct.<br />
<br />
<br />
=== Reinstating live system from backup system and shifting back ===<br />
<br />
This process should be done only when all the users are offline.<br />
<br />
To move the data form live to backup server and restore it back, follow the steps mention below:<br />
<br />
Before restoring the data from live server to backup server and viceversa, do a manual back (If Required) and run the '''backup.adlined''' task on backup server.<br />
<br />
====Steps to stop adline dubai process to start:====<br />
<br />
# Un-ticked automatic backup from the configuration file at adline dubai server.<br />
# Renamed Global.end.temp to Global.end<br />
# Disabled schedule task (Copy adline2adltest & start adlined)<br />
# Disabled backup.adlined task at ADLINED2 server to avoid backup of adlined > adlined2<br />
# After doing this start adlined processes at ADLINED2 server and tick the automatic backup option in the configure file. <br />
# Email client giving the new URL to access NEOSYS.<br />
# Ask the IT guy to plug-in the backup USB to the server and configure the drive letter on the configuration file in neosys. <br />
<br />
====Steps to restore adlined dataset back to adlined server (Live server)====<br />
<br />
ATTENTION: Send a mail to the client staff, saying neosys will be down from XXXX hours and they should logout from neosys before the XXXX hours and save their work. <br />
If possible co-ordinate with IT guy/Responsible person to follow up and make sure that users logout on the decided time. Once all the users are offline, Block all users to access neosys.<br />
<br />
#Take a manual backup of the dataset you want to move to a removable drive (Flash/USB drive)<br />
#Once the backup is completed, go to the configuration file and un-tick the automatic backup from the configuration file.<br />
#Now unplug the USB from the backup server and plug it on main server.<br />
#Before doing a restore read the below note very carefully.<br />
#Now log in to maintenance process and go to General > Backup & Data Management, select Restore from disk or diskette (which is no 4), select the back drive and follow the prompts ahead.<br />
#Now enable all the task disabled which were disabled on adlined server earlier and enable backup.adlined schedule task on adlined2 server.<br />
<br />
'''NOTE:'''<br />
<br />
REMEMBER THAT RESTORE = first DELETE! and then RESTORE<br />
<br />
'''Chat for reference:'''<br />
<br />
DELETE MEANS YOU SHOULD BE FRIGHTENED >> AND THEREFORE TAKE A COPY<br />
<br />
In this case you KNOW you have a good working copy of the data on the backup server so DELETING+RESTORE on the main server is not very frightening .. but STILL .. play SAFE .. take a COPY OF WHAT YOU DELETE DURING RESTORE maybe you can add this chat to wiki as well as my email</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Configuring_IIS&diff=675Configuring IIS2011-05-10T06:58:48Z<p>Sunny: </p>
<hr />
<div>After you have installed all the NEOSYS program files you need to configure IIS so that you can operate NEOSYS. Instructions are below.<br />
<br />
== Configuring IIS for Windows 2008 ==<br />
<br />
==== Installing IIS ====<br />
<br />
First install IIS from Control Panel > Programs & Features > Turn Windows Features ON or OFF > Add Roles:<br />
<br />
[[image:iis1.jpg]]<br />
<br />
On the window that pops up click on next and you will get this screen, tick Web Server (IIS) - on the prompt click on Add Required Resources and then on Next:<br />
<br />
[[image:iis2.jpg]]<br />
<br />
On the next window, click on next until you get this window - tick ASP and ISAPI Extensions:<br />
<br />
[[image:iis3.jpg]]<br />
<br />
Click on Next and Finish<br />
<br />
==== Configuring IIS ====<br />
After successfully installing IIS, go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Internet Information Services (IIS) > Machine Name > Sites > Default Website:<br />
<br />
The first step is to create a virtual directory called neosys linked to D:\neosys\neosys.net:<br />
<br />
[[image:iis4.jpg]]<br />
<br />
Within the above neosys web site folder create a virtual directory called data linked to D:\neosys\data:<br />
<br />
[[image:iis5.jpg]]<br />
<br />
In the IIS Default Web Site create a another virtual directory called neosys.w3c linked to D:\neosys\neosys.w3c (only if timesheets for mac is required):<br />
<br />
[[image:iis6.jpg]]<br />
<br />
To allow file uploads – create a folder IMAGES under D:\neosys and within the neosys web site folder create a virtual directory called images linked to D:\neosys\images:<br />
<br />
[[image:iis7.jpg]]<br />
<br />
After you add all virtual directories the tree map of the Default Website should look as follows:<br />
<br />
[[image:iis8.jpg]]<br />
<br />
To configure file uploads besides adding the images directory, go under IIS > Default Website > neosys – click on Handler Mappings and delete the ISAPI you see there:<br />
<br />
[[image:iis9a.jpg]]<br />
<br />
Thereafter click on Add Script Map and fill in the details as follows – Request path: *.dll , Executable: D:\neosys\neosys.net\NEOSYS\dll\upload.dll , Name: ISAPI (once you click on OK click on YES to the confirmation box)<br />
<br />
[[image:iis9b.jpg]]<br />
<br />
Edit the hosts file under c:\windows\system32\drivers\etc\ - delete the # sign next to 127.0.0.1 localhost and incluide the # sign before ::1 localhost<br />
<br />
[[image:iis10.jpg]]</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Configuring_NEOSYS_Finance_System&diff=638Configuring NEOSYS Finance System2011-02-07T10:59:12Z<p>Sunny: </p>
<hr />
<div>== Deleting unwanted historical unposted batches prior to commencing finance module ==<br />
<br />
This is irreversible so take a backup in case of errors. It is advisable to do this on test data first and then on main data. The process only deletes unposted records. At the time of writing, AF found no way to verify which exact version could be categorised as before or after 2009 and hence he suggests you should do this in test data first.<br />
<br />
The instructions say LT 2008.12 or LT 0812 - "LT" means LESS THAN ie NOT including the period mentioned so it is the first period you want to KEEP!<br />
<br />
=== NEOSYS versions after mid-2009 ===<br />
<br />
==== Clearing both posted & unposted items ====<br />
<br />
F5<br />
SELECT BATCHES WITH YEAR_PERIOD LT "2008.12"<br />
DELETE BATCHES<br />
FLUSH.INDEX<br />
SELECT VOUCHERS WITH YEAR_PERIOD LT "0812"<br />
DELETE VOUCHERS<br />
FLUSH.INDEX<br />
<br />
UTIL - this prepares maintenance to run the next command<br />
CHK.VINDEX ("0" for all periods and delete all missing voucher entries and clear all empty index records)<br />
FLUSH.INDEX<br />
CLEARFILE BALANCES <br />
<br />
==== Clearing unposted items only ====<br />
<br />
F5<br />
SELECT BATCHES WITH YEAR_PERIOD LT "2008.12" AND WITH UNPOSTED<br />
DELETE BATCHES<br />
FLUSH.INDEX<br />
SELECT VOUCHERS WITH YEAR_PERIOD LT "0812" AND WITH LASTACTION "D"<br />
DELETE VOUCHERS<br />
FLUSH.INDEX<br />
<br />
UTIL - this prepares maintenance to run the next command<br />
CHK.VINDEX ("0" for all periods and delete all missing voucher entries and clear all empty index records)<br />
FLUSH.INDEX<br />
<br />
=== NEOSYS versions before mid-2009 ===<br />
<br />
==== Clearing both posted & unposted items ====<br />
<br />
F5<br />
SELECT BATCHES WITH YEAR_PERIOD LT "08.12"<br />
DELETE BATCHES<br />
FLUSH.INDEX<br />
SELECT VOUCHERS WITH YEAR_PERIOD LT "0812"<br />
DELETE VOUCHERS<br />
FLUSH.INDEX<br />
<br />
UTIL - this prepares maintenance to run the next command<br />
CHK.INDEX ("0" for all periods and delete all missing voucher entries and clear all empty index records)<br />
FLUSH.INDEX<br />
CLEARFILE BALANCES <br />
<br />
==== Clearing unposted items only ====<br />
<br />
F5<br />
SELECT BATCHES WITH YEAR_PERIOD LT "08.12" AND WITH UNPOSTED<br />
DELETE BATCHES<br />
FLUSH.INDEX<br />
SELECT VOUCHERS WITH YEAR_PERIOD LT "0812" AND WITH LASTACTION "D"<br />
DELETE VOUCHERS<br />
FLUSH.INDEX<br />
<br />
UTIL - this prepares maintenance to run the next command<br />
CHK.INDEX ("0" for all periods and delete all missing voucher entries and clear all empty index records)<br />
FLUSH.INDEX<br />
<br />
== Deleting selected vouchers from open item statements ==<br />
<br />
This may be useful in fixing some types of cross check balance errors. It must be done in maintenance mode using F5.<br />
<br />
=== Method 1 - Recreation ===<br />
<br />
Delete all and rebuild using CHK.ALLOC. This method is the easiest but takes longer and cannot be done while users are online.<br />
<br />
AAAA is the ORIGINAL account no and CCC is the company code<br />
<br />
DELETE VOUCHER.INDEX *AAAA*CCC<br />
<br />
CHK.ALLOC<br />
<br />
=== Method 2 - Editing ===<br />
<br />
Direct editing using Ctrl+G, Ctrl+D, F9 and Esc.<br />
<br />
WARNING: You can easily delete the wrong entries. If so then use Method 2 to recover.<br />
<br />
WARNING: Do not remain in edit long if there are users online who might post to this account and company otherwise their posting will hang and maybe crash resulting in unrecoverably corrupt finance data requiring restoration of a backup and loss of all users work since the last backup.<br />
<br />
After you list the vouchers in step 2 you will be able to see which ones (lines) you need to delete. The order in the edit is the same as the order in the list. Delete in reverse order, last lines first so the order is unchanged until you delete a line.<br />
<br />
AAAA is the ORIGINAL account no and CCC is the company code<br />
<br />
SELECTVOUCHERS AAAA 1<br />
LIST VOUCHERS DATE VOUCHER_PERIOD<br />
ED VOUCHERS *AAAA*C<br />
<br />
<br />
==How to delete a company from the dataset?==<br />
<br />
This procedure can only be done by NEOSYS staff in the maintenance mode. <br />
<br />
Login to the maintenance window.<br />
<br />
Go to Finance menu, select the company file. To get the company details on the screen enter the code in the company cod field.<br />
<br />
To delete the company press Alt + D and confirm once again after you get the screens as shown below:<br />
<br />
[[File:Company_file.jpg]]<br />
<br />
Once you confirm the above step, system will pop-up a message with the three options as below:<br />
<br />
[[File:Company_file1.jpg]]<br />
<br />
Select the appropriate option to delete the company.</div>Sunnyhttps://techwiki.neosys.com/index.php?title=File:Company_file1.jpg&diff=637File:Company file1.jpg2011-02-07T10:58:12Z<p>Sunny: </p>
<hr />
<div></div>Sunnyhttps://techwiki.neosys.com/index.php?title=File:Company_file.jpg&diff=636File:Company file.jpg2011-02-07T10:56:37Z<p>Sunny: </p>
<hr />
<div></div>Sunnyhttps://techwiki.neosys.com/index.php?title=Handling_damaged_files&diff=634Handling damaged files2011-01-16T07:40:54Z<p>Sunny: /* Fixing damaged files that have no process for recreating them */</p>
<hr />
<div>== Symptoms ==<br />
<br />
"A Damaged file has been found..... ((the rest of this message to be completed)) <br />
Group format Error:<br />
OS File : BOOKING.TEXTS<br />
Group# : 00000932<br />
Record length incorrect or frame linkage error.<br />
<br />
== Cause ==<br />
Rare but nasty problem on server 99% caused by power failure, killing NEOSYS or server hardware or operating system failure.<br />
<br />
*Did somebody kill NEOSYS processes to reboot the server or any other reason?<br />
*Was there a power cut?<br />
*Any expected or unexpected reboots in the server log? (see Event Viewer > System Log)<br />
*Enough disk free space especially on servers not dedicated to NEOSYS?<br />
<br />
== Solution==<br />
<br />
Damaged files, when detected, cause an immediate termination of the currently executing program/user request and a restart of the process is involved. Some damaged files are automatically fixed during restart. Although the process "restarts" it may be internally corrupted in some way and it is advisable to close it completely and start or allow another process to start automatically.<br><br><br />
However, the solution always depends on the cause and usually often requires aggressive interrogation to discover the cause.<br />
<br />
== Recovery==<br />
<br />
It is URGENT to stop using NEOSYS and fix the damaged file because it will cause NEOSYS to crash everytime it happens to update that part of the file. NEOSYS crashing while updating often produces unrecoverable inconsistencies in the database that can only be fixed by programmers sitting for hours trying to edit the database .... or by restoring from a backup causing loss of work.<br />
<br />
See the following sections how to patch the damaged files.<br />
<br />
== Files that are automatically fixed ==<br />
<br />
*LISTS<br />
*LOCKS<br />
*!INDEXING<br />
<br />
The above files are automatically checked for corruption (and initialised to empty if so) when you <br />
startup a NEOSYS process and do not require any manual intervention apart from locating and eliminating the initial cause of the damage.<br />
<br />
If the !INDEXING file was damaged then you should also do REINDEXALL to reinstate any possibly missing index entries, but since this will take a long time<br />
you should do this when everybody is off the system in the evening probably. A few missing index entries may only mean some records missing from some reports which may or may not be seriously inconvenient. It is a temporary file that should not hold any records for longer than it takes to update the various indexes immediately when the user saves any document.<br />
<br />
Each process has its own LISTS file, so damage is limited to one process for the LISTS file. The process number can be seen in the error message. for example:<br />
<br />
Process=7<br />
<br />
You can also see the process number on the server screen. For example here is a process 2.<br />
<br />
13:17:31 TESTDB NEOS0002 0 Listening 7 hours, 49 mins ...<br />
<br />
The LISTS file is a temporary file for sorting records into order for reports, popups etc. Therefore any damage usually causes no real inconvenience apart from the failed report or popup on which the user might receive the "damaged LISTS file" message.<br />
<br />
== Fixing damaged file that have a process to recreate them ==<br />
<br />
ADS file can be recreated with F5 CREATEADS<br />
<br />
ANALYSIS file can be recreated with F5 CREATEANALYSIS<br />
<br />
BRANDS files can be recreated with F5 CREATEBRANDS<br />
<br />
If the file is actually damaged it might be necessary to initialise it first using CLEARFILE filename.<br />
<br />
== Fixing damaged index files (names starting with !) ==<br />
<br />
Whilst backing up or using NEOSYS the following error message might appear:<br />
<br />
"A Damaged file has been found.....<br />
Group format Error:<br />
OS File : !ADS<br />
Group# : 00000932<br />
Record length incorrect or frame linkage error.<br />
<br />
#Ensure that no-one is using NEOSYS<br />
#Log into NEOSYS on the server<br />
#Press F5 to get a TCL command box<br />
#Type REINDEXADS and press enter.<br />
#Wait until it finishes and you get back to the command box<br />
#Type OFF in the command box and you will quit NEOSYS.<br />
<br />
Other reindex commands are:<br />
<br />
*REINDEXACCOUNTS recreates !ACCOUNTS, !BATCHES and !VOUCHERS<br />
*REINDEXADDRESSES <br />
*REINDEXADS<br />
*REINDEXBOOKINGS recreates !BOOKING.ORDERS<br />
*REINDEXBRANDS<br />
*REINDEXCLIENTS<br />
*REINDEXINVS recreates !INVOICES<br />
*REINDEXJOBS<br />
*REINDEXMATERIALS<br />
*REINDEXPLANS<br />
*REINDEXPRODINVS recreates !PRODUCTION.INVOICES<br />
*REINDEXPRODORDERS recreates !PRODUCTION.ORDERS<br />
*REINDEXRATECARDS<br />
*REINDEXSCHEDULES<br />
*REINDEXSUPPLIERS<br />
*REINDEXTIMESHEETS<br />
*REINDEXVEHICLES<br />
<br />
REINDEXMEDIA does all the following<br />
*REINDEXPLANS<br />
*REINDEXSCHEDULES<br />
*REINDEXADS<br />
*REINDEXMATERIALS<br />
*REINDEXBOOKINGS<br />
<br />
REINDEXFILES does all the following<br />
*REINDEXCLIENTS<br />
*REINDEXBRANDS<br />
*REINDEXSUPPLIERS<br />
*REINDEXVEHICLES<br />
*REINDEXRATECARDS<br />
<br />
REINDEXPRODUCTION does all the following<br />
*REINDEXJOBS<br />
*REINDEXPRODORDERS<br />
*REINDEXPRODINVS<br />
*REINDEXTIMESHEETS<br />
<br />
REINDEXALL does all the following<br />
*REINDEXMEDIA<br />
*REINDEXPRODUCTION<br />
*REINDEXFILES<br />
*REINDEXINVS<br />
*REINDEXACCOUNTS<br />
*REINDEXADDRESSES<br />
<br />
== Fixing damaged files that have no process for recreating them ==<br />
<br />
Some damaged files can be rebuilt using NEOSYS utilities especially index files with filenames starting with !. Other damaged files like ''LOG20xx'' can be “fixed” to prevent NEOSYS crashes as follows <i>but some records will most probably be lost</i>. Depending on the file loss of a few records may not be too bad compared to restoring a database but the client should be informed and make the decision. Depending on the file it is usually best to lose the records. We can make a list of files that one can afford to lose records and those files that can be rebuilt programmatically from other files. Booking order texts they can lose records but inform them and especially the numbers mentioned in FIXFILE<br />
<br />
FIXFILE will not run if there are neosys services still running so before doing the FIXFILE command, shut down services from the Support menu or with the Global command:<br />
<br />
'''NOTE:''' If there are multiple datasets running on the server. Shut down the particular dataset which has got the problem:<br />
<br />
F5<br />
<br />
FIXFILE filename<br />
<br />
(Select option 1 to update the file)<br />
<br />
In case you get any Overwrite messages – type YES, as these are the actual files being updated.<br />
<br />
The only alternative is restore from a previous backup in this case losing a days work. Nasty, and even worse, it will be impossible to reproduce the days work and especially the exact serial numbers of critical documents like orders, invoices, receipts and payments advices.<br />
<br />
<br />
=== Using FIXFILE to repair corrupted files ===<br />
<br />
BEWARE: FIXFILE causes loss of data. If the data is critical then use of FIXFILE can be totally catastrophic without any warning.<br />
<br />
Using FIXFILE on some files is a guaranteed way to cause complete chaos for the users without them being aware of it until too late to do anything about it.<br />
<br />
Corrupt files will cause programs to abort every time they try to update that section of the file. Aborting programs causes possibly horrendous inconsistency in the database so it is important to stop all user activity and fix the corrupt file immediately.<br />
<br />
You can freely use FIXFILE on any file but it works by deleting any problematic data so cannot realistically be used on some files at all.<br />
<br />
FIXFILE cannot and does not recover any corrupted records therefore, for those files that have specific programs to rebuild them, FIXFILE is not the correct option.<br />
<br />
Why use FIXFILE at all since it causes loss of data?<br />
<br />
Many files do not have programs to rebuild them and for some of those files, using FIXFILE is a quick way to get the system back in operation BUT with missing records. Missing records causes various degrees of failure ranging from the odd document missing, totally misleading information like wrong account balances, or any kind of system failure.<br />
<br />
FIXFILE does not fix the consistency of information in the database. When the database is is being updated with a transaction, usually a series of files are updated for the one transaction. A damaged file causes the update program to abort in the middle of the series of updates. Therefore some of the updates are done and the remaining updates are not done. This means that the data in the database (even after fixing the corrupt file) is inconsistent.<br />
<br />
FIXFILE merely fixes the technical structure of the file so that any further program accesses to that portion of the file do not cause immediate program termination and consequent likely catastrophic database inconsistency.<br />
<br />
You must prevent anyone from accessing NEOSYS while FIXFILE is running.<br />
<br />
=== Fixing Damaged DEFINITIONS file ===<br />
<br />
==== Non-Solution ====<br />
<br />
You will probably not be able to login if the DEFINITIONS FILE is damaged. You can press Alt+S and type EXECUTE to get a TCL command box but this still doesnt help because you cannot use FIXFILE on DEFINITIONS.<br />
<br />
CAUTION: DO NOT USE FIXFILE TO TRY AND FIX THE DEFINITIONS FILE.<br />
<br />
DOUBLE CAUTION: IN CASE YOU DECIDE TO IGNORE THIS EXPECT ALL KINDS OF HORRIBLE PROBLEMS IN THE DATABASE REQUIRING A COMPLETE RESTORE FROM A GOOD BACKUP AFTER A FEW DAYS OF PAIN BECAUSE RANDOM OLD DATABASE UPGRADE/CONVERSIONS WILL BE PERFORMED *AGAIN* WITHOUT YOU KNOWING IT.<br />
<br />
==== Partial Restore ====<br />
<br />
You can copy recent DEFINITIONS.LK and DEFINITIONS.OV files from the DATA\datasetcode\GENERAL folder.<br />
<br />
CAUTION: All changes done in the Configuration File, Authorisation File, Users File and various other changes will be reverted to the date of the DEFINITIONS files being restored. If you are restoring from last nights backup or testdata then this will not be much but could cause serious confusion to people who have changed their passwords etc.<br />
<br />
==== Full Restore ====<br />
<br />
Restore from your latest backup losing all work done since that time and date.<br />
<br />
=== Preventing users from accessing NEOSYS in order to do maintenance or repairs ===<br />
<br />
On most systems you can simply stop the NEOSYS processes. On other systems where NEOSYS processes are automatically started in response to requests from the web, you need to disable the autostart by one of the following methods<br />
<br />
# Stop the autostart program/script<br />
# Put a file called NET.CFG with a single line saying AUTOSTART=NO in the neosys\neosys folder<br />
# Stop the IIS server<br />
# Stop/Pause the particular web in question<br />
<br />
== Dealing with damaged files that cannot be fixed ==<br />
<br />
If programmers are unable to fix the damage in a reasonably period of time and the damage is caused due to matters beyond NEOSYS control such as non-dedicated servers and power failures then data must be restored and client advised why they are going to suffer loss of data.<br />
<br />
THIS DOES NOT RELEASE NEOSYS SUPPORT STAFF FROM THE OBLIGATION TO PROACTIVELY INFORM THE CLIENT OF MEASURES TO PREVENT THE RECURRENCE OF THE EVENT.<br />
<br />
The following are the steps to follow:<br />
<br />
# Ascertain the cause of the damage to the database by looking at the internal logs<br />
# Create a new database from the damaged one as it will contain the up to date but damaged database.<br />
# Restore the database from the backup media so that the database is in the last good known state. <br />
# The client can see what work was done over the past couple of days from the damaged database and it will assist them to redo the work in the currently restored out of date main database.<br />
# Next discuss with the client about the cause of the damage and (a) what to do to prevent the damage occurring again (b) to agree a procedure to perform a manual backup in case the automatic one is not performed for any reason overnight.</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Troubleshooting_NEOSYS_Generally&diff=604Troubleshooting NEOSYS Generally2010-11-04T07:51:22Z<p>Sunny: /* Solving “page not found” when downloading some file types after uploading them successfully */</p>
<hr />
<div>== Solving failure to start a NEOSYS server due to disk failure message ==<br />
<br />
=== Problem ===<br />
During a reboot process (which maybe due to a Windows update or even done by a support personnel) the NEOSYS server gets hung on the startup and shows a message "Boot Failure - Abort, Retry". <br />
<br />
=== Temporary solution ===<br />
This typically happens due to the USB being plugged into the server and the boot sequence being wrong - i.e. the server trying to boot from the USB first and fails. The immediate solution would be to unplug the USB and ask the client to reboot the server again and upon successfully rebooting the system, plug the USB back again.<br />
<br />
=== Permanent solution ===<br />
The above problem will occur every time the computer is rebooted, so you need to immediately talk to the IT Administrator of the client and ask them to rectify the boot sequence to make it boot first from the CD ROM, then the HDD and last the USB.<br />
<br />
== Solving "Read error in the operating system file" ==<br />
<br />
=== Problem ===<br />
<br />
Nagios reports a hung process and on the server a process has the following message popup.<br />
<br />
Read error in the operating system file "..\DATA\PT0833\ACCOUNTS\REV20049<br />
The file does not exist or the filename is<br />
not valid for the operating system.<br />
<br />
[[Image:readerrorintheoperatingsystemfile.png]]<br />
<br />
=== Cause ===<br />
<br />
Some non-NEOSYS program is directly accessing the NEOSYS database files while NEOSYS processes are running and using the files as well.<br />
<br />
*Client IT staff using a backup program to perform backup without ensuring that NEOSYS processes are shutdown.<br />
*A NEOSYS rsync process taking longer than expected due to new USB.<br />
<br />
=== Solution ===<br />
<br />
Kill the NEOSYS process eg with the X button. It is advisable NOT to let it run further while it cannot properly access one of its files.<br />
<br />
=== Prevention ===<br />
<br />
Remove the third party program or arrange for it to operate only while NEOSYS processes are shutdown eg from 3am-6am.<br />
<br />
== Handling damaged files ==<br />
<br />
[[Handling damaged files]]<br />
<br />
== Checking for corrupt database files ==<br />
<br />
Login to NEOSYS Maintenance<br />
<br />
Press F5<br />
<br />
CHK.FILES<br />
<br />
or <br />
<br />
CHK.FILES filename<br />
<br />
== Assessing Database Size per File ==<br />
<br />
In NEOSYS maintenance mode<br />
<br />
LIST FILES BY BY-DSND SIZE VOLUME.NAME SIZE<br />
<br />
This will include all files not just those in the actual dataset in DATA\* folders.<br />
<br />
== Resolving slow speed ==<br />
<br />
[[Benchmarking NEOSYS]]<br />
<br />
== Handling failure and warning on nightly backup alerts ==<br />
<br />
[[Handling failure and warning messages on nightly backup alerts]]<br />
<br />
== Resolving permissions errors while logging in ==<br />
<br />
=== Problem ===<br />
<br />
While logging in, you get the following error message:<br />
[[Image:login_error_message.jpg]]<br />
<br />
=== Solution ===<br />
<br />
Add the internet guest account to the security list of the data folder with the default permission of list/read/write<br />
<br />
Make sure the read&execute permission is removed<br />
[[Image:permissions_on_data.jpg]]<br />
<br />
<br />
== Resolving the 'HTTP Error 500.0 - Internal Server Error' while logging in on IE on a Windows Vista system ==<br />
<br />
=== Problem ===<br />
After configuring IIS on Windows Vista you will get this error message while trying to login into NEOSYS from Internet Explorer:<br />
<br />
HTTP Error 500.0 - Internal Server Error<br />
Description: This application is running in an application pool that uses the Integrated .NET <br />
mode. This is the preferred mode for running ASP.NET applications on the current and future <br />
version of IIS.<br />
<br />
In this mode, the application using client impersonation configured with <identity <br />
impersonate="true" /> may not behave correctly. Client impersonation is not available in early <br />
ASP.NET request processing stages and may lead modules in those stages to execute with process <br />
identity instead.<br />
<br />
=== Solution ===<br />
<br />
You can move the application to an application pool that uses the Classic .NET mode by using the following from a command line window (the window must be running as Administrator) <br />
<br />
%systemroot%\system32\inetsrv\APPCMD.EXE set app "Default Web Site/neosys" /applicationPool:"Classic .NET AppPool"<br />
<br />
Alternatively, you can use any other application pool on your system that is running in the Classic .NET mode. You can also use the IIS Administration tool to move this application to another application pool.<br />
<br />
<br />
== Resolving the 'Class Not Registered' error message while logging in ==<br />
<br />
=== Problem ===<br />
While logging into NEOSYS, you will get a popup window giving an error message saying 'Class Not Registered - Server Error'. Typically, you will encounter this error with XP Pro IIS 5.1. As usual, there's way to solve it, however the root cause of this is still unknown.<br />
<br />
Anyway, you will get the proper message in the event log:<br />
<br />
Event Type: Warning<br />
Event Source: W3SVC<br />
Event Category: None<br />
Event ID: 36<br />
Description: The server failed to load application '/LM/W3SVC/1/ROOT/NEOSYS.<br />
The error was 'Class not registered'. <br />
<br />
=== Solution ===<br />
So, what do you do ? This problem is related to Component Services, and when you open Component Services MMC, you will most probably get Error Code 8004E00F COM + was unable to talk to Microsoft Distributed Transaction Coordinator. So, fix the COM+ services first by using the following KB from Microsoft (PRB: Cannot Expand "My Computer" in Component Services MMC Snap-In http://support.microsoft.com/?id=301919):<br />
<br />
To resolve this problem, reinstall Component Services as follows: WARNING: <br />
# Open registry editor, locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3, and then delete this key. <br />
# From the Start menu, point to Settings, click Control Panel, and then click Add/Remove Programs. <br />
# Click Add/Remove Windows Components. <br />
# Proceed through the wizard, and accept all of the defaults (including IIS)<br />
# Restart the computer.<br />
<br />
If the above didn't solve it, and you still receive the 'Class not registered' error message, then you need to recreate the IIS packages in COM+, try<br />
<br />
# Delete IIS related package in Component Services MMC<br />
# IIS In-Process Applications <br />
# IIS Out-of-Process Pooled Applications <br />
# IIS Utilities<br />
<br />
Next, if you still get the message, try following before re-install IIS if you can't find Distributed Transaction Coordinator in your Services console.<br />
<br />
Launch command prompt and run the following command.<br />
# msdtc -install<br />
# net start msdtc<br />
<br />
Then try re-install IIS.<br />
<br />
This should solve the problem<br />
<br />
<br />
== Enabling File Security option on Win XP Professional ==<br />
<br />
=== Problem ===<br />
<br />
In the Properties of any folders, the Security option does not show, hence you cannot modify the Read, Write options.<br />
<br />
=== Solution ===<br />
<br />
The solution would be to untick the 'Simple File Sharing' option from Tools > Folder Options > View:<br />
[[Image:simplefilesharingoff.jpg]]<br />
<br />
== B10 & B12 Errors ==<br />
<br />
These errors are in the software and should be immediately escalated to the programmer.<br />
<br />
== Internet Explorer Menu, View, Text Size doesnt change font size as expected ==<br />
<br />
Cause: This is because the font size is now user definable in NEOSYS and View, Text Size does not override predefined font sizes.<br />
<br />
Solution: If you are using Internet Explorer 7 you can scale the screen (including the font size using ctrl + and ctrl - keyboard shortcuts or the font size button on the bottom right hand side of the window. <br />
<br />
You can adjust the font size on the User Details form when you login although this permanently applies to all forms not just the one that you are on.<br />
<br />
== Error on process window "Not enough string space - Out of Memory" ==<br />
<br />
=== Message ===<br />
<br />
‘RTP27’ Line 1. [B29] Not enough string space – Out of Memory.<br />
<br />
Not enough memory to execute Debugger; current program aborted.<br />
Press any key to continue<br />
<br />
[[Image:out_of_memory.jpg]]<br />
<br />
=== Cause ===<br />
Unknown perhaps related to some large document or report<br />
<br />
=== Solution ===<br />
Ask users for any hanging transactions.<br />
None other than closing and starting another process<br />
<br />
== Uploaded jpg files fail to display in internet explorer ==<br />
<br />
Some large jpg files > 2Mb cannot be viewed in internet explorer despite being viewable in image preview, ms paint and other viewers/editors. It is not an issue caused by uploading or downloading the files.<br />
<br />
These file appear to have been created on Photoshop CS Macintosh and may be a special type of uncompressed jpg used for production quality files.<br />
<br />
=== Partial solution ===<br />
Before uploading the files, open them in some editor like MS Paint (right click, edit) and save them. However this results in a loss of quality. Perhaps there is some program that can convert these files to a format understandable by Internet explorer without any loss of quality.<br />
<br />
<br />
== "You have attempted to write to a read-only file" ==<br />
<br />
=== Message ===<br />
<br />
Error while writing data.<br />
You have attempted to write to a read-only file.<br />
- or -<br />
access to the file has been denied by the operating system.<br />
(operating system file name: "..\DATA\ADLINEC\ADAGENCY\REV76467.OV00012618")<br />
<br />
=== Cause ===<br />
<br />
It is almost certainly due to some third party backup or other maintenance software opening the NEOSYS database files when it shouldn't e.g. badly configured third party backup scheduled to backup NEOSYS while NEOSYS is still running. Note that the exact filename varies each time.<br />
<br />
=== Solution ===<br />
<br />
This can be a serious error that causes damaged files in NEOSYS especially if the filename ends in .OV. Use the usual methods of checking for damaged files e.g. do a backup which also looks for damaged files BUT DO NOT OVERWRITE THE LATEST BACKUP SINCE IT MAY BE REQUIRED for restoration. Then fix the damaged files using the usual methods e.g. by rebuilding/using<br />
FIXFILE or restoring databases.<br />
<br />
=== Prevention ===<br />
<br />
Remove the third party backup or other maintenance software or reschedule it to run at a time that NEOSYS is shutdown. Removal of software may require hunting through the windows process list for unexpected programs running.<br />
<br />
== Resolving "Cannot backup/restore because PROCESS1 PROCESS2 (etc) is/are online" message ==<br />
<br />
This can happen for a variety of reasons if all the NEOSYS processes fail to close down at backup time<br />
<br />
# NEOSYS maintenance windows are left open.<br />
# NEOSYS processes hang due to software error.<br />
<br />
== How to kill hung NEOSYS processes ==<br />
<br />
NOTE WELL: If you kill actively working NEOSYS processes (those which are "listening" and not hung/crashed) there is a reasonable chance that the database will be damaged and might need a restore losing possibly large amounts of work.<br />
<br />
==== If NEOSYS processes are visible on the server desktop ====<br />
<br />
Look for processes which don't have "Listening ..." on the last but one line. The times on the left hand side are frozen as at the time of the hang.<br />
<br />
You can then click the X to kill the process and confirm that this is OK.<br />
<br />
Example of a NEOSYS process that has hung due to a software error resulting in a failure to handle a complex query with a lot of brand codes.<br />
<br />
[[Image:hungprocess.jpg]]<br />
<br />
==== If NEOSYS processes are not visible on the server desktop ====<br />
<br />
NEOSYS processes are most of the time visible on the desktop (i.e. the black dos windows) in Windows 2003 OS, except in the case that the process has been scheduled to start on computer restart and no one has logged into the server. In this case it would be running in the background. Secondly in the case of Windows 2008, the processes always are hidden. <br />
<br />
You can check if there are any hung processes from the NEOSYS Support Menu, List of Database Processes. <br />
[[Image:databaseprocesseslist.jpg]]<br />
<br />
In this case you should follow the below instructions - however all of them need to be done within 30 seconds of starting the first instruction to avoid inconvenience to the users. It is recommend that you keep relevant windows open before proceeding with the same:<br />
<br />
#Shutdown NEOSYS by TEMPORARILY putting a file called GLOBAL.END in the parent directory of NEOSYS (if there is already a GLOBAL.END.TEMP file then rename it to GLOBAL.END). Leaving the file there would prevent NEOSYS from starting up again. Shutting down NEOSYS from the Support menu will not work because of the hung processes.<br />
#Use Windows Task Manager to kill all the NTVDM processes - assuming that you have closed all the visible NEOSYS processes, then the NTVDM processes in the task manager would be the hung one.<br />
#Delete GLOBAL.END or rename it to GLOBAL.END.TEMP<br />
#Restart the processes back again. If there are many datasets then you need to restart them all well within the 30 seconds period.<br />
<br />
In case of Patsalides, where we have a thousand datasets which start "on demand" i.e. usually on login; all you need to do is start one dataset which will restart all the other datasets "on demand". If there is no response within 30 seconds then one of the running datasets will start it up so there appears to be a 30 second delay when you login to one of the thousand datasets the first time on any one day.<br />
<br />
=== Temporary workarounds for hung NEOSYS processes ===<br />
Until the error in the software is fixed users can often get their results by simplifying their requirements. For example select individual clients instead of selecting all the brands for a particular client. If the user has repeated his request (in forlorn hope that it would work finally) then the number of NEOSYS working NEOSYS processes will drop causing severe slowdown for other users and complete stop if all the NEOSYS processes hang.<br />
<br />
== How to fix a NEOSYS process which opens up in a notepad instead of Microsoft Windows Based Script Host (i.e. DOS window)==<br />
<br />
The NEOSYS process (cmd file) might open up in a notepad, instead of the usual black colour DOS window. This can be fixed by the following:<br />
<br />
# Download and install the Windows Script 5.6/5.7 from the Microsoft Website<br />
# Go to any folder, click on Tools > Folder Options > File Types and find the .JS and .JSE and change the default program to wscript.exe (from windows>system32)<br />
<br />
== Resolving a 'Could not start' error on Scheduled Tasks in Windows Server 2000 SP4 ==<br />
<br />
This error occurs because of a change that is made to the data that is stored in the credentials database when you install Windows 2000 SP4. Hence installing SP4 causes the the data that is stored in the credentials database to get converted to an SP4-compatible format. A registry key is configured to indicate that the data has been converted to the SP4 format.<br />
<br />
Hence the Scheduled Tasks do not work sometimes. However the Scheduled Tasks works fine sometimes, but when you uninstall SP4, it does not work.<br />
<br />
The best solution is to:<br />
<br />
# Incase Scheduled Tasks do not work after installing SP4, then uninstall SP4 and it should be fine.<br />
# Incase Scheduled Tasks works after installing SP4, and later after uninstalling SP4, it does not work, then install SP4 and it should be fine.<br />
<br />
== Checking for server or NEOSYS crashes ==<br />
<br />
#NEOSYS Maintenance Mode<br />
#General Menu, Setup, Processes<br />
#Select the dates and the option Detailed<br />
<br />
This report shows a list of dates and times that NEOSYS logged in but did not log out properly.<br />
<br />
Ignore the very latest entries since they represent the current NEOSYS processes. For example, if you have four NEOSYS processes running at the time that you get the report (including any in maintenance mode) then you can ignore the last four entries.<br />
<br />
The date and time shows for each process that has failed to shutdown correctly when the process logged in. Versions of NEOSYS from January 2008 will also show the date and time that each crashed NEOSYS process was last active (heartbeat) so that the time of failure can be known.<br />
<br />
If you see a bunch of NEOSYS processes all started up at around the same time but all failed to shutdown correctly then the cause will be a server failure - usually power failure.<br />
<br />
Isolated one-off failures will be related to individual NEOSYS process crashes - most commonly caused by one of the following:<br />
<br />
#NEOSYS hanging to due to software failure<br />
#Manually exiting a NEOSYS process on the server either by pressing Ctrl+Alt+Del or clicking the "X" close icon/box and ignoring the warning<br />
#Random server failures eg memory, disk etc<br />
<br />
Example:<br />
<br />
LOGIN 22/12/2007 06:02 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 06:00 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 06:01 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 06:02 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 08:52 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 08:52 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 08:53 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 8/1/2008 06:00 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 8/1/2008 06:01 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 8/1/2008 06:02 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 8/1/2008 13:51 NEOSYS SERVER NEOSYS Current user session <br />
<br />
Interpretation:<br />
<br />
The first four entries indicate that all four NEOSYS processes started at 06am were suddenly killed probably by power failure<br />
<br />
The next four entries indicate that NEOSYS was restarted at around 08:52 and all these processes were AGAIN killed probably by power failure<br />
<br />
The last four entries can be ignored because there were four NEOSYS processes running at the time that the report was generated<br />
<br />
== Searching for word/number in the database files using maintenance mode ==<br />
<br />
You can search for any word/number in the database files of NEOSYS, using the following command line:<br />
<br />
F5<br />
FIND FILENAME WORDWITHOUTANYSPACES<br />
<br />
For eg:<br />
FIND CURRENCIES 1.1<br />
(here you are searching for the number 1.1 in the currencies file) You CANNOT search for a phrase ie include spaces like this.<br />
<br />
Or you can also type:<br />
FIND FILENAME <enter><br />
and it will ask you what you want do to search. You can enter an exact phrase with spaces.<br />
<br />
Incase you do not know the filenames, you can enter the following command to see all the filenames in the system:<br />
<br />
F5<br />
LF<br />
<br />
== NO LOCK RECORD error when working on NEOSYS ==<br />
<br />
=== Error Message ===<br />
<br />
The following error message appears:<br />
<br />
Cannot save "DOCUMENT NAME" because:<br />
Somebody has updated this record.<br />
Your update cannot be applied.<br />
This session id does not agree "NO LOCK PERIOD"<br />
<br />
=== Possible Causes and Solutions ===<br />
<br />
1. There is some other error in NEOSYS software while saving the record.<br />
Probably another error message would come before this one and that message should be sent to NEOSYS in order to solve the actual problem.<br />
<br />
2. There has been a temporary loss of connection to the server for some period of time.<br />
The NEOSYS web page needs to periodically "refresh" the exclusive lock on the document being edited. If NEOSYS cannot perform the refresh it may lose the rights to save the document.<br />
<br />
Loss of connection could be for a huge variety of reasons including server, network, and workstation failures.<br />
<br />
3. Bad Internet Explorer Configuration<br />
Loss of cookies etc due to third party software (internet toolbars/spyware etc)<br />
<br />
Reset Internet Explorer to factory settings.<br />
<br />
<br />
== Troubleshooting the NTVDM Hard error when opening up NEOSYS processes ==<br />
<br />
=== Error Message ===<br />
<br />
The following error message appears:<br />
<br />
[[Image:ntvdm.jpg]]<br />
<br />
NTVDM encountered a hard error<br />
<br />
=== Solution ===<br />
<br />
This error is caused by missing or corrupt Windows system files (i.e. command.com, autoexec.nt and config.nt). The solution is to run a program called XP FIX which will reinstall these missing files. You can download it form http://www.visualtour.com/downloads/xp_fix.exe<br />
<br />
Sometimes even after running the XP FIX program the error still appears. Then you need to copy all the files under C:/windows/repair to C:/windows/system32 and in the autoexec.nt and config.nt put REM before any lines there which don't have it.<br />
<br />
== Troubleshooting a Service Unavailable message on Internet Explorer when opening up NEOSYS ==<br />
<br />
=== Error Message ===<br />
<br />
The following error message appears in Internet Explorer when you try to open up NEOSYS:<br />
<br />
Service Unavailable<br />
<br />
=== Solution ===<br />
<br />
Open the IIS Manager, right click Web Sites and select properties:<br />
[[Image:serviceunavailable1.jpg]]<br />
<br />
Switch to the Service Tab and tick the "Run WWW Service in IIS 5.0 Isolation Mode".<br />
[[Image:serviceunavailable2.jpg]]<br />
<br />
You will be asked for Restart of IIS. Click yes to restart IIS. If you are not asked just restart IIS.<br />
<br />
== Inspecting IIS log files ==<br />
<br />
At a windows command prompt:<br />
<br />
c:<br />
cd \Windows\system32\LogFiles\W3SVC1<br />
<br />
or<br />
<br />
%SystemDrive%<br />
cd %SystemRoot%<br />
cd system32\LogFiles\W3SVC1<br />
<br />
then (substituting the ip number you are interested in)<br />
<br />
find "192.168.1.55" *|sort>temp.log<br />
<br />
Open temp.log in Excel and use Tools, Data, Text to Columns to split into columns using options "Delimited" and check split on Space.<br />
<br />
Autowidth all columns by clicking on the top left box just outside the data to the left of column A and above column 1 then double click the column separator to the right of column "A"<br />
<br />
Note that times and dates are in UTC/GMT so you have to add/subtract your timezone offset to get local times.<br />
<br />
== Fixing NEOSYS processes that do not auto start / Recovering from incorrect advanced date or time ==<br />
<br />
=== Problem explained ===<br />
After starting up the 1st process, the rest of the processes don't start up.<br />
<br />
=== Solution ===<br />
<br />
The possible cause for this could be that the system date/time might have been changed - either manually or by the auto synchronization. Do the following checks in the sequence of order:<br />
<br />
# Check for any .$* files (* is a number, the highest being the latest one). If it shows OK, then proceed ahead.<br />
# Check for any .end files and delete it to rename to .end.temp<br />
# Check the System Event Viewer log for any 520 or 577 error message (refer http://128.175.24.251/forensics/timechange.htm). Also check for any out of sequence / ahead of today date or time.<br />
# In case of no 520 or 577 error message, go to Administrative Tools > Local Security Policy > Local Policies > Audit Policy > Audit Privilege use - make sure that Success and Failure are selected under this (this will ensure that future changes to the date/time are recorded in the System Log).<br />
# In NEOSYS maintenance mode - F5 ED PROCESSES %UPDATE% - and see what it says, incase of any text there, that means that for sure the system date has been changed.<br />
# Now to fix this, in maintenance mode again enter - F5 DELETE PROCESSES "%UPDATE%"<br />
<br />
<br />
== Recognising and Solving Low Memory Problems ==<br />
<br />
Quick Note: Installing a server class operating system on a workstation class computer with the intention of NEOSYS serving a heavy load is likely to cause problems with low memory.<br />
<br />
Quick Fix: Disable *ALL* non-essential features in the power-on setup menu.<br />
<br />
=== Effects ===<br />
<br />
It is speculated but not proven that low memory may cause NEOSYS to fail by hanging, causing damaged files etc.<br />
<br />
=== Checking ===<br />
<br />
F5<br />
MEMORY<br />
<br />
On server class machines it should say somewhere around 350Kb to 370Kb Free<br />
<br />
Some server class machines have around 330Kb and sometimes even less with no reported problems<br />
<br />
The actual effect of low memory is supposed to make NEOSYS slower and perhaps cause hanging and damaged files however this has not been proven in an specific case so far.<br />
<br />
On workstation class machines it may often say around 280Kb to 300Kb.<br />
<br />
=== Cause ===<br />
<br />
Although there is plenty of real memory in virtually all computers now, NEOSYS runs in the legacy 16 bit virtual memory space of a windows mode called NTVDM. This is limited to 1Mb plus 4Mb of EMS memory.<br />
<br />
The 1Mb memory space is shared with:<br />
<br />
#Various non-essential windows drivers which NEOSYS automatically disables them in autoexec.nt<br />
#Various plug and play hardware device drivers for the various adapters in the computer like video, network adapters and various other items that NEOSYS is unable to disable.<br />
<br />
In a server class computer the hardware device drivers are usually minimally present in the 1Mb base memory and do not therefore DOESNT a low memory situation for NEOSYS.<br />
<br />
In workstation class computers there are often many hardware device drivers present in the 1Mb base memory and this DOES causes a low memory situation for NEOSYS.<br />
<br />
When NEOSYS is installed on workstation class computers with XP there is usually not a heavy load expectation and therefore the low memory does not cause a problem.<br />
<br />
If Windows Server OS is installed on a workstation class computer NEOSYS may well be expected to serve a heavy load with limited amounts of memory.<br />
<br />
Workstation class computers: hardware drivers present and EMS is installed in low memory (0000-9FFF) causing low memory for NEOSYS and possible inability to <br />
<br />
Server class computers: Usually few hardware drivers are present in high part (A000-FFFF) of the 1Mb base memory and EMS is able to occupy the high memory leaving the low part (0000-9FFFF) of the 1Mb memory free for NEOSYS. You can find out how much memory is available to NEOSYS and whether EMS is occuping high or low memory using the following sections.<br />
<br />
=== Fixing Low Memory ===<br />
<br />
Start, Run, notepad c:\windows\system32\autoexec.nt<br />
<br />
Every time NEOSYS starts it tries to make some changes as follow:<br />
<br />
#replaces all lines in C:/WINDOWS/SYSTEM32/AUTOEXEC.NT starting with 'lh ' to start with 'rem NEOSYS LH ' instead.<br />
#changes the line in C:/WINDOWS/SYSTEM32/CONFIG.NT "files=..." to "FILES=200"<br />
<br />
The replacement is case sensitive triggered on 'lh' and 'files' so if you manually edit the files and remove the rem or change the number of files and leave the LH and FILES in uppercase then NEOSYS will NOT make further changes. This allows you to do manual amendments to the files without NEOSYS overwriting them.<br />
<br />
Check that NEOSYS has successfully disabled all the drivers in the lines starting with LH.<br />
<br />
They should be commented out (prefixed) with REM or REM NEOSYS as follows.<br />
<br />
After making changes reopen NEOSYS in maintenance mode to use the MEMORY and WHO commands again.<br />
<br />
<pre><br />
REM Install CD ROM extensions<br />
REM NEOSYS LH %SystemRoot%\system32\mscdexnt.exe<br />
<br />
REM Install network redirector (load before dosx.exe)<br />
REM NEOSYS LH %SystemRoot%\system32\redir<br />
<br />
REM Install DPMI support<br />
REM NEOSYS LH %SYSTEMROOT%\SYSTEM32\DOSX<br />
</pre><br />
<br />
=== Allowing DOS programs that require DOSX to run on the same computer as NEOSYS ===<br />
<br />
The automatic commenting out DOSX by NEOSYS will prevent some other DOS-like programs from running. If NEOSYS is on dedicated server then there should be no other such programs to fail. However, if you must allow DOS-like programs to work as well as NEOSYS you can do the following configuration:<br />
<br />
#leave or restore the original AUTOEXEC.NT and CONFIG.NT files where they are<br />
#copy them to another folder eg neosys folder<br />
#make the necessary REM changes there by hand<br />
#right click the NEOSYS\NEOSYS\AREV.PIF and select properties<br />
#change the location of the AUTOEXEC.NT and CONFIG.NT files in the following location<br />
<br />
[[image:pifsettings.jpg]]<br />
<br />
=== Checking EMS Memory Configuration ===<br />
<br />
==== Inspection ====<br />
<br />
F5<br />
WHO<br />
<br />
press the up arrow to get to the last part/page<br />
<br />
===== Example of Typical Server EMS Memory =====<br />
[[image:serveremm.jpg]]<br />
<br />
===== Example of Typical Workstation EMS Memory =====<br />
[[image:workstationemm.jpg]]<br />
<br />
====Correction====<br />
<br />
No easy way<br />
<br />
Removal of hardware adapters designed for workstations instead of servers eg graphics cards and network cards.<br />
<br />
Many of the devices may be located on the motherboard and not relocatable except possibly by BIOS configuration or special manufacturer information.<br />
<br />
Use windows device manager, View: Resources by Connection, Open the Memory item and look for items between 000A0000 up to 000FFFFF that might give you a clue as to what hardware could be removed or reconfigured. Actually only 000C0000 to 000FFFFF is candidate for EMS memory since 000A000-000BFFFF is mandatory video memory in all systems.<br />
<br />
[[image:devicemanager.jpg]]<br />
<br />
== Resolving issue where NEOSYS processes do not start-up at all or start-up and close immediately ==<br />
<br />
# Find if a file with the name global.end exists in the root directory of the NEOSYS installation. Eg D:\global.end . If you find such a file, rename it to global.end.temp - for more information on global.end and what it does refer to http://techwiki.neosys.com/index.php/Closing_NEOSYS_services<br />
# If the above didn't fix the problem and NEOSYS still does not start, do a windows search for the entire NEOSYS folder for *.end (i.e. any file ending with .end extension). You may find a (databasecode).end file in D:\neosys\neosys folder which is created by the NEOSYS program during backup at 1 am and later on removed automatically. In this case NEOSYS program might have crashed during the backup and left this file behind. (databasecode).end files prevent other other NEOSYS processes starting up on the database while exclusive processes (like backup) are being done.<br />
<br />
In case the above didn't fix the problem then escalate to the programmer immediately.<br />
<br />
== Handling Change Backup message if the client does not use a USB backup device ==<br />
DO *NOT* FOLLOW THIS PROCEDURE SINCE IS IT IS TOTALLY UNACCEPTABLE FOR NEOSYS TO SEND OUT A "BACKUP SUCCESS" MESSAGE WHEN THE BACKUP IS NOT BEING DONE PROPERLY. IN GENERAL, TAKING SHORT CUTS THAT MAKE THINGS APPEAR SATISFACTORY WHEN THEY ARE NOT IS VERY POOR POLICY.<br />
<br />
IF THE CLIENT IS BACKING UP TO A NON-REMOVABLE DESTINATION THEN EITHER 1. LIVE WITH THE FAILURE MESSAGE OR 2. SUPPRESS THE BACKUP ENTIRELY IN WHICH CASE NO BACKUPS ARE BEING DONE AND PROBABLY THIS WILL SHOW ON NEOSYS PROACTIVE WARNING SYSTEMS LIKE NAGIOS.<br />
<br />
# Basically most of the client use USB for Neosys server but there are some clients who do not use USB but save their backups in hard drive. <br />
# As we know that backup take place in Data.bak folder but it do a backup only for a week in a single USB. Over here client do not use USB but save their backup in hard drive in Data.bak folder, once the week is over it will again give Change backup message. <br />
# In this case rename the Data.bak folder to Data1.bak this is done because system read only Data.bak folder as it is configured in the system. When you rename Data.bak to Data1.bak it automatically create a new folder Data.bak in Backup drive.<br />
# This process is done so that the backup should not fail then next day morning and backups are done in Data.bak folder.<br />
# In the third week we will again see the same message Chang backup USB message so you need to rename Data.bak folder to Data2.bak<br />
# But in fourth week you rename the Data1.bak to Data.bak and change the Data2.bak to Data1.bak and Data.bak to Data2.bak <br />
# Keep only three folders and Data.bak, Data1.bak, Data2.bak and keep on renaming these folders every week as shown above.<br />
<br />
== Closing processes that are not visible on the desktop or hidden ==<br />
<br />
NEOSYS processes are most of the time visible on the desktop (i.e. the black dos windows) in Windows 2003 OS, except in the case that the process has been scheduled to start on restart and no one has logged into the server. In this case it would be hidden. Secondly in the case of Windows 2008, the processes always are hidden.<br />
<br />
In these cases whenever there is a hung NEOSYS process - due to many reasons for eg low memory. In this case you should close all processes using the global.end method and then from the task manager kill any NTVDM processes and then restart NEOSYS. This should be done within 30 seconds from using the global.end method to avoid any inconvenience to the users. If there are many datasets then you need to restart them all well within the 30 seconds period.<br />
<br />
In case of Patsalides, where we have a thousand datasets which start "on demand" i.e. usually on login; all you need to do is start one dataset which will restart all the other datasets "on demand". If there is no response within 30 seconds then one of the running datasets will start it up so there appears to be a 30 second delay when you login to one of the thousand datasets the first time on any one day.<br />
<br />
== NEOSYS not updating Nagios ==<br />
<br />
You find something like the following message in UPDATE.$WG in the neosys\neosys.folder<br />
<br />
Connecting to 192.168.100.145:8080 failed: No such file or directory.<br />
<br />
Where the above appears to be some non-functional http proxy server ip/port number and is not the expected nagios server ip number.<br />
<br />
The windows command proxycfg shows the same ip and port<br />
<br />
<pre><br />
D:\NEOSYS\NEOSYS>proxycfg<br />
Microsoft (R) WinHTTP Default Proxy Configuration Tool<br />
Copyright (c) Microsoft Corporation. All rights reserved.<br />
<br />
Current WinHTTP proxy settings under:<br />
HKEY_LOCAL_MACHINE\<br />
SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\<br />
WinHttpSettings :<br />
<br />
Proxy Server(s) : 192.168.100.145:8080<br />
Bypass List : 192.168.*.*;localhost;<local><br />
<br />
</pre><br />
<br />
=== Solution 1 - Remove the above setting to create a direct connection ===<br />
<br />
To remove the registry entries that ProxyCfg.exe creates,<br />
you must delete the WinHttpSettings value from the following registry key.<br />
<br />
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\WinHttpSettings<br />
<br />
After you do the above, confirm that the proxy details are deleted by running the proxycfg command.<br />
<br />
Next, restart the NEOSYS processes for the changes to be affected.<br />
<br />
=== Solution 2 – Configure a functioning proxy ip/port number ===<br />
<br />
Use the proxycfg command to enter a working proxy ip/port number/exclusion list<br />
<br />
http://msdn.microsoft.com/en-us/library/aa384069%28VS.85%29.aspx<br />
<br />
After you do the above, confirm that the new proxy details are working by running the proxycfg command again.<br />
<br />
Next, restart the NEOSYS processes for the changes to be affected.<br />
<br />
<B> Note: Please refer to the link before you restart NEOSYS processes http://techwiki.neosys.com/index.php/Troubleshooting_NEOSYS_Generally#Closing_processes_that_are_not_visible_on_the_desktop_or_hidden </B><br />
<br />
== Solving “page not found” when downloading some file types after uploading them successfully ==<br />
=== One by One ===<br />
<br />
Windows web server will not download file types that it is unaware of. You can enable the download of new file types one by one as follows.<br />
<br />
This process is tedious and error-prone if you have to add many type.<br />
<br />
#Computer Management<br />
#Services and Applications<br />
#IIS properties<br />
#Mime Types<br />
#Add<br />
<br />
=== Many ===<br />
<br />
Window Server 2003 is unaware of all the Office 2007+ file types. To add all Office 2007+ file types at once do the following:<br />
<br />
Stop IIS<br />
<br />
iisreset /stop<br />
<br />
Open the list of mime types<br />
<br />
*Start, Run, notepad C:\WINDOWS\system32\inetsrv\MetaBase.xml<br />
<br />
Search the file for “xlsx” and quit the editor if already inserted.<br />
<br />
Otherwise, find the following line,<br />
<br />
.xml,text/xml<br />
<br />
and insert after that line the following lines. They do not need to be indented.<br />
<br />
<pre><br />
.docm,application/vnd.ms-word.document.macroEnabled.12<br />
.docx,application/vnd.openxmlformats-officedocument.wordprocessingml.document<br />
.dotm,application/vnd.ms-word.template.macroEnabled.12<br />
.dotx,application/vnd.openxmlformats-officedocument.wordprocessingml.template<br />
.potm,application/vnd.ms-powerpoint.template.macroEnabled.12<br />
.potx,application/vnd.openxmlformats-officedocument.presentationml.template<br />
.ppam,application/vnd.ms-powerpoint.addin.macroEnabled.12<br />
.ppsm,application/vnd.ms-powerpoint.slideshow.macroEnabled.12<br />
.ppsx,application/vnd.openxmlformats-officedocument.presentationml.slideshow<br />
.pptm,application/vnd.ms-powerpoint.presentation.macroEnabled.12<br />
.pptx,application/vnd.openxmlformats-officedocument.presentationml.presentation<br />
.xlam,application/vnd.ms-excel.addin.macroEnabled.12<br />
.xlsb,application/vnd.ms-excel.sheet.binary.macroEnabled.12<br />
.xlsm,application/vnd.ms-excel.sheet.macroEnabled.12<br />
.xlsx,application/vnd.openxmlformats-officedocument.spreadsheetml.sheet<br />
.xltm,application/vnd.ms-excel.template.macroEnabled.12<br />
.xltx,application/vnd.openxmlformats-officedocument.spreadsheetml.template<br />
</pre><br />
<br />
Save the file with File and Exit<br />
<br />
Restart IIS</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Troubleshooting_NEOSYS_Generally&diff=603Troubleshooting NEOSYS Generally2010-11-04T07:46:05Z<p>Sunny: </p>
<hr />
<div>== Solving failure to start a NEOSYS server due to disk failure message ==<br />
<br />
=== Problem ===<br />
During a reboot process (which maybe due to a Windows update or even done by a support personnel) the NEOSYS server gets hung on the startup and shows a message "Boot Failure - Abort, Retry". <br />
<br />
=== Temporary solution ===<br />
This typically happens due to the USB being plugged into the server and the boot sequence being wrong - i.e. the server trying to boot from the USB first and fails. The immediate solution would be to unplug the USB and ask the client to reboot the server again and upon successfully rebooting the system, plug the USB back again.<br />
<br />
=== Permanent solution ===<br />
The above problem will occur every time the computer is rebooted, so you need to immediately talk to the IT Administrator of the client and ask them to rectify the boot sequence to make it boot first from the CD ROM, then the HDD and last the USB.<br />
<br />
== Solving "Read error in the operating system file" ==<br />
<br />
=== Problem ===<br />
<br />
Nagios reports a hung process and on the server a process has the following message popup.<br />
<br />
Read error in the operating system file "..\DATA\PT0833\ACCOUNTS\REV20049<br />
The file does not exist or the filename is<br />
not valid for the operating system.<br />
<br />
[[Image:readerrorintheoperatingsystemfile.png]]<br />
<br />
=== Cause ===<br />
<br />
Some non-NEOSYS program is directly accessing the NEOSYS database files while NEOSYS processes are running and using the files as well.<br />
<br />
*Client IT staff using a backup program to perform backup without ensuring that NEOSYS processes are shutdown.<br />
*A NEOSYS rsync process taking longer than expected due to new USB.<br />
<br />
=== Solution ===<br />
<br />
Kill the NEOSYS process eg with the X button. It is advisable NOT to let it run further while it cannot properly access one of its files.<br />
<br />
=== Prevention ===<br />
<br />
Remove the third party program or arrange for it to operate only while NEOSYS processes are shutdown eg from 3am-6am.<br />
<br />
== Handling damaged files ==<br />
<br />
[[Handling damaged files]]<br />
<br />
== Checking for corrupt database files ==<br />
<br />
Login to NEOSYS Maintenance<br />
<br />
Press F5<br />
<br />
CHK.FILES<br />
<br />
or <br />
<br />
CHK.FILES filename<br />
<br />
== Assessing Database Size per File ==<br />
<br />
In NEOSYS maintenance mode<br />
<br />
LIST FILES BY BY-DSND SIZE VOLUME.NAME SIZE<br />
<br />
This will include all files not just those in the actual dataset in DATA\* folders.<br />
<br />
== Resolving slow speed ==<br />
<br />
[[Benchmarking NEOSYS]]<br />
<br />
== Handling failure and warning on nightly backup alerts ==<br />
<br />
[[Handling failure and warning messages on nightly backup alerts]]<br />
<br />
== Resolving permissions errors while logging in ==<br />
<br />
=== Problem ===<br />
<br />
While logging in, you get the following error message:<br />
[[Image:login_error_message.jpg]]<br />
<br />
=== Solution ===<br />
<br />
Add the internet guest account to the security list of the data folder with the default permission of list/read/write<br />
<br />
Make sure the read&execute permission is removed<br />
[[Image:permissions_on_data.jpg]]<br />
<br />
<br />
== Resolving the 'HTTP Error 500.0 - Internal Server Error' while logging in on IE on a Windows Vista system ==<br />
<br />
=== Problem ===<br />
After configuring IIS on Windows Vista you will get this error message while trying to login into NEOSYS from Internet Explorer:<br />
<br />
HTTP Error 500.0 - Internal Server Error<br />
Description: This application is running in an application pool that uses the Integrated .NET <br />
mode. This is the preferred mode for running ASP.NET applications on the current and future <br />
version of IIS.<br />
<br />
In this mode, the application using client impersonation configured with <identity <br />
impersonate="true" /> may not behave correctly. Client impersonation is not available in early <br />
ASP.NET request processing stages and may lead modules in those stages to execute with process <br />
identity instead.<br />
<br />
=== Solution ===<br />
<br />
You can move the application to an application pool that uses the Classic .NET mode by using the following from a command line window (the window must be running as Administrator) <br />
<br />
%systemroot%\system32\inetsrv\APPCMD.EXE set app "Default Web Site/neosys" /applicationPool:"Classic .NET AppPool"<br />
<br />
Alternatively, you can use any other application pool on your system that is running in the Classic .NET mode. You can also use the IIS Administration tool to move this application to another application pool.<br />
<br />
<br />
== Resolving the 'Class Not Registered' error message while logging in ==<br />
<br />
=== Problem ===<br />
While logging into NEOSYS, you will get a popup window giving an error message saying 'Class Not Registered - Server Error'. Typically, you will encounter this error with XP Pro IIS 5.1. As usual, there's way to solve it, however the root cause of this is still unknown.<br />
<br />
Anyway, you will get the proper message in the event log:<br />
<br />
Event Type: Warning<br />
Event Source: W3SVC<br />
Event Category: None<br />
Event ID: 36<br />
Description: The server failed to load application '/LM/W3SVC/1/ROOT/NEOSYS.<br />
The error was 'Class not registered'. <br />
<br />
=== Solution ===<br />
So, what do you do ? This problem is related to Component Services, and when you open Component Services MMC, you will most probably get Error Code 8004E00F COM + was unable to talk to Microsoft Distributed Transaction Coordinator. So, fix the COM+ services first by using the following KB from Microsoft (PRB: Cannot Expand "My Computer" in Component Services MMC Snap-In http://support.microsoft.com/?id=301919):<br />
<br />
To resolve this problem, reinstall Component Services as follows: WARNING: <br />
# Open registry editor, locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3, and then delete this key. <br />
# From the Start menu, point to Settings, click Control Panel, and then click Add/Remove Programs. <br />
# Click Add/Remove Windows Components. <br />
# Proceed through the wizard, and accept all of the defaults (including IIS)<br />
# Restart the computer.<br />
<br />
If the above didn't solve it, and you still receive the 'Class not registered' error message, then you need to recreate the IIS packages in COM+, try<br />
<br />
# Delete IIS related package in Component Services MMC<br />
# IIS In-Process Applications <br />
# IIS Out-of-Process Pooled Applications <br />
# IIS Utilities<br />
<br />
Next, if you still get the message, try following before re-install IIS if you can't find Distributed Transaction Coordinator in your Services console.<br />
<br />
Launch command prompt and run the following command.<br />
# msdtc -install<br />
# net start msdtc<br />
<br />
Then try re-install IIS.<br />
<br />
This should solve the problem<br />
<br />
<br />
== Enabling File Security option on Win XP Professional ==<br />
<br />
=== Problem ===<br />
<br />
In the Properties of any folders, the Security option does not show, hence you cannot modify the Read, Write options.<br />
<br />
=== Solution ===<br />
<br />
The solution would be to untick the 'Simple File Sharing' option from Tools > Folder Options > View:<br />
[[Image:simplefilesharingoff.jpg]]<br />
<br />
== B10 & B12 Errors ==<br />
<br />
These errors are in the software and should be immediately escalated to the programmer.<br />
<br />
== Internet Explorer Menu, View, Text Size doesnt change font size as expected ==<br />
<br />
Cause: This is because the font size is now user definable in NEOSYS and View, Text Size does not override predefined font sizes.<br />
<br />
Solution: If you are using Internet Explorer 7 you can scale the screen (including the font size using ctrl + and ctrl - keyboard shortcuts or the font size button on the bottom right hand side of the window. <br />
<br />
You can adjust the font size on the User Details form when you login although this permanently applies to all forms not just the one that you are on.<br />
<br />
== Error on process window "Not enough string space - Out of Memory" ==<br />
<br />
=== Message ===<br />
<br />
‘RTP27’ Line 1. [B29] Not enough string space – Out of Memory.<br />
<br />
Not enough memory to execute Debugger; current program aborted.<br />
Press any key to continue<br />
<br />
[[Image:out_of_memory.jpg]]<br />
<br />
=== Cause ===<br />
Unknown perhaps related to some large document or report<br />
<br />
=== Solution ===<br />
Ask users for any hanging transactions.<br />
None other than closing and starting another process<br />
<br />
== Uploaded jpg files fail to display in internet explorer ==<br />
<br />
Some large jpg files > 2Mb cannot be viewed in internet explorer despite being viewable in image preview, ms paint and other viewers/editors. It is not an issue caused by uploading or downloading the files.<br />
<br />
These file appear to have been created on Photoshop CS Macintosh and may be a special type of uncompressed jpg used for production quality files.<br />
<br />
=== Partial solution ===<br />
Before uploading the files, open them in some editor like MS Paint (right click, edit) and save them. However this results in a loss of quality. Perhaps there is some program that can convert these files to a format understandable by Internet explorer without any loss of quality.<br />
<br />
<br />
== "You have attempted to write to a read-only file" ==<br />
<br />
=== Message ===<br />
<br />
Error while writing data.<br />
You have attempted to write to a read-only file.<br />
- or -<br />
access to the file has been denied by the operating system.<br />
(operating system file name: "..\DATA\ADLINEC\ADAGENCY\REV76467.OV00012618")<br />
<br />
=== Cause ===<br />
<br />
It is almost certainly due to some third party backup or other maintenance software opening the NEOSYS database files when it shouldn't e.g. badly configured third party backup scheduled to backup NEOSYS while NEOSYS is still running. Note that the exact filename varies each time.<br />
<br />
=== Solution ===<br />
<br />
This can be a serious error that causes damaged files in NEOSYS especially if the filename ends in .OV. Use the usual methods of checking for damaged files e.g. do a backup which also looks for damaged files BUT DO NOT OVERWRITE THE LATEST BACKUP SINCE IT MAY BE REQUIRED for restoration. Then fix the damaged files using the usual methods e.g. by rebuilding/using<br />
FIXFILE or restoring databases.<br />
<br />
=== Prevention ===<br />
<br />
Remove the third party backup or other maintenance software or reschedule it to run at a time that NEOSYS is shutdown. Removal of software may require hunting through the windows process list for unexpected programs running.<br />
<br />
== Resolving "Cannot backup/restore because PROCESS1 PROCESS2 (etc) is/are online" message ==<br />
<br />
This can happen for a variety of reasons if all the NEOSYS processes fail to close down at backup time<br />
<br />
# NEOSYS maintenance windows are left open.<br />
# NEOSYS processes hang due to software error.<br />
<br />
== How to kill hung NEOSYS processes ==<br />
<br />
NOTE WELL: If you kill actively working NEOSYS processes (those which are "listening" and not hung/crashed) there is a reasonable chance that the database will be damaged and might need a restore losing possibly large amounts of work.<br />
<br />
==== If NEOSYS processes are visible on the server desktop ====<br />
<br />
Look for processes which don't have "Listening ..." on the last but one line. The times on the left hand side are frozen as at the time of the hang.<br />
<br />
You can then click the X to kill the process and confirm that this is OK.<br />
<br />
Example of a NEOSYS process that has hung due to a software error resulting in a failure to handle a complex query with a lot of brand codes.<br />
<br />
[[Image:hungprocess.jpg]]<br />
<br />
==== If NEOSYS processes are not visible on the server desktop ====<br />
<br />
NEOSYS processes are most of the time visible on the desktop (i.e. the black dos windows) in Windows 2003 OS, except in the case that the process has been scheduled to start on computer restart and no one has logged into the server. In this case it would be running in the background. Secondly in the case of Windows 2008, the processes always are hidden. <br />
<br />
You can check if there are any hung processes from the NEOSYS Support Menu, List of Database Processes. <br />
[[Image:databaseprocesseslist.jpg]]<br />
<br />
In this case you should follow the below instructions - however all of them need to be done within 30 seconds of starting the first instruction to avoid inconvenience to the users. It is recommend that you keep relevant windows open before proceeding with the same:<br />
<br />
#Shutdown NEOSYS by TEMPORARILY putting a file called GLOBAL.END in the parent directory of NEOSYS (if there is already a GLOBAL.END.TEMP file then rename it to GLOBAL.END). Leaving the file there would prevent NEOSYS from starting up again. Shutting down NEOSYS from the Support menu will not work because of the hung processes.<br />
#Use Windows Task Manager to kill all the NTVDM processes - assuming that you have closed all the visible NEOSYS processes, then the NTVDM processes in the task manager would be the hung one.<br />
#Delete GLOBAL.END or rename it to GLOBAL.END.TEMP<br />
#Restart the processes back again. If there are many datasets then you need to restart them all well within the 30 seconds period.<br />
<br />
In case of Patsalides, where we have a thousand datasets which start "on demand" i.e. usually on login; all you need to do is start one dataset which will restart all the other datasets "on demand". If there is no response within 30 seconds then one of the running datasets will start it up so there appears to be a 30 second delay when you login to one of the thousand datasets the first time on any one day.<br />
<br />
=== Temporary workarounds for hung NEOSYS processes ===<br />
Until the error in the software is fixed users can often get their results by simplifying their requirements. For example select individual clients instead of selecting all the brands for a particular client. If the user has repeated his request (in forlorn hope that it would work finally) then the number of NEOSYS working NEOSYS processes will drop causing severe slowdown for other users and complete stop if all the NEOSYS processes hang.<br />
<br />
== How to fix a NEOSYS process which opens up in a notepad instead of Microsoft Windows Based Script Host (i.e. DOS window)==<br />
<br />
The NEOSYS process (cmd file) might open up in a notepad, instead of the usual black colour DOS window. This can be fixed by the following:<br />
<br />
# Download and install the Windows Script 5.6/5.7 from the Microsoft Website<br />
# Go to any folder, click on Tools > Folder Options > File Types and find the .JS and .JSE and change the default program to wscript.exe (from windows>system32)<br />
<br />
== Resolving a 'Could not start' error on Scheduled Tasks in Windows Server 2000 SP4 ==<br />
<br />
This error occurs because of a change that is made to the data that is stored in the credentials database when you install Windows 2000 SP4. Hence installing SP4 causes the the data that is stored in the credentials database to get converted to an SP4-compatible format. A registry key is configured to indicate that the data has been converted to the SP4 format.<br />
<br />
Hence the Scheduled Tasks do not work sometimes. However the Scheduled Tasks works fine sometimes, but when you uninstall SP4, it does not work.<br />
<br />
The best solution is to:<br />
<br />
# Incase Scheduled Tasks do not work after installing SP4, then uninstall SP4 and it should be fine.<br />
# Incase Scheduled Tasks works after installing SP4, and later after uninstalling SP4, it does not work, then install SP4 and it should be fine.<br />
<br />
== Checking for server or NEOSYS crashes ==<br />
<br />
#NEOSYS Maintenance Mode<br />
#General Menu, Setup, Processes<br />
#Select the dates and the option Detailed<br />
<br />
This report shows a list of dates and times that NEOSYS logged in but did not log out properly.<br />
<br />
Ignore the very latest entries since they represent the current NEOSYS processes. For example, if you have four NEOSYS processes running at the time that you get the report (including any in maintenance mode) then you can ignore the last four entries.<br />
<br />
The date and time shows for each process that has failed to shutdown correctly when the process logged in. Versions of NEOSYS from January 2008 will also show the date and time that each crashed NEOSYS process was last active (heartbeat) so that the time of failure can be known.<br />
<br />
If you see a bunch of NEOSYS processes all started up at around the same time but all failed to shutdown correctly then the cause will be a server failure - usually power failure.<br />
<br />
Isolated one-off failures will be related to individual NEOSYS process crashes - most commonly caused by one of the following:<br />
<br />
#NEOSYS hanging to due to software failure<br />
#Manually exiting a NEOSYS process on the server either by pressing Ctrl+Alt+Del or clicking the "X" close icon/box and ignoring the warning<br />
#Random server failures eg memory, disk etc<br />
<br />
Example:<br />
<br />
LOGIN 22/12/2007 06:02 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 06:00 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 06:01 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 06:02 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 08:52 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 08:52 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 08:53 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 8/1/2008 06:00 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 8/1/2008 06:01 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 8/1/2008 06:02 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 8/1/2008 13:51 NEOSYS SERVER NEOSYS Current user session <br />
<br />
Interpretation:<br />
<br />
The first four entries indicate that all four NEOSYS processes started at 06am were suddenly killed probably by power failure<br />
<br />
The next four entries indicate that NEOSYS was restarted at around 08:52 and all these processes were AGAIN killed probably by power failure<br />
<br />
The last four entries can be ignored because there were four NEOSYS processes running at the time that the report was generated<br />
<br />
== Searching for word/number in the database files using maintenance mode ==<br />
<br />
You can search for any word/number in the database files of NEOSYS, using the following command line:<br />
<br />
F5<br />
FIND FILENAME WORDWITHOUTANYSPACES<br />
<br />
For eg:<br />
FIND CURRENCIES 1.1<br />
(here you are searching for the number 1.1 in the currencies file) You CANNOT search for a phrase ie include spaces like this.<br />
<br />
Or you can also type:<br />
FIND FILENAME <enter><br />
and it will ask you what you want do to search. You can enter an exact phrase with spaces.<br />
<br />
Incase you do not know the filenames, you can enter the following command to see all the filenames in the system:<br />
<br />
F5<br />
LF<br />
<br />
== NO LOCK RECORD error when working on NEOSYS ==<br />
<br />
=== Error Message ===<br />
<br />
The following error message appears:<br />
<br />
Cannot save "DOCUMENT NAME" because:<br />
Somebody has updated this record.<br />
Your update cannot be applied.<br />
This session id does not agree "NO LOCK PERIOD"<br />
<br />
=== Possible Causes and Solutions ===<br />
<br />
1. There is some other error in NEOSYS software while saving the record.<br />
Probably another error message would come before this one and that message should be sent to NEOSYS in order to solve the actual problem.<br />
<br />
2. There has been a temporary loss of connection to the server for some period of time.<br />
The NEOSYS web page needs to periodically "refresh" the exclusive lock on the document being edited. If NEOSYS cannot perform the refresh it may lose the rights to save the document.<br />
<br />
Loss of connection could be for a huge variety of reasons including server, network, and workstation failures.<br />
<br />
3. Bad Internet Explorer Configuration<br />
Loss of cookies etc due to third party software (internet toolbars/spyware etc)<br />
<br />
Reset Internet Explorer to factory settings.<br />
<br />
<br />
== Troubleshooting the NTVDM Hard error when opening up NEOSYS processes ==<br />
<br />
=== Error Message ===<br />
<br />
The following error message appears:<br />
<br />
[[Image:ntvdm.jpg]]<br />
<br />
NTVDM encountered a hard error<br />
<br />
=== Solution ===<br />
<br />
This error is caused by missing or corrupt Windows system files (i.e. command.com, autoexec.nt and config.nt). The solution is to run a program called XP FIX which will reinstall these missing files. You can download it form http://www.visualtour.com/downloads/xp_fix.exe<br />
<br />
Sometimes even after running the XP FIX program the error still appears. Then you need to copy all the files under C:/windows/repair to C:/windows/system32 and in the autoexec.nt and config.nt put REM before any lines there which don't have it.<br />
<br />
== Troubleshooting a Service Unavailable message on Internet Explorer when opening up NEOSYS ==<br />
<br />
=== Error Message ===<br />
<br />
The following error message appears in Internet Explorer when you try to open up NEOSYS:<br />
<br />
Service Unavailable<br />
<br />
=== Solution ===<br />
<br />
Open the IIS Manager, right click Web Sites and select properties:<br />
[[Image:serviceunavailable1.jpg]]<br />
<br />
Switch to the Service Tab and tick the "Run WWW Service in IIS 5.0 Isolation Mode".<br />
[[Image:serviceunavailable2.jpg]]<br />
<br />
You will be asked for Restart of IIS. Click yes to restart IIS. If you are not asked just restart IIS.<br />
<br />
== Inspecting IIS log files ==<br />
<br />
At a windows command prompt:<br />
<br />
c:<br />
cd \Windows\system32\LogFiles\W3SVC1<br />
<br />
or<br />
<br />
%SystemDrive%<br />
cd %SystemRoot%<br />
cd system32\LogFiles\W3SVC1<br />
<br />
then (substituting the ip number you are interested in)<br />
<br />
find "192.168.1.55" *|sort>temp.log<br />
<br />
Open temp.log in Excel and use Tools, Data, Text to Columns to split into columns using options "Delimited" and check split on Space.<br />
<br />
Autowidth all columns by clicking on the top left box just outside the data to the left of column A and above column 1 then double click the column separator to the right of column "A"<br />
<br />
Note that times and dates are in UTC/GMT so you have to add/subtract your timezone offset to get local times.<br />
<br />
== Fixing NEOSYS processes that do not auto start / Recovering from incorrect advanced date or time ==<br />
<br />
=== Problem explained ===<br />
After starting up the 1st process, the rest of the processes don't start up.<br />
<br />
=== Solution ===<br />
<br />
The possible cause for this could be that the system date/time might have been changed - either manually or by the auto synchronization. Do the following checks in the sequence of order:<br />
<br />
# Check for any .$* files (* is a number, the highest being the latest one). If it shows OK, then proceed ahead.<br />
# Check for any .end files and delete it to rename to .end.temp<br />
# Check the System Event Viewer log for any 520 or 577 error message (refer http://128.175.24.251/forensics/timechange.htm). Also check for any out of sequence / ahead of today date or time.<br />
# In case of no 520 or 577 error message, go to Administrative Tools > Local Security Policy > Local Policies > Audit Policy > Audit Privilege use - make sure that Success and Failure are selected under this (this will ensure that future changes to the date/time are recorded in the System Log).<br />
# In NEOSYS maintenance mode - F5 ED PROCESSES %UPDATE% - and see what it says, incase of any text there, that means that for sure the system date has been changed.<br />
# Now to fix this, in maintenance mode again enter - F5 DELETE PROCESSES "%UPDATE%"<br />
<br />
<br />
== Recognising and Solving Low Memory Problems ==<br />
<br />
Quick Note: Installing a server class operating system on a workstation class computer with the intention of NEOSYS serving a heavy load is likely to cause problems with low memory.<br />
<br />
Quick Fix: Disable *ALL* non-essential features in the power-on setup menu.<br />
<br />
=== Effects ===<br />
<br />
It is speculated but not proven that low memory may cause NEOSYS to fail by hanging, causing damaged files etc.<br />
<br />
=== Checking ===<br />
<br />
F5<br />
MEMORY<br />
<br />
On server class machines it should say somewhere around 350Kb to 370Kb Free<br />
<br />
Some server class machines have around 330Kb and sometimes even less with no reported problems<br />
<br />
The actual effect of low memory is supposed to make NEOSYS slower and perhaps cause hanging and damaged files however this has not been proven in an specific case so far.<br />
<br />
On workstation class machines it may often say around 280Kb to 300Kb.<br />
<br />
=== Cause ===<br />
<br />
Although there is plenty of real memory in virtually all computers now, NEOSYS runs in the legacy 16 bit virtual memory space of a windows mode called NTVDM. This is limited to 1Mb plus 4Mb of EMS memory.<br />
<br />
The 1Mb memory space is shared with:<br />
<br />
#Various non-essential windows drivers which NEOSYS automatically disables them in autoexec.nt<br />
#Various plug and play hardware device drivers for the various adapters in the computer like video, network adapters and various other items that NEOSYS is unable to disable.<br />
<br />
In a server class computer the hardware device drivers are usually minimally present in the 1Mb base memory and do not therefore DOESNT a low memory situation for NEOSYS.<br />
<br />
In workstation class computers there are often many hardware device drivers present in the 1Mb base memory and this DOES causes a low memory situation for NEOSYS.<br />
<br />
When NEOSYS is installed on workstation class computers with XP there is usually not a heavy load expectation and therefore the low memory does not cause a problem.<br />
<br />
If Windows Server OS is installed on a workstation class computer NEOSYS may well be expected to serve a heavy load with limited amounts of memory.<br />
<br />
Workstation class computers: hardware drivers present and EMS is installed in low memory (0000-9FFF) causing low memory for NEOSYS and possible inability to <br />
<br />
Server class computers: Usually few hardware drivers are present in high part (A000-FFFF) of the 1Mb base memory and EMS is able to occupy the high memory leaving the low part (0000-9FFFF) of the 1Mb memory free for NEOSYS. You can find out how much memory is available to NEOSYS and whether EMS is occuping high or low memory using the following sections.<br />
<br />
=== Fixing Low Memory ===<br />
<br />
Start, Run, notepad c:\windows\system32\autoexec.nt<br />
<br />
Every time NEOSYS starts it tries to make some changes as follow:<br />
<br />
#replaces all lines in C:/WINDOWS/SYSTEM32/AUTOEXEC.NT starting with 'lh ' to start with 'rem NEOSYS LH ' instead.<br />
#changes the line in C:/WINDOWS/SYSTEM32/CONFIG.NT "files=..." to "FILES=200"<br />
<br />
The replacement is case sensitive triggered on 'lh' and 'files' so if you manually edit the files and remove the rem or change the number of files and leave the LH and FILES in uppercase then NEOSYS will NOT make further changes. This allows you to do manual amendments to the files without NEOSYS overwriting them.<br />
<br />
Check that NEOSYS has successfully disabled all the drivers in the lines starting with LH.<br />
<br />
They should be commented out (prefixed) with REM or REM NEOSYS as follows.<br />
<br />
After making changes reopen NEOSYS in maintenance mode to use the MEMORY and WHO commands again.<br />
<br />
<pre><br />
REM Install CD ROM extensions<br />
REM NEOSYS LH %SystemRoot%\system32\mscdexnt.exe<br />
<br />
REM Install network redirector (load before dosx.exe)<br />
REM NEOSYS LH %SystemRoot%\system32\redir<br />
<br />
REM Install DPMI support<br />
REM NEOSYS LH %SYSTEMROOT%\SYSTEM32\DOSX<br />
</pre><br />
<br />
=== Allowing DOS programs that require DOSX to run on the same computer as NEOSYS ===<br />
<br />
The automatic commenting out DOSX by NEOSYS will prevent some other DOS-like programs from running. If NEOSYS is on dedicated server then there should be no other such programs to fail. However, if you must allow DOS-like programs to work as well as NEOSYS you can do the following configuration:<br />
<br />
#leave or restore the original AUTOEXEC.NT and CONFIG.NT files where they are<br />
#copy them to another folder eg neosys folder<br />
#make the necessary REM changes there by hand<br />
#right click the NEOSYS\NEOSYS\AREV.PIF and select properties<br />
#change the location of the AUTOEXEC.NT and CONFIG.NT files in the following location<br />
<br />
[[image:pifsettings.jpg]]<br />
<br />
=== Checking EMS Memory Configuration ===<br />
<br />
==== Inspection ====<br />
<br />
F5<br />
WHO<br />
<br />
press the up arrow to get to the last part/page<br />
<br />
===== Example of Typical Server EMS Memory =====<br />
[[image:serveremm.jpg]]<br />
<br />
===== Example of Typical Workstation EMS Memory =====<br />
[[image:workstationemm.jpg]]<br />
<br />
====Correction====<br />
<br />
No easy way<br />
<br />
Removal of hardware adapters designed for workstations instead of servers eg graphics cards and network cards.<br />
<br />
Many of the devices may be located on the motherboard and not relocatable except possibly by BIOS configuration or special manufacturer information.<br />
<br />
Use windows device manager, View: Resources by Connection, Open the Memory item and look for items between 000A0000 up to 000FFFFF that might give you a clue as to what hardware could be removed or reconfigured. Actually only 000C0000 to 000FFFFF is candidate for EMS memory since 000A000-000BFFFF is mandatory video memory in all systems.<br />
<br />
[[image:devicemanager.jpg]]<br />
<br />
== Resolving issue where NEOSYS processes do not start-up at all or start-up and close immediately ==<br />
<br />
# Find if a file with the name global.end exists in the root directory of the NEOSYS installation. Eg D:\global.end . If you find such a file, rename it to global.end.temp - for more information on global.end and what it does refer to http://techwiki.neosys.com/index.php/Closing_NEOSYS_services<br />
# If the above didn't fix the problem and NEOSYS still does not start, do a windows search for the entire NEOSYS folder for *.end (i.e. any file ending with .end extension). You may find a (databasecode).end file in D:\neosys\neosys folder which is created by the NEOSYS program during backup at 1 am and later on removed automatically. In this case NEOSYS program might have crashed during the backup and left this file behind. (databasecode).end files prevent other other NEOSYS processes starting up on the database while exclusive processes (like backup) are being done.<br />
<br />
In case the above didn't fix the problem then escalate to the programmer immediately.<br />
<br />
== Handling Change Backup message if the client does not use a USB backup device ==<br />
DO *NOT* FOLLOW THIS PROCEDURE SINCE IS IT IS TOTALLY UNACCEPTABLE FOR NEOSYS TO SEND OUT A "BACKUP SUCCESS" MESSAGE WHEN THE BACKUP IS NOT BEING DONE PROPERLY. IN GENERAL, TAKING SHORT CUTS THAT MAKE THINGS APPEAR SATISFACTORY WHEN THEY ARE NOT IS VERY POOR POLICY.<br />
<br />
IF THE CLIENT IS BACKING UP TO A NON-REMOVABLE DESTINATION THEN EITHER 1. LIVE WITH THE FAILURE MESSAGE OR 2. SUPPRESS THE BACKUP ENTIRELY IN WHICH CASE NO BACKUPS ARE BEING DONE AND PROBABLY THIS WILL SHOW ON NEOSYS PROACTIVE WARNING SYSTEMS LIKE NAGIOS.<br />
<br />
# Basically most of the client use USB for Neosys server but there are some clients who do not use USB but save their backups in hard drive. <br />
# As we know that backup take place in Data.bak folder but it do a backup only for a week in a single USB. Over here client do not use USB but save their backup in hard drive in Data.bak folder, once the week is over it will again give Change backup message. <br />
# In this case rename the Data.bak folder to Data1.bak this is done because system read only Data.bak folder as it is configured in the system. When you rename Data.bak to Data1.bak it automatically create a new folder Data.bak in Backup drive.<br />
# This process is done so that the backup should not fail then next day morning and backups are done in Data.bak folder.<br />
# In the third week we will again see the same message Chang backup USB message so you need to rename Data.bak folder to Data2.bak<br />
# But in fourth week you rename the Data1.bak to Data.bak and change the Data2.bak to Data1.bak and Data.bak to Data2.bak <br />
# Keep only three folders and Data.bak, Data1.bak, Data2.bak and keep on renaming these folders every week as shown above.<br />
<br />
== Closing processes that are not visible on the desktop or hidden ==<br />
<br />
NEOSYS processes are most of the time visible on the desktop (i.e. the black dos windows) in Windows 2003 OS, except in the case that the process has been scheduled to start on restart and no one has logged into the server. In this case it would be hidden. Secondly in the case of Windows 2008, the processes always are hidden.<br />
<br />
In these cases whenever there is a hung NEOSYS process - due to many reasons for eg low memory. In this case you should close all processes using the global.end method and then from the task manager kill any NTVDM processes and then restart NEOSYS. This should be done within 30 seconds from using the global.end method to avoid any inconvenience to the users. If there are many datasets then you need to restart them all well within the 30 seconds period.<br />
<br />
In case of Patsalides, where we have a thousand datasets which start "on demand" i.e. usually on login; all you need to do is start one dataset which will restart all the other datasets "on demand". If there is no response within 30 seconds then one of the running datasets will start it up so there appears to be a 30 second delay when you login to one of the thousand datasets the first time on any one day.<br />
<br />
== NEOSYS not updating Nagios ==<br />
<br />
You find something like the following message in UPDATE.$WG in the neosys\neosys.folder<br />
<br />
Connecting to 192.168.100.145:8080 failed: No such file or directory.<br />
<br />
Where the above appears to be some non-functional http proxy server ip/port number and is not the expected nagios server ip number.<br />
<br />
The windows command proxycfg shows the same ip and port<br />
<br />
<pre><br />
D:\NEOSYS\NEOSYS>proxycfg<br />
Microsoft (R) WinHTTP Default Proxy Configuration Tool<br />
Copyright (c) Microsoft Corporation. All rights reserved.<br />
<br />
Current WinHTTP proxy settings under:<br />
HKEY_LOCAL_MACHINE\<br />
SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\<br />
WinHttpSettings :<br />
<br />
Proxy Server(s) : 192.168.100.145:8080<br />
Bypass List : 192.168.*.*;localhost;<local><br />
<br />
</pre><br />
<br />
=== Solution 1 - Remove the above setting to create a direct connection ===<br />
<br />
To remove the registry entries that ProxyCfg.exe creates,<br />
you must delete the WinHttpSettings value from the following registry key.<br />
<br />
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\WinHttpSettings<br />
<br />
After you do the above, confirm that the proxy details are deleted by running the proxycfg command.<br />
<br />
Next, restart the NEOSYS processes for the changes to be affected.<br />
<br />
=== Solution 2 – Configure a functioning proxy ip/port number ===<br />
<br />
Use the proxycfg command to enter a working proxy ip/port number/exclusion list<br />
<br />
http://msdn.microsoft.com/en-us/library/aa384069%28VS.85%29.aspx<br />
<br />
After you do the above, confirm that the new proxy details are working by running the proxycfg command again.<br />
<br />
Next, restart the NEOSYS processes for the changes to be affected.<br />
<br />
<B> Note: Please refer to the link before you restart NEOSYS processes http://techwiki.neosys.com/index.php/Troubleshooting_NEOSYS_Generally#Closing_processes_that_are_not_visible_on_the_desktop_or_hidden </B><br />
<br />
== Solving “page not found” when downloading some file types after uploading them successfully ==</div>Sunnyhttps://techwiki.neosys.com/index.php?title=Troubleshooting_NEOSYS_Generally&diff=598Troubleshooting NEOSYS Generally2010-10-24T13:46:43Z<p>Sunny: </p>
<hr />
<div>== Solving failure to start a NEOSYS server due to disk failure message ==<br />
<br />
=== Problem ===<br />
During a reboot process (which maybe due to a Windows update or even done by a support personnel) the NEOSYS server gets hung on the startup and shows a message "Boot Failure - Abort, Retry". <br />
<br />
=== Temporary solution ===<br />
This typically happens due to the USB being plugged into the server and the boot sequence being wrong - i.e. the server trying to boot from the USB first and fails. The immediate solution would be to unplug the USB and ask the client to reboot the server again and upon successfully rebooting the system, plug the USB back again.<br />
<br />
=== Permanent solution ===<br />
The above problem will occur every time the computer is rebooted, so you need to immediately talk to the IT Administrator of the client and ask them to rectify the boot sequence to make it boot first from the CD ROM, then the HDD and last the USB.<br />
<br />
== Solving "Read error in the operating system file" ==<br />
<br />
=== Problem ===<br />
<br />
Nagios reports a hung process and on the server a process has the following message popup.<br />
<br />
Read error in the operating system file "..\DATA\PT0833\ACCOUNTS\REV20049<br />
The file does not exist or the filename is<br />
not valid for the operating system.<br />
<br />
[[Image:readerrorintheoperatingsystemfile.png]]<br />
<br />
=== Cause ===<br />
<br />
Some non-NEOSYS program is directly accessing the NEOSYS database files while NEOSYS processes are running and using the files as well.<br />
<br />
*Client IT staff using a backup program to perform backup without ensuring that NEOSYS processes are shutdown.<br />
*A NEOSYS rsync process taking longer than expected due to new USB.<br />
<br />
=== Solution ===<br />
<br />
Kill the NEOSYS process eg with the X button. It is advisable NOT to let it run further while it cannot properly access one of its files.<br />
<br />
=== Prevention ===<br />
<br />
Remove the third party program or arrange for it to operate only while NEOSYS processes are shutdown eg from 3am-6am.<br />
<br />
== Handling damaged files ==<br />
<br />
[[Handling damaged files]]<br />
<br />
== Checking for corrupt database files ==<br />
<br />
Login to NEOSYS Maintenance<br />
<br />
Press F5<br />
<br />
CHK.FILES<br />
<br />
or <br />
<br />
CHK.FILES filename<br />
<br />
== Assessing Database Size per File ==<br />
<br />
In NEOSYS maintenance mode<br />
<br />
LIST FILES BY BY-DSND SIZE VOLUME.NAME SIZE<br />
<br />
This will include all files not just those in the actual dataset in DATA\* folders.<br />
<br />
== Resolving slow speed ==<br />
<br />
[[Benchmarking NEOSYS]]<br />
<br />
== Handling failure and warning on nightly backup alerts ==<br />
<br />
[[Handling failure and warning messages on nightly backup alerts]]<br />
<br />
== Resolving permissions errors while logging in ==<br />
<br />
=== Problem ===<br />
<br />
While logging in, you get the following error message:<br />
[[Image:login_error_message.jpg]]<br />
<br />
=== Solution ===<br />
<br />
Add the internet guest account to the security list of the data folder with the default permission of list/read/write<br />
<br />
Make sure the read&execute permission is removed<br />
[[Image:permissions_on_data.jpg]]<br />
<br />
<br />
== Resolving the 'HTTP Error 500.0 - Internal Server Error' while logging in on IE on a Windows Vista system ==<br />
<br />
=== Problem ===<br />
After configuring IIS on Windows Vista you will get this error message while trying to login into NEOSYS from Internet Explorer:<br />
<br />
HTTP Error 500.0 - Internal Server Error<br />
Description: This application is running in an application pool that uses the Integrated .NET <br />
mode. This is the preferred mode for running ASP.NET applications on the current and future <br />
version of IIS.<br />
<br />
In this mode, the application using client impersonation configured with <identity <br />
impersonate="true" /> may not behave correctly. Client impersonation is not available in early <br />
ASP.NET request processing stages and may lead modules in those stages to execute with process <br />
identity instead.<br />
<br />
=== Solution ===<br />
<br />
You can move the application to an application pool that uses the Classic .NET mode by using the following from a command line window (the window must be running as Administrator) <br />
<br />
%systemroot%\system32\inetsrv\APPCMD.EXE set app "Default Web Site/neosys" /applicationPool:"Classic .NET AppPool"<br />
<br />
Alternatively, you can use any other application pool on your system that is running in the Classic .NET mode. You can also use the IIS Administration tool to move this application to another application pool.<br />
<br />
<br />
== Resolving the 'Class Not Registered' error message while logging in ==<br />
<br />
=== Problem ===<br />
While logging into NEOSYS, you will get a popup window giving an error message saying 'Class Not Registered - Server Error'. Typically, you will encounter this error with XP Pro IIS 5.1. As usual, there's way to solve it, however the root cause of this is still unknown.<br />
<br />
Anyway, you will get the proper message in the event log:<br />
<br />
Event Type: Warning<br />
Event Source: W3SVC<br />
Event Category: None<br />
Event ID: 36<br />
Description: The server failed to load application '/LM/W3SVC/1/ROOT/NEOSYS.<br />
The error was 'Class not registered'. <br />
<br />
=== Solution ===<br />
So, what do you do ? This problem is related to Component Services, and when you open Component Services MMC, you will most probably get Error Code 8004E00F COM + was unable to talk to Microsoft Distributed Transaction Coordinator. So, fix the COM+ services first by using the following KB from Microsoft (PRB: Cannot Expand "My Computer" in Component Services MMC Snap-In http://support.microsoft.com/?id=301919):<br />
<br />
To resolve this problem, reinstall Component Services as follows: WARNING: <br />
# Open registry editor, locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3, and then delete this key. <br />
# From the Start menu, point to Settings, click Control Panel, and then click Add/Remove Programs. <br />
# Click Add/Remove Windows Components. <br />
# Proceed through the wizard, and accept all of the defaults (including IIS)<br />
# Restart the computer.<br />
<br />
If the above didn't solve it, and you still receive the 'Class not registered' error message, then you need to recreate the IIS packages in COM+, try<br />
<br />
# Delete IIS related package in Component Services MMC<br />
# IIS In-Process Applications <br />
# IIS Out-of-Process Pooled Applications <br />
# IIS Utilities<br />
<br />
Next, if you still get the message, try following before re-install IIS if you can't find Distributed Transaction Coordinator in your Services console.<br />
<br />
Launch command prompt and run the following command.<br />
# msdtc -install<br />
# net start msdtc<br />
<br />
Then try re-install IIS.<br />
<br />
This should solve the problem<br />
<br />
<br />
== Enabling File Security option on Win XP Professional ==<br />
<br />
=== Problem ===<br />
<br />
In the Properties of any folders, the Security option does not show, hence you cannot modify the Read, Write options.<br />
<br />
=== Solution ===<br />
<br />
The solution would be to untick the 'Simple File Sharing' option from Tools > Folder Options > View:<br />
[[Image:simplefilesharingoff.jpg]]<br />
<br />
== B10 & B12 Errors ==<br />
<br />
These errors are in the software and should be immediately escalated to the programmer.<br />
<br />
== Internet Explorer Menu, View, Text Size doesnt change font size as expected ==<br />
<br />
Cause: This is because the font size is now user definable in NEOSYS and View, Text Size does not override predefined font sizes.<br />
<br />
Solution: If you are using Internet Explorer 7 you can scale the screen (including the font size using ctrl + and ctrl - keyboard shortcuts or the font size button on the bottom right hand side of the window. <br />
<br />
You can adjust the font size on the User Details form when you login although this permanently applies to all forms not just the one that you are on.<br />
<br />
== Error on process window "Not enough string space - Out of Memory" ==<br />
<br />
=== Message ===<br />
<br />
‘RTP27’ Line 1. [B29] Not enough string space – Out of Memory.<br />
<br />
Not enough memory to execute Debugger; current program aborted.<br />
Press any key to continue<br />
<br />
[[Image:out_of_memory.jpg]]<br />
<br />
=== Cause ===<br />
Unknown perhaps related to some large document or report<br />
<br />
=== Solution ===<br />
Ask users for any hanging transactions.<br />
None other than closing and starting another process<br />
<br />
== Uploaded jpg files fail to display in internet explorer ==<br />
<br />
Some large jpg files > 2Mb cannot be viewed in internet explorer despite being viewable in image preview, ms paint and other viewers/editors. It is not an issue caused by uploading or downloading the files.<br />
<br />
These file appear to have been created on Photoshop CS Macintosh and may be a special type of uncompressed jpg used for production quality files.<br />
<br />
=== Partial solution ===<br />
Before uploading the files, open them in some editor like MS Paint (right click, edit) and save them. However this results in a loss of quality. Perhaps there is some program that can convert these files to a format understandable by Internet explorer without any loss of quality.<br />
<br />
<br />
== "You have attempted to write to a read-only file" ==<br />
<br />
=== Message ===<br />
<br />
Error while writing data.<br />
You have attempted to write to a read-only file.<br />
- or -<br />
access to the file has been denied by the operating system.<br />
(operating system file name: "..\DATA\ADLINEC\ADAGENCY\REV76467.OV00012618")<br />
<br />
=== Cause ===<br />
<br />
It is almost certainly due to some third party backup or other maintenance software opening the NEOSYS database files when it shouldn't e.g. badly configured third party backup scheduled to backup NEOSYS while NEOSYS is still running. Note that the exact filename varies each time.<br />
<br />
=== Solution ===<br />
<br />
This can be a serious error that causes damaged files in NEOSYS especially if the filename ends in .OV. Use the usual methods of checking for damaged files e.g. do a backup which also looks for damaged files BUT DO NOT OVERWRITE THE LATEST BACKUP SINCE IT MAY BE REQUIRED for restoration. Then fix the damaged files using the usual methods e.g. by rebuilding/using<br />
FIXFILE or restoring databases.<br />
<br />
=== Prevention ===<br />
<br />
Remove the third party backup or other maintenance software or reschedule it to run at a time that NEOSYS is shutdown. Removal of software may require hunting through the windows process list for unexpected programs running.<br />
<br />
== Resolving "Cannot backup/restore because PROCESS1 PROCESS2 (etc) is/are online" message ==<br />
<br />
This can happen for a variety of reasons if all the NEOSYS processes fail to close down at backup time<br />
<br />
# NEOSYS maintenance windows are left open.<br />
# NEOSYS processes hang due to software error.<br />
<br />
== How to kill hung NEOSYS processes ==<br />
<br />
NOTE WELL: If you kill actively working NEOSYS processes (those which are "listening" and not hung/crashed) there is a reasonable chance that the database will be damaged and might need a restore losing possibly large amounts of work.<br />
<br />
==== If NEOSYS processes are visible on the server desktop ====<br />
<br />
Look for processes which don't have "Listening ..." on the last but one line. The times on the left hand side are frozen as at the time of the hang.<br />
<br />
You can then click the X to kill the process and confirm that this is OK.<br />
<br />
Example of a NEOSYS process that has hung due to a software error resulting in a failure to handle a complex query with a lot of brand codes.<br />
<br />
[[Image:hungprocess.jpg]]<br />
<br />
==== If NEOSYS processes are not visible on the server desktop ====<br />
<br />
NEOSYS processes are most of the time visible on the desktop (i.e. the black dos windows) in Windows 2003 OS, except in the case that the process has been scheduled to start on computer restart and no one has logged into the server. In this case it would be running in the background. Secondly in the case of Windows 2008, the processes always are hidden. <br />
<br />
You can check if there are any hung processes from the NEOSYS Support Menu, List of Database Processes. <br />
[[Image:databaseprocesseslist.jpg]]<br />
<br />
In this case you should follow the below instructions - however all of them need to be done within 30 seconds of starting the first instruction to avoid inconvenience to the users. It is recommend that you keep relevant windows open before proceeding with the same:<br />
<br />
#Shutdown NEOSYS by TEMPORARILY putting a file called GLOBAL.END in the parent directory of NEOSYS (if there is already a GLOBAL.END.TEMP file then rename it to GLOBAL.END). Leaving the file there would prevent NEOSYS from starting up again. Shutting down NEOSYS from the Support menu will not work because of the hung processes.<br />
#Use Windows Task Manager to kill all the NTVDM processes - assuming that you have closed all the visible NEOSYS processes, then the NTVDM processes in the task manager would be the hung one.<br />
#Delete GLOBAL.END or rename it to GLOBAL.END.TEMP<br />
#Restart the processes back again. If there are many datasets then you need to restart them all well within the 30 seconds period.<br />
<br />
In case of Patsalides, where we have a thousand datasets which start "on demand" i.e. usually on login; all you need to do is start one dataset which will restart all the other datasets "on demand". If there is no response within 30 seconds then one of the running datasets will start it up so there appears to be a 30 second delay when you login to one of the thousand datasets the first time on any one day.<br />
<br />
=== Temporary workarounds for hung NEOSYS processes ===<br />
Until the error in the software is fixed users can often get their results by simplifying their requirements. For example select individual clients instead of selecting all the brands for a particular client. If the user has repeated his request (in forlorn hope that it would work finally) then the number of NEOSYS working NEOSYS processes will drop causing severe slowdown for other users and complete stop if all the NEOSYS processes hang.<br />
<br />
== How to fix a NEOSYS process which opens up in a notepad instead of Microsoft Windows Based Script Host (i.e. DOS window)==<br />
<br />
The NEOSYS process (cmd file) might open up in a notepad, instead of the usual black colour DOS window. This can be fixed by the following:<br />
<br />
# Download and install the Windows Script 5.6/5.7 from the Microsoft Website<br />
# Go to any folder, click on Tools > Folder Options > File Types and find the .JS and .JSE and change the default program to wscript.exe (from windows>system32)<br />
<br />
== Resolving a 'Could not start' error on Scheduled Tasks in Windows Server 2000 SP4 ==<br />
<br />
This error occurs because of a change that is made to the data that is stored in the credentials database when you install Windows 2000 SP4. Hence installing SP4 causes the the data that is stored in the credentials database to get converted to an SP4-compatible format. A registry key is configured to indicate that the data has been converted to the SP4 format.<br />
<br />
Hence the Scheduled Tasks do not work sometimes. However the Scheduled Tasks works fine sometimes, but when you uninstall SP4, it does not work.<br />
<br />
The best solution is to:<br />
<br />
# Incase Scheduled Tasks do not work after installing SP4, then uninstall SP4 and it should be fine.<br />
# Incase Scheduled Tasks works after installing SP4, and later after uninstalling SP4, it does not work, then install SP4 and it should be fine.<br />
<br />
== Checking for server or NEOSYS crashes ==<br />
<br />
#NEOSYS Maintenance Mode<br />
#General Menu, Setup, Processes<br />
#Select the dates and the option Detailed<br />
<br />
This report shows a list of dates and times that NEOSYS logged in but did not log out properly.<br />
<br />
Ignore the very latest entries since they represent the current NEOSYS processes. For example, if you have four NEOSYS processes running at the time that you get the report (including any in maintenance mode) then you can ignore the last four entries.<br />
<br />
The date and time shows for each process that has failed to shutdown correctly when the process logged in. Versions of NEOSYS from January 2008 will also show the date and time that each crashed NEOSYS process was last active (heartbeat) so that the time of failure can be known.<br />
<br />
If you see a bunch of NEOSYS processes all started up at around the same time but all failed to shutdown correctly then the cause will be a server failure - usually power failure.<br />
<br />
Isolated one-off failures will be related to individual NEOSYS process crashes - most commonly caused by one of the following:<br />
<br />
#NEOSYS hanging to due to software failure<br />
#Manually exiting a NEOSYS process on the server either by pressing Ctrl+Alt+Del or clicking the "X" close icon/box and ignoring the warning<br />
#Random server failures eg memory, disk etc<br />
<br />
Example:<br />
<br />
LOGIN 22/12/2007 06:02 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 06:00 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 06:01 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 06:02 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 08:52 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 08:52 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 23/12/2007 08:53 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 8/1/2008 06:00 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 8/1/2008 06:01 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 8/1/2008 06:02 NEOSYS SERVER ADAGENCY Current workstation <br />
LOGIN 8/1/2008 13:51 NEOSYS SERVER NEOSYS Current user session <br />
<br />
Interpretation:<br />
<br />
The first four entries indicate that all four NEOSYS processes started at 06am were suddenly killed probably by power failure<br />
<br />
The next four entries indicate that NEOSYS was restarted at around 08:52 and all these processes were AGAIN killed probably by power failure<br />
<br />
The last four entries can be ignored because there were four NEOSYS processes running at the time that the report was generated<br />
<br />
== Searching for word/number in the database files using maintenance mode ==<br />
<br />
You can search for any word/number in the database files of NEOSYS, using the following command line:<br />
<br />
F5<br />
FIND FILENAME WORDWITHOUTANYSPACES<br />
<br />
For eg:<br />
FIND CURRENCIES 1.1<br />
(here you are searching for the number 1.1 in the currencies file) You CANNOT search for a phrase ie include spaces like this.<br />
<br />
Or you can also type:<br />
FIND FILENAME <enter><br />
and it will ask you what you want do to search. You can enter an exact phrase with spaces.<br />
<br />
Incase you do not know the filenames, you can enter the following command to see all the filenames in the system:<br />
<br />
F5<br />
LF<br />
<br />
== NO LOCK RECORD error when working on NEOSYS ==<br />
<br />
=== Error Message ===<br />
<br />
The following error message appears:<br />
<br />
Cannot save "DOCUMENT NAME" because:<br />
Somebody has updated this record.<br />
Your update cannot be applied.<br />
This session id does not agree "NO LOCK PERIOD"<br />
<br />
=== Possible Causes and Solutions ===<br />
<br />
1. There is some other error in NEOSYS software while saving the record.<br />
Probably another error message would come before this one and that message should be sent to NEOSYS in order to solve the actual problem.<br />
<br />
2. There has been a temporary loss of connection to the server for some period of time.<br />
The NEOSYS web page needs to periodically "refresh" the exclusive lock on the document being edited. If NEOSYS cannot perform the refresh it may lose the rights to save the document.<br />
<br />
Loss of connection could be for a huge variety of reasons including server, network, and workstation failures.<br />
<br />
3. Bad Internet Explorer Configuration<br />
Loss of cookies etc due to third party software (internet toolbars/spyware etc)<br />
<br />
Reset Internet Explorer to factory settings.<br />
<br />
<br />
== Troubleshooting the NTVDM Hard error when opening up NEOSYS processes ==<br />
<br />
=== Error Message ===<br />
<br />
The following error message appears:<br />
<br />
[[Image:ntvdm.jpg]]<br />
<br />
NTVDM encountered a hard error<br />
<br />
=== Solution ===<br />
<br />
This error is caused by missing or corrupt Windows system files (i.e. command.com, autoexec.nt and config.nt). The solution is to run a program called XP FIX which will reinstall these missing files. You can download it form http://www.visualtour.com/downloads/xp_fix.exe<br />
<br />
Sometimes even after running the XP FIX program the error still appears. Then you need to copy all the files under C:/windows/repair to C:/windows/system32 and in the autoexec.nt and config.nt put REM before any lines there which don't have it.<br />
<br />
== Troubleshooting a Service Unavailable message on Internet Explorer when opening up NEOSYS ==<br />
<br />
=== Error Message ===<br />
<br />
The following error message appears in Internet Explorer when you try to open up NEOSYS:<br />
<br />
Service Unavailable<br />
<br />
=== Solution ===<br />
<br />
Open the IIS Manager, right click Web Sites and select properties:<br />
[[Image:serviceunavailable1.jpg]]<br />
<br />
Switch to the Service Tab and tick the "Run WWW Service in IIS 5.0 Isolation Mode".<br />
[[Image:serviceunavailable2.jpg]]<br />
<br />
You will be asked for Restart of IIS. Click yes to restart IIS. If you are not asked just restart IIS.<br />
<br />
== Inspecting IIS log files ==<br />
<br />
At a windows command prompt:<br />
<br />
c:<br />
cd \Windows\system32\LogFiles\W3SVC1<br />
<br />
or<br />
<br />
%SystemDrive%<br />
cd %SystemRoot%<br />
cd system32\LogFiles\W3SVC1<br />
<br />
then (substituting the ip number you are interested in)<br />
<br />
find "192.168.1.55" *|sort>temp.log<br />
<br />
Open temp.log in Excel and use Tools, Data, Text to Columns to split into columns using options "Delimited" and check split on Space.<br />
<br />
Autowidth all columns by clicking on the top left box just outside the data to the left of column A and above column 1 then double click the column separator to the right of column "A"<br />
<br />
Note that times and dates are in UTC/GMT so you have to add/subtract your timezone offset to get local times.<br />
<br />
== Fixing NEOSYS processes that do not auto start / Recovering from incorrect advanced date or time ==<br />
<br />
=== Problem explained ===<br />
After starting up the 1st process, the rest of the processes don't start up.<br />
<br />
=== Solution ===<br />
<br />
The possible cause for this could be that the system date/time might have been changed - either manually or by the auto synchronization. Do the following checks in the sequence of order:<br />
<br />
# Check for any .$* files (* is a number, the highest being the latest one). If it shows OK, then proceed ahead.<br />
# Check for any .end files and delete it to rename to .end.temp<br />
# Check the System Event Viewer log for any 520 or 577 error message (refer http://128.175.24.251/forensics/timechange.htm). Also check for any out of sequence / ahead of today date or time.<br />
# In case of no 520 or 577 error message, go to Administrative Tools > Local Security Policy > Local Policies > Audit Policy > Audit Privilege use - make sure that Success and Failure are selected under this (this will ensure that future changes to the date/time are recorded in the System Log).<br />
# In NEOSYS maintenance mode - F5 ED PROCESSES %UPDATE% - and see what it says, incase of any text there, that means that for sure the system date has been changed.<br />
# Now to fix this, in maintenance mode again enter - F5 DELETE PROCESSES "%UPDATE%"<br />
<br />
<br />
== Recognising and Solving Low Memory Problems ==<br />
<br />
Quick Note: Installing a server class operating system on a workstation class computer with the intention of NEOSYS serving a heavy load is likely to cause problems with low memory.<br />
<br />
Quick Fix: Disable *ALL* non-essential features in the power-on setup menu.<br />
<br />
=== Effects ===<br />
<br />
It is speculated but not proven that low memory may cause NEOSYS to fail by hanging, causing damaged files etc.<br />
<br />
=== Checking ===<br />
<br />
F5<br />
MEMORY<br />
<br />
On server class machines it should say somewhere around 350Kb to 370Kb Free<br />
<br />
Some server class machines have around 330Kb and sometimes even less with no reported problems<br />
<br />
The actual effect of low memory is supposed to make NEOSYS slower and perhaps cause hanging and damaged files however this has not been proven in an specific case so far.<br />
<br />
On workstation class machines it may often say around 280Kb to 300Kb.<br />
<br />
=== Cause ===<br />
<br />
Although there is plenty of real memory in virtually all computers now, NEOSYS runs in the legacy 16 bit virtual memory space of a windows mode called NTVDM. This is limited to 1Mb plus 4Mb of EMS memory.<br />
<br />
The 1Mb memory space is shared with:<br />
<br />
#Various non-essential windows drivers which NEOSYS automatically disables them in autoexec.nt<br />
#Various plug and play hardware device drivers for the various adapters in the computer like video, network adapters and various other items that NEOSYS is unable to disable.<br />
<br />
In a server class computer the hardware device drivers are usually minimally present in the 1Mb base memory and do not therefore DOESNT a low memory situation for NEOSYS.<br />
<br />
In workstation class computers there are often many hardware device drivers present in the 1Mb base memory and this DOES causes a low memory situation for NEOSYS.<br />
<br />
When NEOSYS is installed on workstation class computers with XP there is usually not a heavy load expectation and therefore the low memory does not cause a problem.<br />
<br />
If Windows Server OS is installed on a workstation class computer NEOSYS may well be expected to serve a heavy load with limited amounts of memory.<br />
<br />
Workstation class computers: hardware drivers present and EMS is installed in low memory (0000-9FFF) causing low memory for NEOSYS and possible inability to <br />
<br />
Server class computers: Usually few hardware drivers are present in high part (A000-FFFF) of the 1Mb base memory and EMS is able to occupy the high memory leaving the low part (0000-9FFFF) of the 1Mb memory free for NEOSYS. You can find out how much memory is available to NEOSYS and whether EMS is occuping high or low memory using the following sections.<br />
<br />
=== Fixing Low Memory ===<br />
<br />
Start, Run, notepad c:\windows\system32\autoexec.nt<br />
<br />
Every time NEOSYS starts it tries to make some changes as follow:<br />
<br />
#replaces all lines in C:/WINDOWS/SYSTEM32/AUTOEXEC.NT starting with 'lh ' to start with 'rem NEOSYS LH ' instead.<br />
#changes the line in C:/WINDOWS/SYSTEM32/CONFIG.NT "files=..." to "FILES=200"<br />
<br />
The replacement is case sensitive triggered on 'lh' and 'files' so if you manually edit the files and remove the rem or change the number of files and leave the LH and FILES in uppercase then NEOSYS will NOT make further changes. This allows you to do manual amendments to the files without NEOSYS overwriting them.<br />
<br />
Check that NEOSYS has successfully disabled all the drivers in the lines starting with LH.<br />
<br />
They should be commented out (prefixed) with REM or REM NEOSYS as follows.<br />
<br />
After making changes reopen NEOSYS in maintenance mode to use the MEMORY and WHO commands again.<br />
<br />
<pre><br />
REM Install CD ROM extensions<br />
REM NEOSYS LH %SystemRoot%\system32\mscdexnt.exe<br />
<br />
REM Install network redirector (load before dosx.exe)<br />
REM NEOSYS LH %SystemRoot%\system32\redir<br />
<br />
REM Install DPMI support<br />
REM NEOSYS LH %SYSTEMROOT%\SYSTEM32\DOSX<br />
</pre><br />
<br />
=== Allowing DOS programs that require DOSX to run on the same computer as NEOSYS ===<br />
<br />
The automatic commenting out DOSX by NEOSYS will prevent some other DOS-like programs from running. If NEOSYS is on dedicated server then there should be no other such programs to fail. However, if you must allow DOS-like programs to work as well as NEOSYS you can do the following configuration:<br />
<br />
#leave or restore the original AUTOEXEC.NT and CONFIG.NT files where they are<br />
#copy them to another folder eg neosys folder<br />
#make the necessary REM changes there by hand<br />
#right click the NEOSYS\NEOSYS\AREV.PIF and select properties<br />
#change the location of the AUTOEXEC.NT and CONFIG.NT files in the following location<br />
<br />
[[image:pifsettings.jpg]]<br />
<br />
=== Checking EMS Memory Configuration ===<br />
<br />
==== Inspection ====<br />
<br />
F5<br />
WHO<br />
<br />
press the up arrow to get to the last part/page<br />
<br />
===== Example of Typical Server EMS Memory =====<br />
[[image:serveremm.jpg]]<br />
<br />
===== Example of Typical Workstation EMS Memory =====<br />
[[image:workstationemm.jpg]]<br />
<br />
====Correction====<br />
<br />
No easy way<br />
<br />
Removal of hardware adapters designed for workstations instead of servers eg graphics cards and network cards.<br />
<br />
Many of the devices may be located on the motherboard and not relocatable except possibly by BIOS configuration or special manufacturer information.<br />
<br />
Use windows device manager, View: Resources by Connection, Open the Memory item and look for items between 000A0000 up to 000FFFFF that might give you a clue as to what hardware could be removed or reconfigured. Actually only 000C0000 to 000FFFFF is candidate for EMS memory since 000A000-000BFFFF is mandatory video memory in all systems.<br />
<br />
[[image:devicemanager.jpg]]<br />
<br />
== Resolving issue where NEOSYS processes do not start-up at all or start-up and close immediately ==<br />
<br />
# Find if a file with the name global.end exists in the root directory of the NEOSYS installation. Eg D:\global.end . If you find such a file, rename it to global.end.temp - for more information on global.end and what it does refer to http://techwiki.neosys.com/index.php/Closing_NEOSYS_services<br />
# If the above didn't fix the problem and NEOSYS still does not start, do a windows search for the entire NEOSYS folder for *.end (i.e. any file ending with .end extension). You may find a (databasecode).end file in D:\neosys\neosys folder which is created by the NEOSYS program during backup at 1 am and later on removed automatically. In this case NEOSYS program might have crashed during the backup and left this file behind. (databasecode).end files prevent other other NEOSYS processes starting up on the database while exclusive processes (like backup) are being done.<br />
<br />
In case the above didn't fix the problem then escalate to the programmer immediately.<br />
<br />
== Handling Change Backup message if the client does not use a USB backup device ==<br />
DO *NOT* FOLLOW THIS PROCEDURE SINCE IS IT IS TOTALLY UNACCEPTABLE FOR NEOSYS TO SEND OUT A "BACKUP SUCCESS" MESSAGE WHEN THE BACKUP IS NOT BEING DONE PROPERLY. IN GENERAL, TAKING SHORT CUTS THAT MAKE THINGS APPEAR SATISFACTORY WHEN THEY ARE NOT IS VERY POOR POLICY.<br />
<br />
IF THE CLIENT IS BACKING UP TO A NON-REMOVABLE DESTINATION THEN EITHER 1. LIVE WITH THE FAILURE MESSAGE OR 2. SUPPRESS THE BACKUP ENTIRELY IN WHICH CASE NO BACKUPS ARE BEING DONE AND PROBABLY THIS WILL SHOW ON NEOSYS PROACTIVE WARNING SYSTEMS LIKE NAGIOS.<br />
<br />
# Basically most of the client use USB for Neosys server but there are some clients who do not use USB but save their backups in hard drive. <br />
# As we know that backup take place in Data.bak folder but it do a backup only for a week in a single USB. Over here client do not use USB but save their backup in hard drive in Data.bak folder, once the week is over it will again give Change backup message. <br />
# In this case rename the Data.bak folder to Data1.bak this is done because system read only Data.bak folder as it is configured in the system. When you rename Data.bak to Data1.bak it automatically create a new folder Data.bak in Backup drive.<br />
# This process is done so that the backup should not fail then next day morning and backups are done in Data.bak folder.<br />
# In the third week we will again see the same message Chang backup USB message so you need to rename Data.bak folder to Data2.bak<br />
# But in fourth week you rename the Data1.bak to Data.bak and change the Data2.bak to Data1.bak and Data.bak to Data2.bak <br />
# Keep only three folders and Data.bak, Data1.bak, Data2.bak and keep on renaming these folders every week as shown above.<br />
<br />
== Closing processes that are not visible on the desktop or hidden ==<br />
<br />
NEOSYS processes are most of the time visible on the desktop (i.e. the black dos windows) in Windows 2003 OS, except in the case that the process has been scheduled to start on restart and no one has logged into the server. In this case it would be hidden. Secondly in the case of Windows 2008, the processes always are hidden.<br />
<br />
In these cases whenever there is a hung NEOSYS process - due to many reasons for eg low memory. In this case you should close all processes using the global.end method and then from the task manager kill any NTVDM processes and then restart NEOSYS. This should be done within 30 seconds from using the global.end method to avoid any inconvenience to the users. If there are many datasets then you need to restart them all well within the 30 seconds period.<br />
<br />
In case of Patsalides, where we have a thousand datasets which start "on demand" i.e. usually on login; all you need to do is start one dataset which will restart all the other datasets "on demand". If there is no response within 30 seconds then one of the running datasets will start it up so there appears to be a 30 second delay when you login to one of the thousand datasets the first time on any one day.<br />
<br />
== NEOSYS not updating Nagios ==<br />
<br />
You find something like the following message in UPDATE.$WG in the neosys\neosys.folder<br />
<br />
Connecting to 192.168.100.145:8080 failed: No such file or directory.<br />
<br />
Where the above appears to be some non-functional http proxy server ip/port number and is not the expected nagios server ip number.<br />
<br />
The windows command proxycfg shows the same ip and port<br />
<br />
<pre><br />
D:\NEOSYS\NEOSYS>proxycfg<br />
Microsoft (R) WinHTTP Default Proxy Configuration Tool<br />
Copyright (c) Microsoft Corporation. All rights reserved.<br />
<br />
Current WinHTTP proxy settings under:<br />
HKEY_LOCAL_MACHINE\<br />
SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\<br />
WinHttpSettings :<br />
<br />
Proxy Server(s) : 192.168.100.145:8080<br />
Bypass List : 192.168.*.*;localhost;<local><br />
<br />
</pre><br />
<br />
=== Solution 1 - Remove the above setting to create a direct connection ===<br />
<br />
To remove the registry entries that ProxyCfg.exe creates,<br />
you must delete the WinHttpSettings value from the following registry key.<br />
<br />
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\WinHttpSettings<br />
<br />
After you do the above, confirm that the proxy details are deleted by running the proxycfg command.<br />
<br />
Next, restart the NEOSYS processes for the changes to be affected.<br />
<br />
=== Solution 2 – Configure a functioning proxy ip/port number ===<br />
<br />
Use the proxycfg command to enter a working proxy ip/port number/exclusion list<br />
<br />
http://msdn.microsoft.com/en-us/library/aa384069%28VS.85%29.aspx<br />
<br />
After you do the above, confirm that the new proxy details are working by running the proxycfg command again.<br />
<br />
Next, restart the NEOSYS processes for the changes to be affected.<br />
<br />
<B> Note: Please refer to the link before you restart NEOSYS processes http://techwiki.neosys.com/index.php/Troubleshooting_NEOSYS_Generally#Closing_processes_that_are_not_visible_on_the_desktop_or_hidden </B></div>Sunnyhttps://techwiki.neosys.com/index.php?title=File:001.png&diff=421File:001.png2009-08-26T06:32:26Z<p>Sunny: </p>
<hr />
<div></div>Sunny