NEOSYS Technical Support Wiki - User contributions [en]

Setting up TCP/IP filtering

2008-06-25T13:59:53Z

77.68.3.139:

Tcp/ip filtering is a simple but effective firewall but cannot distinguish between incoming and outgoing traffic or do port forwarding.

All dedicated Neosys client servers which are installed in future will have TCP/IP filtering enabled and we will drop installation of anti-virus programs. However it the client has a workgroup anti-virus installation than it can be installed in addition to TCP/IP filtering.

Note:
#Despite Windows telling you that it is necessary to reboot to activate any changes, it is probably NOT necessary.
#Don't do changes while critical users are working or you cannot get power cycle the server since changing filtering sometimes causes network failure.

The following ports need to be opened when TCP/IP filtering is enabled:

*80/8123 web
*443/4430 secure web
*22/19580 ssh
*25/2500 smtp
*5500/55000 vnc reverse connection

and optionally
*3389/33890 rdc
*5900/59000 vnc

On our own NEOSYS server, some standard ports which need to be opened:

*21 standard ftp
*80 standard http
*443 standard https
*3389 standard remote desktop connection

NEOSYS non-standard ports

*2500 neosys smtp
*4430 neosys https port
*55000 neosys ultravnc reverse connection
*19580 neosys ssh port
*8000 neosys wiki

TCP/IP properties, advanced, options

[[Image:tcpipfiltering1.png]]

Setting up HTTPS

2008-06-19T14:22:40Z

77.68.3.139: /* Solution */

== Creating a single HTTPS web site ==

=== Creating a site in IIS ===

In order to run on the same port number, IIS sites need either unique ip numbers (set in tcp/http *and* ssh/https settings) or different host header values.

Therefore either the ip number has to be one of the available ones provided to neosys by leaseweb etc. or the host header value must be set to '''clientname'''.hosts.neosys.com.

The port number for tcp/http should be the neosys standard arbitrary port of 8123, not port 80 in order to prevent access via standard http. We could use various almost arbitrary ports for http since they are going to blocked by tcp/ip filtering or a firewall but it is better to know that port 8123 is the only one since IIS insists on having some port open for http.

The https options are only available after running selfssl (see below) at least once on the server.

[[Image:httpadvancedwebsitesetup.png]]

=== Install ssl/https on the site. ===

install selfssl.exe from Microsoft site (iis60rkt.exe available in neosys nl1 download folder) only the ssl utility is needed.

http://www.microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&displaylang=en

then

[[Image:SelfSSL.png]]

C:\Program Files\IIS Resources\SelfSSL>selfssl /v:9999 /s:'''''866651215''''' /p:4430 /n:CN='''''clientname'''''.hosts.neosys.com
Microsoft (R) SelfSSL Version 1.0
Copyright (C) 2003 Microsoft Corporation. All rights reserved.
Do you want to replace the SSL settings for site 866651215 (Y/N)?y
The self signed certificate was successfully assigned to site 866651215.

/v:9999 means valid for 9999 days
/s:'''''866651215''''' is the site number in this case (site number is shown in IIS management screen)
/p:4430 is the non-standard port number neosys uses by convention for ssl/https instead of the standard 443
/n:CN='''''clientname'''''.hosts.neosys.com indicates the full domain name of the site

You probably made a mistake in the site number if you get the following message.

Error opening site metabase key: 0x80070003

=== Testing access to the new https web site. ===

Make a subdomain '''clientname'''.hosts.neosys.com

https://'''clientname'''.hosts.neosys.com:4430/neosys

If you get certificate error:

#check that the selfsll /n:CN='''clientname'''.hosts.neosys.com matches the domain name used in IE
#install the certificate into the client computer (double click the padlock, view certificates etc)

closing all internet explorer versions and restarting is necessary for installed certificates to become effective.

== Creating multiple HTTPS web sites ==

=== Bugs ===

SelfSSL allows only one website to have SSL at a time

IIS Diagnostics Toolkit which has fixed SelfSSL but doesnt allow full control
http://www.microsoft.com/windowsserver2003/iis/diagnostictools/default.mspx

=== Solution ===

Use selfssl as follows:

#delete any existing certificate (IIS->directory security->server certificate wizard)
#create certificate for a site in selfssl following the normal procedure
#export the certificate to a pfx file (IIS->Site->directory security->server certificate wizard)
#remove the certificate (IIS->Site->directory security->server certificate wizard)
#import pfx certificate back (IIS->Site->directory security->server certificate wizard)

Continue adding sites this way and they should work perfectly fine. Just follow the sequence here for each site being added.

Certificates should be saved in d:\hosts\certificates preferably by name for easy reference otherwise by site number.

=== Re-installing Certificates ===

Sometimes due to an unknown issue, site/s stop working and hence there is a need to re-install the site certificate.

==== Re-installing Certificates from saved PFX files ====

Just do the first and last steps of the normal installation procedure.

#delete the existing certificate (IIS->Site->directory security->server certificate wizard)
#import pfx certificate (IIS->Site->directory security->server certificate wizard)

==== Re-installing Certificates from selfssl ====

Repeat the usual installation method above without missing the delete stage

If users have installed certificates in their browsers then they will have to reinstall them again to avoid the usual "certificate not trusted/matching" type problems.

Setting up HTTPS

2008-06-19T14:21:21Z

77.68.3.139: /* Re-installing Certificates */

== Creating a single HTTPS web site ==

=== Creating a site in IIS ===

In order to run on the same port number, IIS sites need either unique ip numbers (set in tcp/http *and* ssh/https settings) or different host header values.

Therefore either the ip number has to be one of the available ones provided to neosys by leaseweb etc. or the host header value must be set to '''clientname'''.hosts.neosys.com.

The port number for tcp/http should be the neosys standard arbitrary port of 8123, not port 80 in order to prevent access via standard http. We could use various almost arbitrary ports for http since they are going to blocked by tcp/ip filtering or a firewall but it is better to know that port 8123 is the only one since IIS insists on having some port open for http.

The https options are only available after running selfssl (see below) at least once on the server.

[[Image:httpadvancedwebsitesetup.png]]

=== Install ssl/https on the site. ===

install selfssl.exe from Microsoft site (iis60rkt.exe available in neosys nl1 download folder) only the ssl utility is needed.

http://www.microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&displaylang=en

then

[[Image:SelfSSL.png]]

C:\Program Files\IIS Resources\SelfSSL>selfssl /v:9999 /s:'''''866651215''''' /p:4430 /n:CN='''''clientname'''''.hosts.neosys.com
Microsoft (R) SelfSSL Version 1.0
Copyright (C) 2003 Microsoft Corporation. All rights reserved.
Do you want to replace the SSL settings for site 866651215 (Y/N)?y
The self signed certificate was successfully assigned to site 866651215.

/v:9999 means valid for 9999 days
/s:'''''866651215''''' is the site number in this case (site number is shown in IIS management screen)
/p:4430 is the non-standard port number neosys uses by convention for ssl/https instead of the standard 443
/n:CN='''''clientname'''''.hosts.neosys.com indicates the full domain name of the site

You probably made a mistake in the site number if you get the following message.

Error opening site metabase key: 0x80070003

=== Testing access to the new https web site. ===

Make a subdomain '''clientname'''.hosts.neosys.com

https://'''clientname'''.hosts.neosys.com:4430/neosys

If you get certificate error:

#check that the selfsll /n:CN='''clientname'''.hosts.neosys.com matches the domain name used in IE
#install the certificate into the client computer (double click the padlock, view certificates etc)

closing all internet explorer versions and restarting is necessary for installed certificates to become effective.

== Creating multiple HTTPS web sites ==

=== Bugs ===

SelfSSL allows only one website to have SSL at a time

IIS Diagnostics Toolkit which has fixed SelfSSL but doesnt allow full control
http://www.microsoft.com/windowsserver2003/iis/diagnostictools/default.mspx

=== Solution ===

Use selfssl as follows:

#delete any existing certificate (IIS->directory security->server certificate wizard)
#create certificate for a site in selfssl following the normal procedure
#export the certificate to a pfx file (IIS->Site->directory security->server certificate wizard)
#remove the certificate (IIS->Site->directory security->server certificate wizard)
#import pfx certificate back (IIS->Site->directory security->server certificate wizard)

Continue adding sites this way and they should work perfectly fine. Just follow the sequence here for each site being added.

=== Re-installing Certificates ===

Sometimes due to an unknown issue, site/s stop working and hence there is a need to re-install the site certificate.

==== Re-installing Certificates from saved PFX files ====

Just do the first and last steps of the normal installation procedure.

#delete the existing certificate (IIS->Site->directory security->server certificate wizard)
#import pfx certificate (IIS->Site->directory security->server certificate wizard)

==== Re-installing Certificates from selfssl ====

Repeat the usual installation method above without missing the delete stage

If users have installed certificates in their browsers then they will have to reinstall them again to avoid the usual "certificate not trusted/matching" type problems.

Setting up HTTPS

2008-06-19T14:20:15Z

77.68.3.139: /* Creating multiple HTTPS web sites */

== Creating a single HTTPS web site ==

=== Creating a site in IIS ===

In order to run on the same port number, IIS sites need either unique ip numbers (set in tcp/http *and* ssh/https settings) or different host header values.

Therefore either the ip number has to be one of the available ones provided to neosys by leaseweb etc. or the host header value must be set to '''clientname'''.hosts.neosys.com.

The port number for tcp/http should be the neosys standard arbitrary port of 8123, not port 80 in order to prevent access via standard http. We could use various almost arbitrary ports for http since they are going to blocked by tcp/ip filtering or a firewall but it is better to know that port 8123 is the only one since IIS insists on having some port open for http.

The https options are only available after running selfssl (see below) at least once on the server.

[[Image:httpadvancedwebsitesetup.png]]

=== Install ssl/https on the site. ===

install selfssl.exe from Microsoft site (iis60rkt.exe available in neosys nl1 download folder) only the ssl utility is needed.

http://www.microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&displaylang=en

then

[[Image:SelfSSL.png]]

C:\Program Files\IIS Resources\SelfSSL>selfssl /v:9999 /s:'''''866651215''''' /p:4430 /n:CN='''''clientname'''''.hosts.neosys.com
Microsoft (R) SelfSSL Version 1.0
Copyright (C) 2003 Microsoft Corporation. All rights reserved.
Do you want to replace the SSL settings for site 866651215 (Y/N)?y
The self signed certificate was successfully assigned to site 866651215.

/v:9999 means valid for 9999 days
/s:'''''866651215''''' is the site number in this case (site number is shown in IIS management screen)
/p:4430 is the non-standard port number neosys uses by convention for ssl/https instead of the standard 443
/n:CN='''''clientname'''''.hosts.neosys.com indicates the full domain name of the site

You probably made a mistake in the site number if you get the following message.

Error opening site metabase key: 0x80070003

=== Testing access to the new https web site. ===

Make a subdomain '''clientname'''.hosts.neosys.com

https://'''clientname'''.hosts.neosys.com:4430/neosys

If you get certificate error:

#check that the selfsll /n:CN='''clientname'''.hosts.neosys.com matches the domain name used in IE
#install the certificate into the client computer (double click the padlock, view certificates etc)

closing all internet explorer versions and restarting is necessary for installed certificates to become effective.

== Creating multiple HTTPS web sites ==

=== Bugs ===

SelfSSL allows only one website to have SSL at a time

IIS Diagnostics Toolkit which has fixed SelfSSL but doesnt allow full control
http://www.microsoft.com/windowsserver2003/iis/diagnostictools/default.mspx

=== Solution ===

Use selfssl as follows:

#delete any existing certificate (IIS->directory security->server certificate wizard)
#create certificate for a site in selfssl following the normal procedure
#export the certificate to a pfx file (IIS->Site->directory security->server certificate wizard)
#remove the certificate (IIS->Site->directory security->server certificate wizard)
#import pfx certificate back (IIS->Site->directory security->server certificate wizard)

Continue adding sites this way and they should work perfectly fine. Just follow the sequence here for each site being added.

=== Re-installing Certificates ===

Sometimes due to an unknown issue, site/s stop working and hence there is a need to re-install the site certificate. The following procedure to be followed (actually we follow the same procedure as install, but step 1 is to delete the existing certificate):

==== Re-installing Certificates from saved PFX files ====

Just do the first and last steps of the normal installation procedure

#delete the existing certificate (IIS->Site->directory security->server certificate wizard)
#import pfx certificate (IIS->Site->directory security->server certificate wizard)

==== Re-installing Certificates from selfssl ====

Repeat the usual installation method above without missing the delete stage

If users have installed certificates in their browsers then they will have to reinstall them again to avoid the usual "certificate not trusted/matching" type problems.

Setting up HTTPS

2008-06-13T08:59:31Z

77.68.3.139: /* Install ssl/https on the site. */

== Creating a single HTTPS web site ==

=== Creating a site in IIS ===

In order to run on the same port number, IIS sites need either unique ip numbers (set in tcp/http *and* ssh/https settings) or different host header values.

Therefore either the ip number has to be one of the available ones provided to neosys by leaseweb etc. or the host header value must be set to '''clientname'''.hosts.neosys.com.

The port number for tcp/http should be the neosys standard arbitrary port of 8123, not port 80 in order to prevent access via standard http. We could use various almost arbitrary ports for http since they are going to blocked by tcp/ip filtering or a firewall but it is better to know that port 8123 is the only one since IIS insists on having some port open for http.

The https options are only available after running selfssl (see below) at least once on the server.

[[Image:httpadvancedwebsitesetup.png]]

=== Install ssl/https on the site. ===

install selfssl.exe from Microsoft site (iis60rkt.exe available in neosys nl1 download folder) only the ssl utility is needed.

http://www.microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&displaylang=en

then

[[Image:SelfSSL.png]]

C:\Program Files\IIS Resources\SelfSSL>selfssl /v:9999 /s:'''''866651215''''' /p:4430 /n:CN='''''clientname'''''.hosts.neosys.com
Microsoft (R) SelfSSL Version 1.0
Copyright (C) 2003 Microsoft Corporation. All rights reserved.
Do you want to replace the SSL settings for site 866651215 (Y/N)?y
The self signed certificate was successfully assigned to site 866651215.

/v:9999 means valid for 9999 days
/s:'''''866651215''''' is the site number in this case (site number is shown in IIS management screen)
/p:4430 is the non-standard port number neosys uses by convention for ssl/https instead of the standard 443
/n:CN='''''clientname'''''.hosts.neosys.com indicates the full domain name of the site

You probably made a mistake in the site number if you get the following message.

Error opening site metabase key: 0x80070003

=== Testing access to the new https web site. ===

Make a subdomain '''clientname'''.hosts.neosys.com

https://'''clientname'''.hosts.neosys.com:4430/neosys

If you get certificate error:

#check that the selfsll /n:CN='''clientname'''.hosts.neosys.com matches the domain name used in IE
#install the certificate into the client computer (double click the padlock, view certificates etc)

closing all internet explorer versions and restarting is necessary for installed certificates to become effective.

== Creating multiple HTTPS web sites ==

=== Bugs ===

SelfSSL allows only one website to have SSL at a time

IIS Diagnostics Toolkit which has fixed SelfSSL but doesnt allow full control
http://www.microsoft.com/windowsserver2003/iis/diagnostictools/default.mspx

=== Solution ===

Use selfssl as follows:

#create certificate for a site in selfssl following the normal procedure
#export the certificate to a pfx file (IIS->Site->directory security->server certificate wizard)
#remove the certificate (IIS->Site->directory security->server certificate wizard)
#import pfx certificate back (IIS->Site->directory security->server certificate wizard)

Continue adding sites this way and they should work perfectly fine. Just follow the sequence here for each site being added.

=== Re-installing Certificates ===

Sometimes due to an unknown issue, site/s stop working and hence there is a need to re-install the site certificate. The following procedure to be followed (actually we follow the same procedure as install, but step 1 is to delete the existing certificate):

==== Re-installing Certificates from selfssl ====

#Delete the existing certificate (IIS->directory security->server certificate wizard)
#create certificate for site in SELFSSL
#export the certificate to a pfx file (IIS->directory security->server certificate wizard)
#remove certificate from site (IIS->directory security->server certificate wizard)
#import pfx from step 3 using same wizard
#Done

==== Re-installing Certificates from saved PFX files ====

#Delete the existing certificate (IIS->Site->directory security->server certificate wizard)
#import pfx certificate (IIS->Site->directory security->server certificate wizard)
#Done

Handling damaged files

2008-05-25T07:31:14Z

77.68.3.139: /* Fixing damaged index files (names starting with !) */

== Symptoms ==

"A Damaged file has been found..... ((the rest of this message to be completed))
Group format Error:
OS File : BOOKING.TEXTS
Group# : 00000932
Record length incorrect or frame linkage error.

== Cause ==
Rare but nasty problem on server 99% caused by power failure, killing NEOSYS or server hardware or operating system failure.

*Did somebody kill NEOSYS processes to reboot the server or any other reason?
*Was there a power cut?
*Any expected or unexpected reboots in the server log? (see Event Viewer > System Log)
*Enough disk free space especially on servers not dedicated to neosys?

== Solution==

Depends on the cause and usually often requires aggressive interrogation to discover the cause.

== Recovery==

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.

See the following sections how to patch the damaged files.

== Files that are automatically fixed ==

*LISTS
*LOCKS
*!INDEXING

The above files are automatically checked for corruption (and initialised to empty if so) when you
startup a NEOSYS process and do not require any manual intervention apart from locating and eliminating the initial cause of the damage.

If the !INDEXING file was damaged then strictly speaking you should also do REINDEXALL to reinstate any possibly missing index entries, but since this will take a long time
you should do this when everybody is off the system in the evening probably.

== Fixing damaged files that have no process for recreating them ==

Some damaged files can be rebuilt using NEOSYS utilities especially index files with filenames starting with !. Other damaged files can be “fixed” to prevent NEOSYS crashes as follows but some records will most probably be lost. 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

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:

F5

FIXFILE filename

(Select option 1 to update the file)

In case you get any Overwrite messages – type YES, as these are the actual files being updated.

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.

=== Using FIXFILE to repair corrupted files ===

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.

You can freely use FIXFILE on any file but it 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. Many files do not have programs to rebuild them and FIXFILE is a quick way to get the system back in operation.

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.

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.

You must prevent anyone from accessing NEOSYS while FIXFILE is running.

=== Fixing Damaged DEFINITIONS file ===

==== Non-Solution ====

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.

CAUTION: DO NOT USE FIXFILE TO TRY AND FIX THE DEFINITIONS FILE.

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.

==== Partial Restore ====

You can copy recent DEFINITIONS.LK and DEFINITIONS.OV files from the DATA\datasetcode\GENERAL folder.

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.

==== Full Restore ====

Restore from your latest backup losing all work done since that time and date.

=== Preventing users from accessing NEOSYS in order to do maintenance or repairs ===

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

# Stop the autostart program/script
# Put a file called NET.CFG with a single line saying AUTOSTART=NO in the neosys\neosys folder
# Stop the IIS server
# Stop/Pause the particular web in question

== Fixing damaged file that have a process to recreate them ==

ADS file can be recreated with F5 CREATEADS

ANALYSIS file can be recreated with F5 CREATEANALYSIS

== Fixing damaged index files (names starting with !) ==

Whilst backing up or using NEOSYS the following error message might appear:

"A Damaged file has been found.....
Group format Error:
OS File : !ADS
Group# : 00000932
Record length incorrect or frame linkage error.

#Ensure that no-one is using NEOSYS
#Log into NEOSYS on the server
#Press F5 to get a TCL command box
#Type REINDEXADS and press enter.
#Wait until it finishes and you get back to the command box
#Type OFF in the command box and you will quit NEOSYS.

Other reindex commands are:

*REINDEXACCOUNTS recreates !ACCOUNTS, !BATCHES and !VOUCHERS
*REINDEXADDRESSES
*REINDEXADS
*REINDEXBOOKINGS recreates !BOOKING.ORDERS
*REINDEXBRANDS
*REINDEXCLIENTS
*REINDEXINVS recreates !INVOICES
*REINDEXJOBS
*REINDEXMATERIALS
*REINDEXPLANS
*REINDEXPRODINVS recreates !PRODUCTION.INVOICES
*REINDEXPRODORDERS recreates !PRODUCTION.ORDERS
*REINDEXRATECARDS
*REINDEXSCHEDULES
*REINDEXSUPPLIERS
*REINDEXTIMESHEETS
*REINDEXVEHICLES

REINDEXMEDIA does all the following
*REINDEXPLANS
*REINDEXSCHEDULES
*REINDEXADS
*REINDEXMATERIALS
*REINDEXBOOKINGS

REINDEXFILES does all the following
*REINDEXCLIENTS
*REINDEXBRANDS
*REINDEXSUPPLIERS
*REINDEXVEHICLES
*REINDEXRATECARDS

REINDEXPRODUCTION does all the following
*REINDEXJOBS
*REINDEXPRODORDERS
*REINDEXPRODINVS
*REINDEXTIMESHEETS

REINDEXALL does all the following
*REINDEXMEDIA
*REINDEXPRODUCTION
*REINDEXFILES
*REINDEXINVS
*REINDEXACCOUNTS
*REINDEXADDRESSES

== Dealing with damaged files that cannot be fixed ==

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.

THIS DOES NOT RELEASE NEOSYS SUPPORT STAFF FROM THE OBLIGATION TO PROACTIVELY INFORM THE CLIENT OF MEASURES TO PREVENT THE RECURRENCE OF THE EVENT.

The following are the steps to follow:

# Ascertain the cause of the damage to the database by looking at the internal logs
# Create a new database from the damaged one as it will contain the up to date but damaged database.
# Restore the database from the backup media so that the database is in the last good known state.
# 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.
# 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.

Template:Non-Liability For Backup

2008-03-23T08:31:59Z

77.68.3.139: New page: If a NEOSYS client has not signed the standard NEOSYS contract which excludes liability then NEOSYS needs a specific agreement to the following: Dear xxxxxxxx, NEOSYS has offered to se...

If a NEOSYS client has not signed the standard NEOSYS contract which excludes liability then NEOSYS needs a specific agreement to the following:

Dear xxxxxxxx,

NEOSYS has offered to setup a nightly backup of your NEOSYS data.

We can only do this on condition that you will not hold NEOSYS liable for damages of any kind in the case that our backup procedure fails to meet its essential purpose in an emergency.

You may make your own alternate parallel arrangements to ensure that the whole of the contents of the NEOSYS server are backed up sometime between 3am and 6am at night when NEOSYS system is shutdown.

Please confirm your agreement.

Best Regards, xxxx xxxx NEOSYS

Configuring NEOSYS Generally

2008-03-23T08:31:47Z

77.68.3.139: /* Configuring backup procedures */

=== Configuring letterhead ===
[[Configuring Letterhead]]

=== Configuring Client Security mark ===
All client installations are hardcoded with the name of the NEOSYS client allowed to use the software. This client mark is generated by the programmer and given to Technical Staff during installation and is a mandatory feature and cannot be removed. This Client security mark is printed on all documents generated out of NEOSYS and appears as below:

[[Image:clientsecuritymark.jpg]]

This can be changed incase the client's legal name changes.

The client security mark is configured by editing:

ED DEFINITIONS AGENCY.PARAMS

Line 1

This client mark can be displayed as an email hyperlink for all the reports generated (such as Media Diary, List of Ads Pending Booking, List of Invoices etc.) and this hyperlink can be configured by editing:

ED DOS SYSTEM.CFG

Line 10

=== Configuring fonts and colors for all users ===

Current latest version of NEOSYS software allows choice of font for all columnar reports and documents produced by NEOSYS.

The default for all NEOSYS reports and documents unless you follow this procedure is a dark and light buff yellow.

ED DEFINITIONS SYSTEM

line 46 then press Ctrl+E to edit multivalues (sublines)

mv 1: color for table column heading rows

mv 2: color for table body rows

mv 3: font

Press F9 to save, then Esc to get out of editing multivalues

Users can override the above the colors and fonts in their user details after login.

=== Changing the signatory ===

In Maintenance mode, press F5 and the following command:

ED DEFINITIONS AGENCY.PARAMS

Be careful not to insert lines except at the end. Moving other lines down will totally screw NEOSYS!

Than go to the bottom of the page (Ctrl+Page down). Once you reach at the bottom, ENTER enough times to add additional lines if required, than search for '''line 61''' (Ctrl+G) and edit the document / add this code:

 Name of General Manager General Manager 

=== Clearing files in database (done when you want to clean an old database) ===

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.

Clear data F5 CLEAROP (only clears transactions not reference files)

Clear suppliers F5 CLEARFILE SUPPLIERS

Clear Vehicles F5 CLEARFILE VEHICLES

Flush Index F5 FLUSH.INDEX

Clear all F5 CLEARALL (rather nasty command because clears all reference files as well)

=== Configuring backup procedures ===

==== Non-Liability for Backup ====

{{Non-Liability For Backup}}

==== Old Instructions ====

The following instructions have been superceded by the System Configuration File on the NEOSYS Support Menu.

There is no proper user interface to control the backup parameters and you must use NEOSYS maintenance mode and press F5 before the following commands.

ONE DATABASE - To control the backup of one database do this:

ED DEFINITIONS BACKUP

ONE INSTALLATION - To control the backup of all databases in one installation:

Any lines in the following override the above and affect all databases.

ED DOS BACKUP.CFG

MULTIPLE INSTALLATIONS - To control the backup of multiple parallel installations.

Any lines in the following override the above and affect all NEOSYS installations in the same folder.

ED DOS ..\..\BACKUP.CFG

What each line does is as follows:

*backup params
*1=date last attempted
**2= not used ... was workstation for backup (blank defaults to server)
*3=min time of day for backup to start (defaults to 02:00)
*4=max time of day for backup to start (defaults to 02:05)
*5=days to do backup 1234567 1=sun NIGHT!!! EG 2AM
*2/3/4/5 could be multivalued in parallel (to be programmed)
*6=tech support email addresse(s) separated by ';'
*7=backup disk letter
*8=mv list of datasets NOT to backup (press ctrl+E) (Not used if any datasets listed in Configuration File)
*9=1 disable both backup and shutdown completely
*10=email addresses to send backup.zip to OR replacement for 6 if 6 missing backups@neosys.com is excluded in NET from backup.zip recipients
*11=1=suppress backup but do shutdown (testdata) (Doesnt suppress if any datasets listed in Configuration File)
*12=backup disk for uploads (images) folder if different from 7. Put 0 to suppress backup.
*13=backup media check method: blank is default (weekly rotation) 1=wrong media doesnt fail the backup
*14=email address(es) for all log entries to be sent to (ALL - not just those related to backup)

==== Configuring which days the backup will be done on ====

Line 5 should a list of digits indicating desired days of week 1-7 where 1 is Monday

e.g. 23456 to backup on Mon-Fri night

NB Assuming the backups are at the default time of 2am then you must put "2"
for Monday night since it actually takes place on Tuesday at 2am.

==== Configuring email backup alerts ====

See lines 6 and 10 above

==== Excluding TEST, historical or other databases from backing up every night ====
Database backup is automatically skipped if the last four characters of the database code are TEST or the word TESTING or TRAINING is found in the database name or if the database code is found in the list of database codes (ctrl+e) not to be backed up in line 8 of BACKUP.CFG or if line 11 is set to 1.

==== Backing up the Images folder ====

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 be installed. Incase of old installations, please follow the Cygwin re-installation procedure at [[Setting_up_and_using_remote_support#Upgrading_SSHD_.2F_Cygwin]].

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:

line 12 - and specify the Drive of the location to be backed up to. eg. E or F

=== Configuring automated emails in NEOSYS ===

Login to NEOSYS Maintenance

Press F5

ED DEFINITIONS SMTP.CFG

and press enter (F9/Esc to save and exit)

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS SMTP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations. Available in NEOSYS versions dated 24/4/2007 onwards.

ED DOS ..\..\SMTP.CFG

Lines are fixed (only first two lines are required)

#sender email (must be acceptable to the smtp host name following)
#smtp host name (domain name or ip number)
#smtp port number (blank for 25)
#smtp timeout in seconds (blank for 60?)
#smto use ssl (1=yes, blank for no) ssl is secure connection
#smtp authorization type (1)
#smtp user
#smtp pass

Typical configuration

in DOS SMTP.CFG

clientname@neosys.com
mailout.neosys.com
2500

Note that neosys mail server will accept email from anywhere as long as the sender email is @neosys.com

=== Copying a single record from one database to another ===

You need to know the file name and record key of the record to be copied.

In this case the file is DEFINITIONS and the key is AGENCY.PARAMS

You can invent any old style 8.3 filename instead of C:\AGP.DAT in the following example

On the source computer:

F5
COPY DEFINITIONS AGENCY.PARAMS TO: (DOS C:\AGP.DAT)

On the target computer:

F5
COPY DOS C:\AGP.DAT (ON) TO: (DEFINITIONS AGENCY.PARAMS)

The (O) option is required to force overwrite of the existing

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.

== NEOSYS Authorisation File ==

=== Preventing users from assigning their own passwords ===

The task AUTHORISATION INVENT OWN PASSWORDS should always have the lock NEOSYS to prevent users from creating their own passwords. Most users create unsafe passwords given the choice.

People nearly always ask to give their own passwords but you should tell them that NEOSYS always assigns random passwords for security reasons. It is not worth arguing and discussing the point with most people since they don't usually grasp the importance and soon learn their NEOSYS password anyway.

NEOSYS support staff who login as NEOSYS are still authorised to create their own passwords but it is better not to leak this information to clients immediately since people will grasp on to it and be disappointed or even offended that you are not granting this privilege to them.

Unfortunately there is no general way for people to change their own passwords at the moment. Only the few people who have access to the Support Menu and Authorisation File can do it. Changing your own passwords should be on the NEOSYS Help menu so everybody can do it.

=== Authorising access from outside the LAN ===

From 15/2/2008 access to NEOSYS is by default restricted to users from the standard local area network ip numbers starting 192.168, 10 and 127 so you might get clients complaining that they cannot login.

In order to allow access from outside you will have to update the Authorisation File and put a list of valid ip numbers that they are authorised to login from.

You dont have to put ip numbers on every single user. If the user ip numbers are blank for a user then the system will look for and use the nearest ip numbers on the following users below within the same department. Therefore you only have to put the ip numbers on the bottom "department user".

==== Examples ====

To allow someone to login from a) anywhere in the office and b) from another office with a static ip number of say 80.11.22.33 put something like 192.168.*,10.*,127.*,80.11.22.33

To allow someone to login from anywhere put * This is not recommended but necessary if someone absolutely has to login from anywhere in the world.

== Allowing users temporary login as NEOSYS in maintenance mode ==

#Get them to login with any name even NEOSYS
#Get the to enter "?" for the pass without the quotes
#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
#Follow the NEOSYS lock/key procedure using the full contents of the lock including the user name
(to allow access EXCEPT access to authorisation screen use 132456 as the last number of the initial command)
#Give them the key and get them to enter and proceed

== Giving users access to the Support Menu ==

The Support Menu in NEOSYS enables users to access the following:

# List of Database processes
# List of Documents in use
# Stop/Restart NEOSYS service
# Backup
# Log
# Authorisation file

This menu is locked with the task SUPPORT MENU ACCESS and has the LS key. To give any user/I.T. administrator access to this menu, you have to give him the LS key.

== Configuring payment instruction text ==

NEOSYS picks up the first available payment instructions from the following locations and ignores any instructions in the later files.

#Client file
#Currency file
#Company file
#Configuration File

If, following the normal rules, the payment instructions are "NONE" then the instructions are blank.

There is a manually edited flag in the company file on one NEOSYS client (cannot remember which) which makes the company file payment instructions take precedence over any currency file payment instructions. This may be added to the Client File u/i as "For all currencies"

The usual way of configuring payment instructions is to put it in the Company file under Finance. However this does not allow for different payment instructions per currency. If you put the payment instructions in the currency file however, then these instructions apply to all companies unless you edit the manual flag in the company record to say that the company file instructions take precedence over. There is no way at the moment in NEOSYS to have different instructions per company AND per currency.

Tip: Since the rules of getting payment instructions are not simple, if you are *changing* payment instructions, locate where the old instructions are and simply change them without worrying about the rules.

== Configuring upload of photoshop "cs2" jpg files ==

Photoshop version "cs2" produces jpg files that cannot be viewed in Internet Explorer.

A solution is to rename the files extension from .jpg to .psjpg before uploading.

"psjpg" files are an invention of NEOSYS and IIS must be configured to handle .psjpg files as follows:

Windows Server 2003 (doesnt work on XP)

#Computer Management, Internet Information Server, Properties
#Click MIME Types
#Click New
#Extension: psjpg
#MIME Type: application/photoshop
#Click OK,OK,OK
#Restart IIS (Right click, All Tasks, Restart)

Installing NEOSYS Service

2008-03-21T06:19:17Z

77.68.3.139: /* Setting up daily scheduled tasks */

= INSTALLING NEOSYS SERVICE =

== Main installation: ==

Make sure NOT TO COPY an existing NEOSYS installation to another location and ONLY do a
completely new install with a fresh database, because copying a folder will copy a variety of
hidden configurations.

=== Preparing server for installation ===
It is advised that the server is not connected to the existing domain controller.

=== Locating servers ===

Before installation, ensure that Clients servers should be placed out of public areas for safety and also to ensure that USB flash drives for NEOSYS backup cannot be misappropriated.

=== Moving NEOSYS to new servers ===

Make sure you disable old systems BEFORE you enable new systems.

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.

Failure to follow this procedure OFTEN results in chaos in the clients procedures. Missing invoices, etc etc etc.

=== Installing NEOSYS on partitions ===

Good server management practice is to have separate partitions for operating system (C:) and data partitions (D:)

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.

==== Multiple Partitions ====

If there is more than one partition then NEOSYS should be installed on any partition (e.g. D:) except the operating system partition (usually C:).

==== Single Partition ====

If there is only one partition then depending on the level of sophistication of the client it may be advisable to go to the effort of reinstall the operating system or using third party repartitioning tools to create separate partitions.

Otherwise there is no overriding problem to have NEOSYS installed on the operating system.

=== Downloading and running installation files ===

# http://www.neosys.com/support/accounts.exe ... and install to X:\Neosys
# http://www.neosys.com/support/adagency.exe ... and install to X:\Neosys

=== Creating shortcuts ===

Make desktop shortcut ‘Maintenance’ to (or right click, send to desktop as shortcut)

x:\neosys\neosys\adagency.bat

or

x:\neosys\neosys\accounts.bat

=== Disabling network protocols in XP for client servers ===

Remove Windows protocols from ALL network adapters present in the machine whether in use or not. This is quick and easy since it does not require a reboot and provides a good degree of protection but does NOT replace the need for TCP/IP filtering for complete protection.

[[image:properties.jpg]]

Why should I remove the protocols which are not in use?

Not removing unnecessary protocols can result in slowin down the network communication or even pose as a security threat.

=== Activating NEOSYS using authorization number ===

Start NEOSYS Maintenance and it will give a “Computer Number” and ask for an “Authorisation No”

Send the computer number to NEOSYS admin to get the authorization no.

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.

=== Installing initial Database ===

First time entering maintenance you will enter a command box (like NEOSYS F5)

Type FILEMAN and then restore. You will need a BACKUP.ZIP file in C:\ containing the initial database. You can download this file from http://www.neosys.com/support/backup.zip

=== Creating a .CMD file to start NEOSYS Service: ===

In x:\neosys create a file startmain.cmd

x:
cd \neosys\neosys
Start neosys.js /system ADAGENCY /database databasecode

(where databasecode is the code of the database)

In x:\neosys create a file starttest.cmd

x:
cd \neosys\neosys
Start neosys.js /system ADAGENCY /database testdatabasecode

(where testdatabasecode is the code of the testdatabase)

=== Differences for Pure Accounts Module Only Installations ===

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.

=== Creating a .CMD file to copy maindata to testdata ===

In x:\neosys create a file copymain2test.cmd

Xcopy x:\neosys\data\maindatabasecode x:\neosys\data\testdatabasecode /s /y

=== Setting up daily scheduled tasks ===

Automatic Schedules:
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.

Manually Configured Schedules:

Automatic download & Install of Windows Update - to be configured at 3 am everyday

==== New Instructions ====

Main database 1 process starting at 6:00am.

Use Support Menu, System Configuration File to request 3 processes for main database and 1 for test database

==== Old Instructions ====

Maindata – 3 processes starting 6:00 am, 6:01 am, 6:02 am

Testdata – 1 process at 6:04 am

Copy Maindata to Testdata – 1 process at 1:45 am

For multiple sites on the same computer put the second site starting five minutes later at 6:05, third site starting five minutes earlier at 5:55, the third site starting five minutes later at 6:10 and so on.

=== Configuring NEOSYS to start automatically on server start-up ===

Unfortunately using this method the NEOSYS processes are not visible when you login as a user.

==== startall.cmd file ====

Make a startall.cmd file in the neosys folder something like this, where xxxx and xxxxtest are the names of the usual database start-up cmd files.

start cmd /c "start xxxx.cmd"
c:\cygwin\bin\sleep 5
start cmd /c "start xxxx.cmd"
c:\cygwin\bin\sleep 5
start cmd /c "start xxxx.cmd"
c:\cygwin\bin\sleep 5
start cmd /c "start xxxxtest.cmd"
c:\cygwin\bin\sleep 5

==== Windows scheduled task ====

[[Image:win_sch_task.jpg]]

Schedule a task to run the startall.cmd file whenever the computer starts

== Installing and upgrading NEOSYS pure accounting systems ==

Basic installation using ACCOUNTS.EXE and upgrades using ADAGENCY.EXE are identical to the normal adagency installation process.

Differences are as follows:

# Maintenance shortcut to ACCOUNTS.BAT
# Process startup file contains "/system ACCOUNTS" instead of "/system ADAGENCY"
# 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
# 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.

Installing NEOSYS Service

2008-03-21T06:15:24Z

77.68.3.139: /* Creating a .CMD file to start NEOSYS Service: */

= INSTALLING NEOSYS SERVICE =

== Main installation: ==

Make sure NOT TO COPY an existing NEOSYS installation to another location and ONLY do a
completely new install with a fresh database, because copying a folder will copy a variety of
hidden configurations.

=== Preparing server for installation ===
It is advised that the server is not connected to the existing domain controller.

=== Locating servers ===

Before installation, ensure that Clients servers should be placed out of public areas for safety and also to ensure that USB flash drives for NEOSYS backup cannot be misappropriated.

=== Moving NEOSYS to new servers ===

Make sure you disable old systems BEFORE you enable new systems.

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.

Failure to follow this procedure OFTEN results in chaos in the clients procedures. Missing invoices, etc etc etc.

=== Installing NEOSYS on partitions ===

Good server management practice is to have separate partitions for operating system (C:) and data partitions (D:)

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.

==== Multiple Partitions ====

If there is more than one partition then NEOSYS should be installed on any partition (e.g. D:) except the operating system partition (usually C:).

==== Single Partition ====

If there is only one partition then depending on the level of sophistication of the client it may be advisable to go to the effort of reinstall the operating system or using third party repartitioning tools to create separate partitions.

Otherwise there is no overriding problem to have NEOSYS installed on the operating system.

=== Downloading and running installation files ===

# http://www.neosys.com/support/accounts.exe ... and install to X:\Neosys
# http://www.neosys.com/support/adagency.exe ... and install to X:\Neosys

=== Creating shortcuts ===

Make desktop shortcut ‘Maintenance’ to (or right click, send to desktop as shortcut)

x:\neosys\neosys\adagency.bat

or

x:\neosys\neosys\accounts.bat

=== Disabling network protocols in XP for client servers ===

Remove Windows protocols from ALL network adapters present in the machine whether in use or not. This is quick and easy since it does not require a reboot and provides a good degree of protection but does NOT replace the need for TCP/IP filtering for complete protection.

[[image:properties.jpg]]

Why should I remove the protocols which are not in use?

Not removing unnecessary protocols can result in slowin down the network communication or even pose as a security threat.

=== Activating NEOSYS using authorization number ===

Start NEOSYS Maintenance and it will give a “Computer Number” and ask for an “Authorisation No”

Send the computer number to NEOSYS admin to get the authorization no.

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.

=== Installing initial Database ===

First time entering maintenance you will enter a command box (like NEOSYS F5)

Type FILEMAN and then restore. You will need a BACKUP.ZIP file in C:\ containing the initial database. You can download this file from http://www.neosys.com/support/backup.zip

=== Creating a .CMD file to start NEOSYS Service: ===

In x:\neosys create a file startmain.cmd

x:
cd \neosys\neosys
Start neosys.js /system ADAGENCY /database databasecode

(where databasecode is the code of the database)

In x:\neosys create a file starttest.cmd

x:
cd \neosys\neosys
Start neosys.js /system ADAGENCY /database testdatabasecode

(where testdatabasecode is the code of the testdatabase)

=== Differences for Pure Accounts Module Only Installations ===

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.

=== Creating a .CMD file to copy maindata to testdata ===

In x:\neosys create a file copymain2test.cmd

Xcopy x:\neosys\data\maindatabasecode x:\neosys\data\testdatabasecode /s /y

=== Setting up daily scheduled tasks ===

Automatic Schedules:
Neosys automatically shuts down at 2 am every morning for backup. It closes all the running processes and backups up to the selected drive.

Manually Configured Schedules:

Automatic download & Install of Windows Update - to be configured at 3 am everyday

Maindata – 3 processes starting 6:00 am, 6:01 am, 6:02 am

Testdata – 1 process at 6:04 am

Copy Maindata to Testdata – 1 process at 2:45 am

For multiple sites on the same computer put the second site starting five minutes later at 6:05, third site starting five minutes earlier at 5:55, the third site starting five minutes later at 6:10 and so on.

=== Configuring NEOSYS to start automatically on server start-up ===

Unfortunately using this method the NEOSYS processes are not visible when you login as a user.

==== startall.cmd file ====

Make a startall.cmd file in the neosys folder something like this, where xxxx and xxxxtest are the names of the usual database start-up cmd files.

start cmd /c "start xxxx.cmd"
c:\cygwin\bin\sleep 5
start cmd /c "start xxxx.cmd"
c:\cygwin\bin\sleep 5
start cmd /c "start xxxx.cmd"
c:\cygwin\bin\sleep 5
start cmd /c "start xxxxtest.cmd"
c:\cygwin\bin\sleep 5

==== Windows scheduled task ====

[[Image:win_sch_task.jpg]]

Schedule a task to run the startall.cmd file whenever the computer starts

== Installing and upgrading NEOSYS pure accounting systems ==

Basic installation using ACCOUNTS.EXE and upgrades using ADAGENCY.EXE are identical to the normal adagency installation process.

Differences are as follows:

# Maintenance shortcut to ACCOUNTS.BAT
# Process startup file contains "/system ACCOUNTS" instead of "/system ADAGENCY"
# 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
# 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.

Configuring NEOSYS Generally

2008-02-28T04:38:42Z

77.68.3.139: /* Configuring backup procedures */

=== Configuring letterhead ===
[[Configuring Letterhead]]

=== Configuring Client Security mark ===
All client installations are hardcoded with the name of the NEOSYS client allowed to use the software. This client mark is generated by the programmer and given to Technical Staff during installation and is a mandatory feature and cannot be removed. This Client security mark is printed on all documents generated out of NEOSYS and appears as below:

[[Image:clientsecuritymark.jpg]]

This can be changed incase the client's legal name changes.

The client security mark is configured by editing:

ED DEFINITIONS AGENCY.PARAMS

Line 1

This client mark can be displayed as an email hyperlink for all the reports generated (such as Media Diary, List of Ads Pending Booking, List of Invoices etc.) and this hyperlink can be configured by editing:

ED DOS SYSTEM.CFG

Line 10

=== Configuring fonts and colors for all users ===

Current latest version of NEOSYS software allows choice of font for all columnar reports and documents produced by NEOSYS.

The default for all NEOSYS reports and documents unless you follow this procedure is a dark and light buff yellow.

ED DEFINITIONS SYSTEM

line 46 then press Ctrl+E to edit multivalues (sublines)

mv 1: color for table column heading rows

mv 2: color for table body rows

mv 3: font

Press F9 to save, then Esc to get out of editing multivalues

Users can override the above the colors and fonts in their user details after login.

=== Changing the signatory ===

In Maintenance mode, press F5 and the following command:

ED DEFINITIONS AGENCY.PARAMS

Be careful not to insert lines except at the end. Moving other lines down will totally screw NEOSYS!

Than go to the bottom of the page (Ctrl+Page down). Once you reach at the bottom, ENTER enough times to add additional lines if required, than search for '''line 61''' (Ctrl+G) and edit the document / add this code:

 Name of General Manager General Manager 

=== Clearing files in database (done when you want to clean an old database) ===

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.

Clear data F5 CLEAROP (only clears transactions not reference files)

Clear suppliers F5 CLEARFILE SUPPLIERS

Clear Vehicles F5 CLEARFILE VEHICLES

Flush Index F5 FLUSH.INDEX

Clear all F5 CLEARALL (rather nasty command because clears all reference files as well)

=== Configuring backup procedures ===

There is no proper user interface to control the backup parameters and you must use NEOSYS maintenance mode and press F5 before the following commands.

ONE DATABASE - To control the backup of one database do this:

ED DEFINITIONS BACKUP

ONE INSTALLATION - To control the backup of all databases in one installation:

Any lines in the following override the above and affect all databases.

ED DOS BACKUP.CFG

MULTIPLE INSTALLATIONS - To control the backup of multiple parallel installations.

Any lines in the following override the above and affect all NEOSYS installations in the same folder.

ED DOS ..\..\BACKUP.CFG

What each line does is as follows:

*backup params
*1=date last attempted
**2= not used ... was workstation for backup (blank defaults to server)
*3=min time of day for backup to start (defaults to 02:00)
*4=max time of day for backup to start (defaults to 02:05)
*5=days to do backup 1234567 1=sun NIGHT!!! EG 2AM
*2/3/4/5 could be multivalued in parallel (to be programmed)
*6=tech support email addresse(s) separated by ';'
*7=backup disk letter
*8=mv list of datasets NOT to backup (press ctrl+E) (Not used if any datasets listed in Configuration File)
*9=1 disable both backup and shutdown completely
*10=email addresses to send backup.zip to OR replacement for 6 if 6 missing backups@neosys.com is excluded in NET from backup.zip recipients
*11=1=suppress backup but do shutdown (testdata) (Doesnt suppress if any datasets listed in Configuration File)
*12=backup disk for uploads (images) folder if different from 7. Put 0 to suppress backup.
*13=backup media check method: blank is default (weekly rotation) 1=wrong media doesnt fail the backup
*14=email address(es) for all log entries to be sent to (ALL - not just those related to backup)

==== Configuring which days the backup will be done on ====

Line 5 should a list of digits indicating desired days of week 1-7 where 1 is Monday

e.g. 23456 to backup on Mon-Fri night

NB Assuming the backups are at the default time of 2am then you must put "2"
for Monday night since it actually takes place on Tuesday at 2am.

==== Configuring email backup alerts ====

See lines 6 and 10 above

==== Excluding TEST, historical or other databases from backing up every night ====
Database backup is automatically skipped if the last four characters of the database code are TEST or the word TESTING or TRAINING is found in the database name or if the database code is found in the list of database codes (ctrl+e) not to be backed up in line 8 of BACKUP.CFG or if line 11 is set to 1.

==== Backing up the Images folder ====

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 be installed. Incase of old installations, please follow the Cygwin re-installation procedure at [[Setting_up_and_using_remote_support#Upgrading_SSHD_.2F_Cygwin]].

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:

line 12 - and specify the Drive of the location to be backed up to. eg. E or F

=== Configuring automated emails in NEOSYS ===

Login to NEOSYS Maintenance

Press F5

ED DEFINITIONS SMTP.CFG

and press enter (F9/Esc to save and exit)

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS SMTP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations. Available in NEOSYS versions dated 24/4/2007 onwards.

ED DOS ..\..\SMTP.CFG

Lines are fixed (only first two lines are required)

#sender email (must be acceptable to the smtp host name following)
#smtp host name (domain name or ip number)
#smtp port number (blank for 25)
#smtp timeout in seconds (blank for 60?)
#smto use ssl (1=yes, blank for no) ssl is secure connection
#smtp authorization type (1)
#smtp user
#smtp pass

Typical configuration

in DOS SMTP.CFG

clientname@neosys.com
mailout.neosys.com
2500

Note that neosys mail server will accept email from anywhere as long as the sender email is @neosys.com

=== Copying a single record from one database to another ===

You need to know the file name and record key of the record to be copied.

In this case the file is DEFINITIONS and the key is AGENCY.PARAMS

You can invent any old style 8.3 filename instead of C:\AGP.DAT in the following example

On the source computer:

F5
COPY DEFINITIONS AGENCY.PARAMS TO: (DOS C:\AGP.DAT)

On the target computer:

F5
COPY DOS C:\AGP.DAT (ON) TO: (DEFINITIONS AGENCY.PARAMS)

The (O) option is required to force overwrite of the existing

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.

== NEOSYS Authorisation File ==

=== Preventing users from assigning their own passwords ===

The task AUTHORISATION INVENT OWN PASSWORDS should always have the lock NEOSYS to prevent users from creating their own passwords. Most users create unsafe passwords given the choice.

People nearly always ask to give their own passwords but you should tell them that NEOSYS always assigns random passwords for security reasons. It is not worth arguing and discussing the point with most people since they don't usually grasp the importance and soon learn their NEOSYS password anyway.

NEOSYS support staff who login as NEOSYS are still authorised to create their own passwords but it is better not to leak this information to clients immediately since people will grasp on to it and be disappointed or even offended that you are not granting this privilege to them.

Unfortunately there is no general way for people to change their own passwords at the moment. Only the few people who have access to the Support Menu and Authorisation File can do it. Changing your own passwords should be on the NEOSYS Help menu so everybody can do it.

=== Authorising access from outside the LAN ===

From 15/2/2008 access to NEOSYS is by default restricted to users from the standard local area network ip numbers starting 192.168, 10 and 127 so you might get clients complaining that they cannot login.

In order to allow access from outside you will have to update the Authorisation File and put a list of valid ip numbers that they are authorised to login from.

You dont have to put ip numbers on every single user. If the user ip numbers are blank for a user then the system will look for and use the nearest ip numbers on the following users below within the same department. Therefore you only have to put the ip numbers on the bottom "department user".

==== Examples ====

To allow someone to login from a) anywhere in the office and b) from another office with a static ip number of say 80.11.22.33 put something like 192.168.*,10.*,127.*,80.11.22.33

To allow someone to login from anywhere put * This is not recommended but necessary if someone absolutely has to login from anywhere in the world.

== Allowing users temporary login as NEOSYS in maintenance mode ==

#Get them to login with any name even NEOSYS
#Get the to enter "?" for the pass without the quotes
#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
#Follow the NEOSYS lock/key procedure using the full contents of the lock including the user name
(to allow access EXCEPT access to authorisation screen use 132456 as the last number of the initial command)
#Give them the key and get them to enter and proceed

== Giving users access to the Support Menu ==

The Support Menu in NEOSYS enables users to access the following:

# List of Database processes
# List of Documents in use
# Stop/Restart NEOSYS service
# Backup
# Log
# Authorisation file

This menu is locked with the task SUPPORT MENU ACCESS and has the LS key. To give any user/I.T. administrator access to this menu, you have to give him the LS key.

== Configuring payment instruction text ==

NEOSYS picks up the first available payment instructions from the following locations and ignores any instructions in the later files.

#Client file
#Currency file
#Company file
#Configuration File

If, following the normal rules, the payment instructions are "NONE" then the instructions are blank.

There is a manually edited flag in the company file on one NEOSYS client (cannot remember which) which makes the company file payment instructions take precedence over any currency file payment instructions. This may be added to the Client File u/i as "For all currencies"

The usual way of configuring payment instructions is to put it in the Company file under Finance. However this does not allow for different payment instructions per currency. If you put the payment instructions in the currency file however, then these instructions apply to all companies unless you edit the manual flag in the company record to say that the company file instructions take precedence over. There is no way at the moment in NEOSYS to have different instructions per company AND per currency.

Tip: Since the rules of getting payment instructions are not simple, if you are *changing* payment instructions, locate where the old instructions are and simply change them without worrying about the rules.

== Configuring upload of photoshop "cs2" jpg files ==

Photoshop version "cs2" produces jpg files that cannot be viewed in Internet Explorer.

A solution is to rename the files extension from .jpg to .psjpg before uploading.

"psjpg" files are an invention of NEOSYS and IIS must be configured to handle .psjpg files as follows:

Windows Server 2003 (doesnt work on XP)

#Computer Management, Internet Information Server, Properties
#Click MIME Types
#Click New
#Extension: psjpg
#MIME Type: application/photoshop
#Click OK,OK,OK
#Restart IIS (Right click, All Tasks, Restart)

Configuring NEOSYS Generally

2008-02-28T04:37:58Z

77.68.3.139: /* Configuring backup procedures */

=== Configuring letterhead ===
[[Configuring Letterhead]]

=== Configuring Client Security mark ===
All client installations are hardcoded with the name of the NEOSYS client allowed to use the software. This client mark is generated by the programmer and given to Technical Staff during installation and is a mandatory feature and cannot be removed. This Client security mark is printed on all documents generated out of NEOSYS and appears as below:

[[Image:clientsecuritymark.jpg]]

This can be changed incase the client's legal name changes.

The client security mark is configured by editing:

ED DEFINITIONS AGENCY.PARAMS

Line 1

This client mark can be displayed as an email hyperlink for all the reports generated (such as Media Diary, List of Ads Pending Booking, List of Invoices etc.) and this hyperlink can be configured by editing:

ED DOS SYSTEM.CFG

Line 10

=== Configuring fonts and colors for all users ===

Current latest version of NEOSYS software allows choice of font for all columnar reports and documents produced by NEOSYS.

The default for all NEOSYS reports and documents unless you follow this procedure is a dark and light buff yellow.

ED DEFINITIONS SYSTEM

line 46 then press Ctrl+E to edit multivalues (sublines)

mv 1: color for table column heading rows

mv 2: color for table body rows

mv 3: font

Press F9 to save, then Esc to get out of editing multivalues

Users can override the above the colors and fonts in their user details after login.

=== Changing the signatory ===

In Maintenance mode, press F5 and the following command:

ED DEFINITIONS AGENCY.PARAMS

Be careful not to insert lines except at the end. Moving other lines down will totally screw NEOSYS!

Than go to the bottom of the page (Ctrl+Page down). Once you reach at the bottom, ENTER enough times to add additional lines if required, than search for '''line 61''' (Ctrl+G) and edit the document / add this code:

 Name of General Manager General Manager 

=== Clearing files in database (done when you want to clean an old database) ===

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.

Clear data F5 CLEAROP (only clears transactions not reference files)

Clear suppliers F5 CLEARFILE SUPPLIERS

Clear Vehicles F5 CLEARFILE VEHICLES

Flush Index F5 FLUSH.INDEX

Clear all F5 CLEARALL (rather nasty command because clears all reference files as well)

=== Configuring backup procedures ===

There is no proper user interface to control the backup parameters and you must use NEOSYS maintenance mode and press F5 before the following commands.

ONE DATABASE - To control the backup of one database do this:

ED DEFINITIONS BACKUP

ONE INSTALLATION - To control the backup of all databases in one installation:

Any lines in the following override the above and affect all databases.

ED DOS BACKUP.CFG

MULTIPLE INSTALLATIONS - To control the backup of multiple parallel installations.

Any lines in the following override the above and affect all NEOSYS installations in the same folder.

ED DOS ..\..\BACKUP.CFG

What each line does is as follows:

*backup params
*1=date last attempted
**2= not used ... was workstation for backup (blank defaults to server)
*3=min time of day for backup to start (defaults to 02:00)
*4=max time of day for backup to start (defaults to 02:05)
*5=days to do backup 1234567 1=sun NIGHT!!! EG 2AM
*2/3/4/5 could be multivalued in parallel (to be programmed)
*6=tech support email addresse(s) separated by ';'
*7=backup disk letter
*8=mv list of datasets NOT to backup (press ctrl+E) (Not used if any datasets listed in Configuration File)
*9=1 disable both backup and shutdown completely
*10=email addresses to send backup.zip to OR replacement for 6 if 6 missing backups@neosys.com is excluded in NET from backup.zip recipients
*11=1=suppress backup but do shutdown (testdata) (Doesnt suppress if any datasets listed defined in Configuration File)
*12=backup disk for uploads (images) folder if different from 7. Put 0 to suppress backup.
*13=backup media check method: blank is default (weekly rotation) 1=wrong media doesnt fail the backup
*14=email address(es) for all log entries to be sent to (ALL - not just those related to backup)

==== Configuring which days the backup will be done on ====

Line 5 should a list of digits indicating desired days of week 1-7 where 1 is Monday

e.g. 23456 to backup on Mon-Fri night

NB Assuming the backups are at the default time of 2am then you must put "2"
for Monday night since it actually takes place on Tuesday at 2am.

==== Configuring email backup alerts ====

See lines 6 and 10 above

==== Excluding TEST, historical or other databases from backing up every night ====
Database backup is automatically skipped if the last four characters of the database code are TEST or the word TESTING or TRAINING is found in the database name or if the database code is found in the list of database codes (ctrl+e) not to be backed up in line 8 of BACKUP.CFG or if line 11 is set to 1.

==== Backing up the Images folder ====

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 be installed. Incase of old installations, please follow the Cygwin re-installation procedure at [[Setting_up_and_using_remote_support#Upgrading_SSHD_.2F_Cygwin]].

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:

line 12 - and specify the Drive of the location to be backed up to. eg. E or F

=== Configuring automated emails in NEOSYS ===

Login to NEOSYS Maintenance

Press F5

ED DEFINITIONS SMTP.CFG

and press enter (F9/Esc to save and exit)

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS SMTP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations. Available in NEOSYS versions dated 24/4/2007 onwards.

ED DOS ..\..\SMTP.CFG

Lines are fixed (only first two lines are required)

#sender email (must be acceptable to the smtp host name following)
#smtp host name (domain name or ip number)
#smtp port number (blank for 25)
#smtp timeout in seconds (blank for 60?)
#smto use ssl (1=yes, blank for no) ssl is secure connection
#smtp authorization type (1)
#smtp user
#smtp pass

Typical configuration

in DOS SMTP.CFG

clientname@neosys.com
mailout.neosys.com
2500

Note that neosys mail server will accept email from anywhere as long as the sender email is @neosys.com

=== Copying a single record from one database to another ===

You need to know the file name and record key of the record to be copied.

In this case the file is DEFINITIONS and the key is AGENCY.PARAMS

You can invent any old style 8.3 filename instead of C:\AGP.DAT in the following example

On the source computer:

F5
COPY DEFINITIONS AGENCY.PARAMS TO: (DOS C:\AGP.DAT)

On the target computer:

F5
COPY DOS C:\AGP.DAT (ON) TO: (DEFINITIONS AGENCY.PARAMS)

The (O) option is required to force overwrite of the existing

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.

== NEOSYS Authorisation File ==

=== Preventing users from assigning their own passwords ===

The task AUTHORISATION INVENT OWN PASSWORDS should always have the lock NEOSYS to prevent users from creating their own passwords. Most users create unsafe passwords given the choice.

People nearly always ask to give their own passwords but you should tell them that NEOSYS always assigns random passwords for security reasons. It is not worth arguing and discussing the point with most people since they don't usually grasp the importance and soon learn their NEOSYS password anyway.

NEOSYS support staff who login as NEOSYS are still authorised to create their own passwords but it is better not to leak this information to clients immediately since people will grasp on to it and be disappointed or even offended that you are not granting this privilege to them.

Unfortunately there is no general way for people to change their own passwords at the moment. Only the few people who have access to the Support Menu and Authorisation File can do it. Changing your own passwords should be on the NEOSYS Help menu so everybody can do it.

=== Authorising access from outside the LAN ===

From 15/2/2008 access to NEOSYS is by default restricted to users from the standard local area network ip numbers starting 192.168, 10 and 127 so you might get clients complaining that they cannot login.

In order to allow access from outside you will have to update the Authorisation File and put a list of valid ip numbers that they are authorised to login from.

You dont have to put ip numbers on every single user. If the user ip numbers are blank for a user then the system will look for and use the nearest ip numbers on the following users below within the same department. Therefore you only have to put the ip numbers on the bottom "department user".

==== Examples ====

To allow someone to login from a) anywhere in the office and b) from another office with a static ip number of say 80.11.22.33 put something like 192.168.*,10.*,127.*,80.11.22.33

To allow someone to login from anywhere put * This is not recommended but necessary if someone absolutely has to login from anywhere in the world.

== Allowing users temporary login as NEOSYS in maintenance mode ==

#Get them to login with any name even NEOSYS
#Get the to enter "?" for the pass without the quotes
#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
#Follow the NEOSYS lock/key procedure using the full contents of the lock including the user name
(to allow access EXCEPT access to authorisation screen use 132456 as the last number of the initial command)
#Give them the key and get them to enter and proceed

== Giving users access to the Support Menu ==

The Support Menu in NEOSYS enables users to access the following:

# List of Database processes
# List of Documents in use
# Stop/Restart NEOSYS service
# Backup
# Log
# Authorisation file

This menu is locked with the task SUPPORT MENU ACCESS and has the LS key. To give any user/I.T. administrator access to this menu, you have to give him the LS key.

== Configuring payment instruction text ==

NEOSYS picks up the first available payment instructions from the following locations and ignores any instructions in the later files.

#Client file
#Currency file
#Company file
#Configuration File

If, following the normal rules, the payment instructions are "NONE" then the instructions are blank.

There is a manually edited flag in the company file on one NEOSYS client (cannot remember which) which makes the company file payment instructions take precedence over any currency file payment instructions. This may be added to the Client File u/i as "For all currencies"

The usual way of configuring payment instructions is to put it in the Company file under Finance. However this does not allow for different payment instructions per currency. If you put the payment instructions in the currency file however, then these instructions apply to all companies unless you edit the manual flag in the company record to say that the company file instructions take precedence over. There is no way at the moment in NEOSYS to have different instructions per company AND per currency.

Tip: Since the rules of getting payment instructions are not simple, if you are *changing* payment instructions, locate where the old instructions are and simply change them without worrying about the rules.

== Configuring upload of photoshop "cs2" jpg files ==

Photoshop version "cs2" produces jpg files that cannot be viewed in Internet Explorer.

A solution is to rename the files extension from .jpg to .psjpg before uploading.

"psjpg" files are an invention of NEOSYS and IIS must be configured to handle .psjpg files as follows:

Windows Server 2003 (doesnt work on XP)

#Computer Management, Internet Information Server, Properties
#Click MIME Types
#Click New
#Extension: psjpg
#MIME Type: application/photoshop
#Click OK,OK,OK
#Restart IIS (Right click, All Tasks, Restart)

Configuring NEOSYS Generally

2008-02-28T04:37:12Z

77.68.3.139: /* Configuring backup procedures */

=== Configuring letterhead ===
[[Configuring Letterhead]]

=== Configuring Client Security mark ===
All client installations are hardcoded with the name of the NEOSYS client allowed to use the software. This client mark is generated by the programmer and given to Technical Staff during installation and is a mandatory feature and cannot be removed. This Client security mark is printed on all documents generated out of NEOSYS and appears as below:

[[Image:clientsecuritymark.jpg]]

This can be changed incase the client's legal name changes.

The client security mark is configured by editing:

ED DEFINITIONS AGENCY.PARAMS

Line 1

This client mark can be displayed as an email hyperlink for all the reports generated (such as Media Diary, List of Ads Pending Booking, List of Invoices etc.) and this hyperlink can be configured by editing:

ED DOS SYSTEM.CFG

Line 10

=== Configuring fonts and colors for all users ===

Current latest version of NEOSYS software allows choice of font for all columnar reports and documents produced by NEOSYS.

The default for all NEOSYS reports and documents unless you follow this procedure is a dark and light buff yellow.

ED DEFINITIONS SYSTEM

line 46 then press Ctrl+E to edit multivalues (sublines)

mv 1: color for table column heading rows

mv 2: color for table body rows

mv 3: font

Press F9 to save, then Esc to get out of editing multivalues

Users can override the above the colors and fonts in their user details after login.

=== Changing the signatory ===

In Maintenance mode, press F5 and the following command:

ED DEFINITIONS AGENCY.PARAMS

Be careful not to insert lines except at the end. Moving other lines down will totally screw NEOSYS!

Than go to the bottom of the page (Ctrl+Page down). Once you reach at the bottom, ENTER enough times to add additional lines if required, than search for '''line 61''' (Ctrl+G) and edit the document / add this code:

 Name of General Manager General Manager 

=== Clearing files in database (done when you want to clean an old database) ===

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.

Clear data F5 CLEAROP (only clears transactions not reference files)

Clear suppliers F5 CLEARFILE SUPPLIERS

Clear Vehicles F5 CLEARFILE VEHICLES

Flush Index F5 FLUSH.INDEX

Clear all F5 CLEARALL (rather nasty command because clears all reference files as well)

=== Configuring backup procedures ===

There is no proper user interface to control the backup parameters and you must use NEOSYS maintenance mode and press F5 before the following commands.

ONE DATABASE - To control the backup of one database do this:

ED DEFINITIONS BACKUP

ONE INSTALLATION - To control the backup of all databases in one installation:

Any lines in the following override the above and affect all databases.

ED DOS BACKUP.CFG

MULTIPLE INSTALLATIONS - To control the backup of multiple parallel installations.

Any lines in the following override the above and affect all NEOSYS installations in the same folder.

ED DOS ..\..\BACKUP.CFG

What each line does is as follows:

*backup params
*1=date last attempted
**2= not used ... was workstation for backup (blank defaults to server)
*3=min time of day for backup to start (defaults to 02:00)
*4=max time of day for backup to start (defaults to 02:05)
*5=days to do backup 1234567 1=sun NIGHT!!! EG 2AM
*2/3/4/5 could be multivalued in parallel (to be programmed)
*6=tech support email addresse(s) separated by ';'
*7=backup disk letter
*8=mv list of datasets NOT to backup (press ctrl+E) (Not used if any backups defined in Configuration File)
*9=1 disable both backup and shutdown completely
*10=email addresses to send backup.zip to OR replacement for 6 if 6 missing backups@neosys.com is excluded in NET from backup.zip recipients
*11=1=suppress backup but do shutdown (testdata) (Not used if any backups defined in Configuration File)
*12=backup disk for uploads (images) folder if different from 7. Put 0 to suppress backup.
*13=backup media check method: blank is default (weekly rotation) 1=wrong media doesnt fail the backup
*14=email address(es) for all log entries to be sent to (ALL - not just those related to backup)

==== Configuring which days the backup will be done on ====

Line 5 should a list of digits indicating desired days of week 1-7 where 1 is Monday

e.g. 23456 to backup on Mon-Fri night

NB Assuming the backups are at the default time of 2am then you must put "2"
for Monday night since it actually takes place on Tuesday at 2am.

==== Configuring email backup alerts ====

See lines 6 and 10 above

==== Excluding TEST, historical or other databases from backing up every night ====
Database backup is automatically skipped if the last four characters of the database code are TEST or the word TESTING or TRAINING is found in the database name or if the database code is found in the list of database codes (ctrl+e) not to be backed up in line 8 of BACKUP.CFG or if line 11 is set to 1.

==== Backing up the Images folder ====

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 be installed. Incase of old installations, please follow the Cygwin re-installation procedure at [[Setting_up_and_using_remote_support#Upgrading_SSHD_.2F_Cygwin]].

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:

line 12 - and specify the Drive of the location to be backed up to. eg. E or F

=== Configuring automated emails in NEOSYS ===

Login to NEOSYS Maintenance

Press F5

ED DEFINITIONS SMTP.CFG

and press enter (F9/Esc to save and exit)

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS SMTP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations. Available in NEOSYS versions dated 24/4/2007 onwards.

ED DOS ..\..\SMTP.CFG

Lines are fixed (only first two lines are required)

#sender email (must be acceptable to the smtp host name following)
#smtp host name (domain name or ip number)
#smtp port number (blank for 25)
#smtp timeout in seconds (blank for 60?)
#smto use ssl (1=yes, blank for no) ssl is secure connection
#smtp authorization type (1)
#smtp user
#smtp pass

Typical configuration

in DOS SMTP.CFG

clientname@neosys.com
mailout.neosys.com
2500

Note that neosys mail server will accept email from anywhere as long as the sender email is @neosys.com

=== Copying a single record from one database to another ===

You need to know the file name and record key of the record to be copied.

In this case the file is DEFINITIONS and the key is AGENCY.PARAMS

You can invent any old style 8.3 filename instead of C:\AGP.DAT in the following example

On the source computer:

F5
COPY DEFINITIONS AGENCY.PARAMS TO: (DOS C:\AGP.DAT)

On the target computer:

F5
COPY DOS C:\AGP.DAT (ON) TO: (DEFINITIONS AGENCY.PARAMS)

The (O) option is required to force overwrite of the existing

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.

== NEOSYS Authorisation File ==

=== Preventing users from assigning their own passwords ===

The task AUTHORISATION INVENT OWN PASSWORDS should always have the lock NEOSYS to prevent users from creating their own passwords. Most users create unsafe passwords given the choice.

People nearly always ask to give their own passwords but you should tell them that NEOSYS always assigns random passwords for security reasons. It is not worth arguing and discussing the point with most people since they don't usually grasp the importance and soon learn their NEOSYS password anyway.

NEOSYS support staff who login as NEOSYS are still authorised to create their own passwords but it is better not to leak this information to clients immediately since people will grasp on to it and be disappointed or even offended that you are not granting this privilege to them.

Unfortunately there is no general way for people to change their own passwords at the moment. Only the few people who have access to the Support Menu and Authorisation File can do it. Changing your own passwords should be on the NEOSYS Help menu so everybody can do it.

=== Authorising access from outside the LAN ===

From 15/2/2008 access to NEOSYS is by default restricted to users from the standard local area network ip numbers starting 192.168, 10 and 127 so you might get clients complaining that they cannot login.

In order to allow access from outside you will have to update the Authorisation File and put a list of valid ip numbers that they are authorised to login from.

You dont have to put ip numbers on every single user. If the user ip numbers are blank for a user then the system will look for and use the nearest ip numbers on the following users below within the same department. Therefore you only have to put the ip numbers on the bottom "department user".

==== Examples ====

To allow someone to login from a) anywhere in the office and b) from another office with a static ip number of say 80.11.22.33 put something like 192.168.*,10.*,127.*,80.11.22.33

To allow someone to login from anywhere put * This is not recommended but necessary if someone absolutely has to login from anywhere in the world.

== Allowing users temporary login as NEOSYS in maintenance mode ==

#Get them to login with any name even NEOSYS
#Get the to enter "?" for the pass without the quotes
#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
#Follow the NEOSYS lock/key procedure using the full contents of the lock including the user name
(to allow access EXCEPT access to authorisation screen use 132456 as the last number of the initial command)
#Give them the key and get them to enter and proceed

== Giving users access to the Support Menu ==

The Support Menu in NEOSYS enables users to access the following:

# List of Database processes
# List of Documents in use
# Stop/Restart NEOSYS service
# Backup
# Log
# Authorisation file

This menu is locked with the task SUPPORT MENU ACCESS and has the LS key. To give any user/I.T. administrator access to this menu, you have to give him the LS key.

== Configuring payment instruction text ==

NEOSYS picks up the first available payment instructions from the following locations and ignores any instructions in the later files.

#Client file
#Currency file
#Company file
#Configuration File

If, following the normal rules, the payment instructions are "NONE" then the instructions are blank.

There is a manually edited flag in the company file on one NEOSYS client (cannot remember which) which makes the company file payment instructions take precedence over any currency file payment instructions. This may be added to the Client File u/i as "For all currencies"

The usual way of configuring payment instructions is to put it in the Company file under Finance. However this does not allow for different payment instructions per currency. If you put the payment instructions in the currency file however, then these instructions apply to all companies unless you edit the manual flag in the company record to say that the company file instructions take precedence over. There is no way at the moment in NEOSYS to have different instructions per company AND per currency.

Tip: Since the rules of getting payment instructions are not simple, if you are *changing* payment instructions, locate where the old instructions are and simply change them without worrying about the rules.

== Configuring upload of photoshop "cs2" jpg files ==

Photoshop version "cs2" produces jpg files that cannot be viewed in Internet Explorer.

A solution is to rename the files extension from .jpg to .psjpg before uploading.

"psjpg" files are an invention of NEOSYS and IIS must be configured to handle .psjpg files as follows:

Windows Server 2003 (doesnt work on XP)

#Computer Management, Internet Information Server, Properties
#Click MIME Types
#Click New
#Extension: psjpg
#MIME Type: application/photoshop
#Click OK,OK,OK
#Restart IIS (Right click, All Tasks, Restart)

Installing NEOSYS

2008-02-24T16:19:05Z

77.68.3.139:

[[Installing NEOSYS Service]]

[[Configuring Antivirus for NEOSYS]]

[[Benchmarking NEOSYS]]

[[Setting up HTTPS]]

[[Setting up TCP/IP filtering]]

[[Setting up remote backup]]

[[Setting up monitoring]]

[[Setting up Dynsite / Dynamic IP update client]]

[[Installing IE7 Download Blocker]]

[[Establishing Emergency Support Procedures]]

[[Technical / Hardware requirements]]

Configuring NEOSYS Generally

2008-02-05T13:10:29Z

77.68.3.139: /* Configuring backup procedures */

=== Configuring letterhead ===
[[Configuring Letterhead]]

=== Configuring Client Security mark ===
All client installations are hardcoded with the name of the NEOSYS client allowed to use the software. This client mark is generated by the programmer and given to Technical Staff during installation and is a mandatory feature and cannot be removed. This Client security mark is printed on all documents generated out of NEOSYS and appears as below:

[[Image:clientsecuritymark.jpg]]

This can be changed incase the client's legal name changes.

The client security mark is configured by editing:

ED DEFINITIONS AGENCY.PARAMS

Line 1

This client mark can be displayed as an email hyperlink for all the reports generated (such as Media Diary, List of Ads Pending Booking, List of Invoices etc.) and this hyperlink can be configured by editing:

ED DOS SYSTEM.CFG

Line 10

=== Configuring fonts and colors for all users ===

Current latest version of NEOSYS software allows choice of font for all columnar reports and documents produced by NEOSYS.

The default for all NEOSYS reports and documents unless you follow this procedure is a dark and light buff yellow.

ED DEFINITIONS SYSTEM

line 46 then press Ctrl+E to edit multivalues (sublines)

mv 1: color for table column heading rows

mv 2: color for table body rows

mv 3: font

Press F9 to save, then Esc to get out of editing multivalues

Users can override the above the colors and fonts in their user details after login.

=== Changing the signatory ===

In Maintenance mode, press F5 and the following command:

ED DEFINITIONS AGENCY.PARAMS

Be careful not to insert lines except at the end. Moving other lines down will totally screw NEOSYS!

Than go to the bottom of the page (Ctrl+Page down). Once you reach at the bottom, ENTER enough times to add additional lines if required, than search for '''line 61''' (Ctrl+G) and edit the document / add this code:

 Name of General Manager General Manager 

=== Clearing files in database (done when you want to clean an old database) ===

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.

Clear data F5 CLEAROP (only clears transactions not reference files)

Clear suppliers F5 CLEARFILE SUPPLIERS

Clear Vehicles F5 CLEARFILE VEHICLES

Flush Index F5 FLUSH.INDEX

Clear all F5 CLEARALL (rather nasty command because clears all reference files as well)

=== Configuring backup procedures ===

There is no proper user interface to control the backup parameters and you must use NEOSYS maintenance mode and press F5 before the following commands.

ONE DATABASE - To control the backup of one database do this:

ED DEFINITIONS BACKUP

ONE INSTALLATION - To control the backup of all databases in one installation:

Any lines in the following override the above and affect all databases.

ED DOS BACKUP.CFG

MULTIPLE INSTALLATIONS - To control the backup of multiple parallel installations.

Any lines in the following override the above and affect all NEOSYS installations in the same folder.

ED DOS ..\..\BACKUP.CFG

What each line does is as follows:

*backup params
*1=date last attempted
**2= not used ... was workstation for backup (blank defaults to server)
*3=min time of day for backup to start (defaults to 02:00)
*4=max time of day for backup to start (defaults to 02:05)
*5=days to do backup 1234567 1=sun NIGHT!!! EG 2AM
*2/3/4/5 could be multivalued in parallel (to be programmed)
*6=tech support email addresse(s) separated by ';'
*7=backup disk letter
*8=mv list of datasets NOT to backup (press ctrl+E)
*9=1 disable both backup and shutdown completely
*10=email addresses to send backup.zip to OR replacement for 6 if 6 missing backups@neosys.com is excluded in NET from backup.zip recipients
*11=1=suppress backup but do shutdown (testdata)
*12=backup disk for uploads (images) folder if different from 7. Put 0 to suppress backup.
*13=backup media check method: blank is default (weekly rotation) 1=wrong media doesnt fail the backup
*14=email address(es) for all log entries to be sent to (ALL - not just those related to backup)

==== Configuring which days the backup will be done on ====

Line 5 should a list of digits indicating desired days of week 1-7 where 1 is Monday

e.g. 23456 to backup on Mon-Fri night

NB Assuming the backups are at the default time of 2am then you must put "2"
for Monday night since it actually takes place on Tuesday at 2am.

==== Configuring email backup alerts ====

See lines 6 and 10 above

==== Excluding TEST, historical or other databases from backing up every night ====
Database backup is automatically skipped if the last four characters of the database code are TEST or the word TESTING or TRAINING is found in the database name or if the database code is found in the list of database codes (ctrl+e) not to be backed up in line 8 of BACKUP.CFG or if line 11 is set to 1.

==== Backing up the Images folder ====

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 be installed. Incase of old installations, please follow the Cygwin re-installation procedure at [[Setting_up_and_using_remote_support#Upgrading_SSHD_.2F_Cygwin]].

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:

line 12 - and specify the Drive of the location to be backed up to. eg. E or F

=== Configuring automated emails in NEOSYS ===

Login to NEOSYS Maintenance

Press F5

ED DEFINITIONS SMTP.CFG

and press enter (F9/Esc to save and exit)

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS SMTP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations. Available in NEOSYS versions dated 24/4/2007 onwards.

ED DOS ..\..\SMTP.CFG

Lines are fixed (only first two lines are required)

#sender email (must be acceptable to the smtp host name following)
#smtp host name (domain name or ip number)
#smtp port number (blank for 25)
#smtp timeout in seconds (blank for 60?)
#smto use ssl (1=yes, blank for no) ssl is secure connection
#smtp authorization type (1)
#smtp user
#smtp pass

Typical configuration

in DOS SMTP.CFG

clientname@neosys.com
mailout.neosys.com
2500

Note that neosys mail server will accept email from anywhere as long as the sender email is @neosys.com

=== Copying a single record from one database to another ===

You need to know the file name and record key of the record to be copied.

In this case the file is DEFINITIONS and the key is AGENCY.PARAMS

You can invent any old style 8.3 filename instead of C:\AGP.DAT in the following example

On the source computer:

F5
COPY DEFINITIONS AGENCY.PARAMS TO: (DOS C:\AGP.DAT)

On the target computer:

F5
COPY DOS C:\AGP.DAT (ON) TO: (DEFINITIONS AGENCY.PARAMS)

The (O) option is required to force overwrite of the existing

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.

== NEOSYS Authorisation File ==

=== Preventing users from assigning their own passwords ===

The task AUTHORISATION INVENT OWN PASSWORDS should always have the lock NEOSYS to prevent users from creating their own passwords. Most users create unsafe passwords given the choice.

People nearly always ask to give their own passwords but you should tell them that NEOSYS always assigns random passwords for security reasons. It is not worth arguing and discussing the point with most people since they don't usually grasp the importance and soon learn their NEOSYS password anyway.

NEOSYS support staff who login as NEOSYS are still authorised to create their own passwords but it is better not to leak this information to clients immediately since people will grasp on to it and be disappointed or even offended that you are not granting this privilege to them.

Unfortunately there is no general way for people to change their own passwords at the moment. Only the few people who have access to the Support Menu and Authorisation File can do it. Changing your own passwords should be on the NEOSYS Help menu so everybody can do it.

== Allowing users temporary login as NEOSYS in maintenance mode ==

#Get them to login with any name even NEOSYS
#Get the to enter "?" for the pass without the quotes
#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
#Follow the NEOSYS lock/key procedure using the full contents of the lock including the user name
(to allow access EXCEPT access to authorisation screen use 132456 as the last number of the initial command)
#Give them the key and get them to enter and proceed

== Giving users access to the Support Menu ==

The Support Menu in NEOSYS enables users to access the following:

# List of Database processes
# List of Documents in use
# Stop/Restart NEOSYS service
# Backup
# Log
# Authorisation file

This menu is locked with the task SUPPORT MENU ACCESS and has the LS key. To give any user/I.T. administrator access to this menu, you have to give him the LS key.

== Configuring payment instruction text ==

NEOSYS picks up the first available payment instructions from the following locations and ignores any instructions in the later files.

#Client file
#Currency file
#Company file
#Configuration File

If, following the normal rules, the payment instructions are "NONE" then the instructions are blank.

There is a manually edited flag in the company file on one NEOSYS client (cannot remember which) which makes the company file payment instructions take precedence over any currency file payment instructions. This may be added to the Client File u/i as "For all currencies"

The usual way of configuring payment instructions is to put it in the Company file under Finance. However this does not allow for different payment instructions per currency. If you put the payment instructions in the currency file however, then these instructions apply to all companies unless you edit the manual flag in the company record to say that the company file instructions take precedence over. There is no way at the moment in NEOSYS to have different instructions per company AND per currency.

Tip: Since the rules of getting payment instructions are not simple, if you are *changing* payment instructions, locate where the old instructions are and simply change them without worrying about the rules.

== Configuring upload of photoshop "cs2" jpg files ==

Photoshop version "cs2" produces jpg files that cannot be viewed in Internet Explorer.

A solution is to rename the files extension from .jpg to .psjpg before uploading.

"psjpg" files are an invention of NEOSYS and IIS must be configured to handle .psjpg files as follows:

Windows Server 2003 (doesnt work on XP)

#Computer Management, Internet Information Server, Properties
#Click MIME Types
#Click New
#Extension: psjpg
#MIME Type: application/photoshop
#Click OK,OK,OK
#Restart IIS (Right click, All Tasks, Restart)

Configuring NEOSYS Generally

2008-01-18T08:17:44Z

77.68.3.139: /* Configuring backup procedures */

=== Configuring letterhead ===
[[Configuring Letterhead]]

=== Configuring Client Security mark ===
All client installations are hardcoded with the name of the NEOSYS client allowed to use the software. This client mark is generated by the programmer and given to Technical Staff during installation and is a mandatory feature and cannot be removed. This Client security mark is printed on all documents generated out of NEOSYS and appears as below:

[[Image:clientsecuritymark.jpg]]

This can be changed incase the client's legal name changes.

The client security mark is configured by editing:

ED DEFINITIONS AGENCY.PARAMS

Line 1

This client mark can be displayed as an email hyperlink for all the reports generated (such as Media Diary, List of Ads Pending Booking, List of Invoices etc.) and this hyperlink can be configured by editing:

ED DOS SYSTEM.CFG

Line 10

=== Configuring fonts and colors for all users ===

Current latest version of NEOSYS software allows choice of font for all columnar reports and documents produced by NEOSYS.

The default for all NEOSYS reports and documents unless you follow this procedure is a dark and light buff yellow.

ED DEFINITIONS SYSTEM

line 46 then press Ctrl+E to edit multivalues (sublines)

mv 1: color for table column heading rows

mv 2: color for table body rows

mv 3: font

Press F9 to save, then Esc to get out of editing multivalues

Users can override the above the colors and fonts in their user details after login.

=== Changing the signatory ===

In Maintenance mode, press F5 and the following command:

ED DEFINITIONS AGENCY.PARAMS

Be careful not to insert lines except at the end. Moving other lines down will totally screw NEOSYS!

Than go to the bottom of the page (Ctrl+Page down). Once you reach at the bottom, ENTER enough times to add additional lines if required, than search for '''line 61''' (Ctrl+G) and edit the document / add this code:

 Name of General Manager General Manager 

=== Clearing files in database (done when you want to clean an old database) ===

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.

Clear data F5 CLEAROP (only clears transactions not reference files)

Clear suppliers F5 CLEARFILE SUPPLIERS

Clear Vehicles F5 CLEARFILE VEHICLES

Flush Index F5 FLUSH.INDEX

Clear all F5 CLEARALL (rather nasty command because clears all reference files as well)

=== Configuring backup procedures ===

There is no proper user interface to control the backup parameters and you must use NEOSYS maintenance mode and press F5 before the following commands.

ONE DATABASE - To control the backup of one database do this:

ED DEFINITIONS BACKUP

ONE INSTALLATION - To control the backup of all databases in one installation:

Any lines in the following override the above and affect all databases.

ED DOS BACKUP.CFG

MULTIPLE INSTALLATIONS - To control the backup of multiple parallel installations.

Any lines in the following override the above and affect all NEOSYS installations in the same folder.

ED DOS ..\..\BACKUP.CFG

What each line does is as follows:

*backup params
*1=date last attempted
**2= not used ... was workstation for backup (blank defaults to server)
*3=min time of day for backup to start (defaults to 02:00)
*4=max time of day for backup to start (defaults to 02:05)
*5=days to do backup 1234567 1=sun NIGHT!!! EG 2AM
*2/3/4/5 could be multivalued in parallel (to be programmed)
*6=tech support email addresse(s) separated by ';'
*7=backup disk letter
*8=mv list of datasets NOT to backup (press ctrl+E)
*9=1 disable both backup and shutdown completely
*10=email addresses to send backup.zip to OR replacement for 6 if 6 missing backups@neosys.com is excluded in NET from backup.zip recipients
*11=1=suppress backup but do shutdown (testdata)
*12=backup disk for uploads (images) folder if different from 7. Put 0 to suppress backup.
*13=backup media check method: blank is default (weekly rotation) 1=wrong media doesnt fail the backup

==== Configuring which days the backup will be done on ====

Line 5 should a list of digits indicating desired days of week 1-7 where 1 is Monday

e.g. 23456 to backup on Mon-Fri night

NB Assuming the backups are at the default time of 2am then you must put "2"
for Monday night since it actually takes place on Tuesday at 2am.

==== Configuring email backup alerts ====

See lines 6 and 10 above

==== Excluding TEST, historical or other databases from backing up every night ====
Database backup is automatically skipped if the last four characters of the database code are TEST or the word TESTING or TRAINING is found in the database name or if the database code is found in the list of database codes (ctrl+e) not to be backed up in line 8 of BACKUP.CFG or if line 11 is set to 1.

==== Backing up the Images folder ====

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 be installed. Incase of old installations, please follow the Cygwin re-installation procedure at [[Setting_up_and_using_remote_support#Upgrading_SSHD_.2F_Cygwin]].

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:

line 12 - and specify the Drive of the location to be backed up to. eg. E or F

=== Configuring automated emails in NEOSYS ===

Login to NEOSYS Maintenance

Press F5

ED DEFINITIONS SMTP.CFG

and press enter (F9/Esc to save and exit)

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS SMTP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations. Available in NEOSYS versions dated 24/4/2007 onwards.

ED DOS ..\..\SMTP.CFG

Lines are fixed (only first two lines are required)

#sender email (must be acceptable to the smtp host name following)
#smtp host name (domain name or ip number)
#smtp port number (blank for 25)
#smtp timeout in seconds (blank for 60?)
#smto use ssl (1=yes, blank for no) ssl is secure connection
#smtp authorization type (1)
#smtp user
#smtp pass

Typical configuration

in DOS SMTP.CFG

clientname@neosys.com
mailout.neosys.com
2500

Note that neosys mail server will accept email from anywhere as long as the sender email is @neosys.com

=== Copying a single record from one database to another ===

You need to know the file name and record key of the record to be copied.

In this case the file is DEFINITIONS and the key is AGENCY.PARAMS

You can invent any old style 8.3 filename instead of C:\AGP.DAT in the following example

On the source computer:

F5
COPY DEFINITIONS AGENCY.PARAMS TO: (DOS C:\AGP.DAT)

On the target computer:

F5
COPY DOS C:\AGP.DAT (ON) TO: (DEFINITIONS AGENCY.PARAMS)

The (O) option is required to force overwrite of the existing

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.

== NEOSYS Authorisation File ==

=== Preventing users from assigning their own passwords ===

The task AUTHORISATION INVENT OWN PASSWORDS should always have the lock NEOSYS to prevent users from creating their own passwords. Most users create unsafe passwords given the choice.

People nearly always ask to give their own passwords but you should tell them that NEOSYS always assigns random passwords for security reasons. It is not worth arguing and discussing the point with most people since they don't usually grasp the importance and soon learn their NEOSYS password anyway.

NEOSYS support staff who login as NEOSYS are still authorised to create their own passwords but it is better not to leak this information to clients immediately since people will grasp on to it and be disappointed or even offended that you are not granting this privilege to them.

Unfortunately there is no general way for people to change their own passwords at the moment. Only the few people who have access to the Support Menu and Authorisation File can do it. Changing your own passwords should be on the NEOSYS Help menu so everybody can do it.

== Allowing users temporary login as NEOSYS in maintenance mode ==

#Get them to login with any name even NEOSYS
#Get the to enter "?" for the pass without the quotes
#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
#Follow the NEOSYS lock/key procedure using the full contents of the lock including the user name
(to allow access EXCEPT access to authorisation screen use 132456 as the last number of the initial command)
#Give them the key and get them to enter and proceed

== Giving users access to the Support Menu ==

The Support Menu in NEOSYS enables users to access the following:

# List of Database processes
# List of Documents in use
# Stop/Restart NEOSYS service
# Backup
# Log
# Authorisation file

This menu is locked with the task SUPPORT MENU ACCESS and has the LS key. To give any user/I.T. administrator access to this menu, you have to give him the LS key.

== Configuring payment instruction text ==

NEOSYS picks up the first available payment instructions from the following locations and ignores any instructions in the later files.

#Client file
#Currency file
#Company file
#Configuration File

If, following the normal rules, the payment instructions are "NONE" then the instructions are blank.

There is a manually edited flag in the company file on one NEOSYS client (cannot remember which) which makes the company file payment instructions take precedence over any currency file payment instructions. This may be added to the Client File u/i as "For all currencies"

The usual way of configuring payment instructions is to put it in the Company file under Finance. However this does not allow for different payment instructions per currency. If you put the payment instructions in the currency file however, then these instructions apply to all companies unless you edit the manual flag in the company record to say that the company file instructions take precedence over. There is no way at the moment in NEOSYS to have different instructions per company AND per currency.

Tip: Since the rules of getting payment instructions are not simple, if you are *changing* payment instructions, locate where the old instructions are and simply change them without worrying about the rules.

== Configuring upload of photoshop "cs2" jpg files ==

Photoshop version "cs2" produces jpg files that cannot be viewed in Internet Explorer.

A solution is to rename the files extension from .jpg to .psjpg before uploading.

"psjpg" files are an invention of NEOSYS and IIS must be configured to handle .psjpg files as follows:

Windows Server 2003 (doesnt work on XP)

#Computer Management, Internet Information Server, Properties
#Click MIME Types
#Click New
#Extension: psjpg
#MIME Type: application/photoshop
#Click OK,OK,OK
#Restart IIS (Right click, All Tasks, Restart)

Troubleshooting NEOSYS Generally

2008-01-16T05:11:44Z

77.68.3.139: /* Searching for word/number in the database files using maintenance mode */

=== Document Remains Locked longer than 10 minutes after an Internet Explorer Window crashes ===

Lost/hidden internet explorer window on windows that cannot be accessed keeps document locked until process killed/windows restarted

==== Symptoms ====

#Internet Explorer Windows "disappears" while working on a document.
#Attempts to reopen the same document (even after the normal NEOSYS ten minute lock timeout) results in a message something like "Cannot be edited because the document is in use by (username)"
#NEOSYS Support Menu, List of Open Documents shows that the record lock is being actively refreshed every five minutes as per normal NEOSYS process
#The iexplorer task can be seen in task managers, list of processes even after closing all Internet Explorer window.

==== Cause ====

Almost certainly due to windows unreliability when PC is customised with additional software from internet etc.

==== Work around ====

Kill the iexplorer task in Task Manager's list of processes or reboot the workstation and wait for up to 10 minutes for the lock to be cleared.

==== Permanent Solution ====

#Remove Internet Explorer Add-ons
#Reinstall Internet Explorer
#Reinstall Windows

=== Handling damaged files ===

[[Handling damaged files]]

=== Checking for corrupt database files ===

Login to NEOSYS Maintenance

Press F5

CHK.FILES

or

CHK.FILES filename

=== Assessing Database Size per File ===

In NEOSYS maintenance mode

LIST FILES BY BY-DSND SIZE VOLUME.NAME SIZE

This will include all files not just those in the actual dataset in DATA\* folders.

=== Troubleshooting Internet Explorer ===

[[Troubleshooting IE]]

=== Resolving slow speed ===

[[Benchmarking NEOSYS]]

=== Handling failure and warning on nightly backup alerts ===

[[Handling failure and warning messages on nightly backup alerts]]

== Resolving permissions errors while logging in ==

=== Problem ===

While logging in, you get the following error message:
[[Image:login_error_message.jpg]]

=== Solution ===

Add the internet guest account to the security list of the data folder with the default permission of list/read/write

Make sure the read&execute permission is removed
[[Image:permissions_on_data.jpg]]

== Resolving the 'HTTP Error 500.0 - Internal Server Error' while logging in on IE on a Windows Vista system ==

=== Problem ===
After configuring IIS on Windows Vista you will get this error message while trying to login into NEOSYS from Internet Explorer:

HTTP Error 500.0 - Internal Server Error
Description: This application is running in an application pool that uses the Integrated .NET
mode. This is the preferred mode for running ASP.NET applications on the current and future
version of IIS.

In this mode, the application using client impersonation configured with <identity
impersonate="true" /> may not behave correctly. Client impersonation is not available in early
ASP.NET request processing stages and may lead modules in those stages to execute with process
identity instead.

=== Solution ===

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)

%systemroot%\system32\inetsrv\APPCMD.EXE set app "Default Web Site/neosys" /applicationPool:"Classic .NET AppPool"

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.

== Resolving the 'Class Not Registered' error message while logging in ==

=== Problem ===
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.

Anyway, you will get the proper message in the event log:

Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 36
Description: The server failed to load application '/LM/W3SVC/1/ROOT/NEOSYS.
The error was 'Class not registered'.

=== Solution ===
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):

To resolve this problem, reinstall Component Services as follows: WARNING:
# Open registry editor, locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3, and then delete this key.
# From the Start menu, point to Settings, click Control Panel, and then click Add/Remove Programs.
# Click Add/Remove Windows Components.
# Proceed through the wizard, and accept all of the defaults (including IIS)
# Restart the computer.

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

# Delete IIS related package in Component Services MMC
# IIS In-Process Applications
# IIS Out-of-Process Pooled Applications
# IIS Utilities

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.

Launch command prompt and run the following command.
# msdtc -install
# net start msdtc

Then try re-install IIS.

This should solve the problem

== Enabling File Security option on Win XP Professional ==

=== Problem ===

In the Properties of any folders, the Security option does not show, hence you cannot modify the Read, Write options.

=== Solution ===

The solution would be to untick the 'Simple File Sharing' option from Tools > Folder Options > View:
[[Image:simplefilesharingoff.jpg]]

== B10 & B12 Errors ==

These errors are in the software and should be immediately escalated to the programmer.

== Internet Explorer Menu, View, Text Size doesnt change font size as expected ==

Cause: This is because the font size is now user definable in NEOSYS and View, Text Size does not override predefined font sizes.

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.

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.

== Error on process window "Not enough string space - Out of Memory" ==

=== Message ===

‘RTP27’ Line 1. [B29] Not enough string space – Out of Memory.

Not enough memory to execute Debugger; current program aborted.
Press any key to continue

[[Image:out_of_memory.jpg]]

=== Cause ===
Unknown perhaps related to some large document or report

=== Solution ===
Ask users for any hanging transactions.
None other than closing and starting another process

== Uploaded jpg files fail to display in internet explorer ==

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.

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.

=== Partial solution ===
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.

== "You have attempted to write to a read-only file" ==

=== Message ===

Error while writing data.
You have attempted to write to a read-only file.
- or -
access to the file has been denied by the operating system.
(operating system file name: "..\DATA\ADLINEC\ADAGENCY\REV76467.OV00012618")

=== Cause ===

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.

=== Short Term Solution ===

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
FIXFILE or restoring databases.

=== Long Term Solution ===

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.

== Resolving "Cannot backup/restore because PROCESS1 PROCESS2 (etc) is/are online" message ==

This can happen for a variety of reasons if all the NEOSYS processes fail to close down at backup time

# NEOSYS maintenance windows are left open.
# NEOSYS processes hang due to software error.

== How to kill hung NEOSYS processes ==

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.

==== If NEOSYS processes are visible on the server desktop ====

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.

You can then click the X to kill the process and confirm that this is OK.

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.

[[Image:hungprocess.jpg]]

==== If NEOSYS processes are not visible on the server desktop ====

You can check if there are any hung processes from the NEOSYS Support Menu, List of Database Processes.
[[Image:databaseprocesseslist.jpg]]

#Shutdown NEOSYS by TEMPORARILY putting a file called GLOBAL.END in the parent directory of neosys. 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.
#Use Windows Task Manager to kill all the NTVDM tasks. Don't kill active NEOSYS processes.

[[Image:taskmanager.jpg]]

=== Temporary workarounds for hung NEOSYS processes ===

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.

== How to fix a NEOSYS process which opens up in a notepad instead of Microsoft Windows Based Script Host (i.e. DOS window)==

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:

# Download and install the Windows Script 5.6/5.7 from the Microsoft Website
# 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)

== Resolving a 'Could not start' error on Scheduled Tasks in Windows Server 2000 SP4 ==

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.

Hence the Scheduled Tasks do not work sometimes. However the Scheduled Tasks works fine sometimes, but when you uninstall SP4, it does not work.

The best solution is to:

# Incase Scheduled Tasks do not work after installing SP4, then uninstall SP4 and it should be fine.
# Incase Scheduled Tasks works after installing SP4, and later after uninstalling SP4, it does not work, then install SP4 and it should be fine.

=== Checking for server or NEOSYS crashes ===

#NEOSYS Maintenance Mode
#General Menu, Setup, Processes
#Select the dates and the option Detailed

This report shows a list of dates and times that NEOSYS logged in but did not log out properly.

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.

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.

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.

Isolated one-off failures will be related to individual NEOSYS process crashes - most commonly caused by one of the following:

#NEOSYS hanging to due to software failure
#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
#Random server failures eg memory, disk etc

Example:

LOGIN 22/12/2007 06:02 NEOSYS SERVER ADAGENCY Current workstation
LOGIN 23/12/2007 06:00 NEOSYS SERVER ADAGENCY Current workstation
LOGIN 23/12/2007 06:01 NEOSYS SERVER ADAGENCY Current workstation
LOGIN 23/12/2007 06:02 NEOSYS SERVER ADAGENCY Current workstation
LOGIN 23/12/2007 08:52 NEOSYS SERVER ADAGENCY Current workstation
LOGIN 23/12/2007 08:52 NEOSYS SERVER ADAGENCY Current workstation
LOGIN 23/12/2007 08:53 NEOSYS SERVER ADAGENCY Current workstation
LOGIN 8/1/2008 06:00 NEOSYS SERVER ADAGENCY Current workstation
LOGIN 8/1/2008 06:01 NEOSYS SERVER ADAGENCY Current workstation
LOGIN 8/1/2008 06:02 NEOSYS SERVER ADAGENCY Current workstation
LOGIN 8/1/2008 13:51 NEOSYS SERVER NEOSYS Current user session

Interpretation:

The first four entries indicate that all four NEOSYS processes started at 06am were suddenly killed probably by power failure

The next four entries indicate that NEOSYS was restarted at around 08:52 and all these processes were AGAIN killed probably by power failure

The last four entries can be ignored because there were four NEOSYS processes running at the time that the report was generated

=== Searching for word/number in the database files using maintenance mode ===

You can search for any word/number in the database files of NEOSYS, using the following command line:

F5
FIND FILENAME WORDWITHOUTANYSPACES

For eg:
FIND CURRENCIES 1.1
(here you are searching for the number 1.1 in the currencies file) You CANNOT search for a phrase ie include spaces like this.

Or you can also type:
FIND FILENAME <enter>
and it will ask you what you want do to search. You can enter an exact phrase with spaces.

Incase you do not know the filenames, you can enter the following command to see all the filenames in the system:

F5
LF

Setting up HTTPS

2008-01-09T16:34:26Z

77.68.3.139: /* Install ssl/https on the site. */

== Creating a single HTTPS web site ==

=== Creating a site in IIS ===

In order to run on the same port number, IIS sites need either unique ip numbers (set in tcp/http *and* ssh/https settings) or different host header values.

Therefore either the ip number has to be one of the available ones provided to neosys by leaseweb etc. or the host header value must be set to '''clientname'''.hosts.neosys.com.

The port number for tcp/http should be the neosys standard arbitrary port of 8123, not port 80 in order to prevent access via standard http. We could use various almost arbitrary ports for http since they are going to blocked by tcp/ip filtering or a firewall but it is better to know that port 8123 is the only one since IIS insists on having some port open for http.

The https options are only available after running selfssl (see below) at least once on the server.

[[Image:httpadvancedwebsitesetup.png]]

=== Install ssl/https on the site. ===

install selfssl.exe from Microsoft site (iis60rkt.exe available in neosys nl1 download folder) only the ssl utility is needed.

http://www.microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&displaylang=en

then

[[Image:SelfSSL.png]]

C:\Program Files\IIS Resources\SelfSSL>selfssl /v:9999 /s:'''''866651215''''' /p:4430 /n:CN='''''clientname'''''.hosts.neosys.com
Microsoft (R) SelfSSL Version 1.0
Copyright (C) 2003 Microsoft Corporation. All rights reserved.
Do you want to replace the SSL settings for site 866651215 (Y/N)?y
The self signed certificate was successfully assigned to site 866651215.

/v:9999 means valid for 9999 days
/s:'''''866651215''''' is the site number in this case (site number is shown in IIS management screen)
/p:4430 is the non-standard port number neosys uses by convention for ssl/https instead of the standard 443
/n:CN='''''clientname'''''.hosts.neosys.com indicates the full domain name of the site

=== Testing access to the new https web site. ===

Make a subdomain '''clientname'''.hosts.neosys.com

https://'''clientname'''.hosts.neosys.com:4430/neosys

If you get certificate error:

#check that the selfsll /n:CN='''clientname'''.hosts.neosys.com matches the domain name used in IE
#install the certificate into the client computer (double click the padlock, view certificates etc)

closing all internet explorer versions and restarting is necessary for installed certificates to become effective.

== Creating multiple HTTPS web sites ==

=== Bugs ===

SelfSSL allows only one website to have SSL at a time

IIS Diagnostics Toolkit which has fixed SelfSSL but doesnt allow full control
http://www.microsoft.com/windowsserver2003/iis/diagnostictools/default.mspx

=== Solution ===

Use selfssl as follows:

#create certificate for a site in selfssl following the normal procedure
#export the certificate to a pfx file (IIS->Site->directory security->server certificate wizard)
#remove the certificate (IIS->Site->directory security->server certificate wizard)
#import pfx certificate back (IIS->Site->directory security->server certificate wizard)

Continue adding sites this way and they should work perfectly fine. Just follow the sequence here for each site being added.

=== Re-installing Certificates ===

Sometimes due to an unknown issue, site/s stop working and hence there is a need to re-install the site certificate. The following procedure to be followed (actually we follow the same procedure as install, but step 1 is to delete the existing certificate):

==== Re-installing Certificates from selfssl ====

#Delete the existing certificate (IIS->directory security->server certificate wizard)
#create certificate for site in SELFSSL
#export the certificate to a pfx file (IIS->directory security->server certificate wizard)
#remove certificate from site (IIS->directory security->server certificate wizard)
#import pfx from step 3 using same wizard
#Done

==== Re-installing Certificates from saved PFX files ====

#Delete the existing certificate (IIS->Site->directory security->server certificate wizard)
#import pfx certificate (IIS->Site->directory security->server certificate wizard)
#Done

Setting up HTTPS

2008-01-09T13:30:00Z

77.68.3.139: /* Install ssl/https on the site. */

== Creating a single HTTPS web site ==

=== Creating a site in IIS ===

In order to run on the same port number, IIS sites need either unique ip numbers (set in tcp/http *and* ssh/https settings) or different host header values.

Therefore either the ip number has to be one of the available ones provided to neosys by leaseweb etc. or the host header value must be set to '''clientname'''.hosts.neosys.com.

The port number for tcp/http should be the neosys standard arbitrary port of 8123, not port 80 in order to prevent access via standard http. We could use various almost arbitrary ports for http since they are going to blocked by tcp/ip filtering or a firewall but it is better to know that port 8123 is the only one since IIS insists on having some port open for http.

The https options are only available after running selfssl (see below) at least once on the server.

[[Image:httpadvancedwebsitesetup.png]]

=== Install ssl/https on the site. ===

install selfssl.exe from Microsoft site (iis60rkt.exe available in neosys nl1 download folder) only the ssl utility is needed.

http://www.microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&displaylang=en

then

[[Image:SelfSSL.png]]

C:\Program Files\IIS Resources\SelfSSL>selfssl /v:9999 /s:'''''866651215''''' /p:4430 /n:CN='''''clientname'''''.hosts.neosys.com
Microsoft (R) SelfSSL Version 1.0
Copyright (C) 2003 Microsoft Corporation. All rights reserved.
Do you want to replace the SSL settings for site 866651215 (Y/N)?y
The self signed certificate was successfully assigned to site 866651215.

/v:9999 means valid for 9999 days
/s:'''''866651215''''' is the site number in this case (site number is shown in IIS management screen)
/p:4430 is the non-standard port number neosys uses by convention for ssl/https instead of the standard 443
/n:CN='''''clientname'''''.hosts.neosys.com indicates the full domain name of the site

=== Testing access to the new https web site. ===

Make a subdomain '''clientname'''.hosts.neosys.com

https://'''clientname'''.hosts.neosys.com:4430/neosys

If you get certificate error:

#check that the selfsll /n:CN='''clientname'''.hosts.neosys.com matches the domain name used in IE
#install the certificate into the client computer (double click the padlock, view certificates etc)

closing all internet explorer versions and restarting is necessary for installed certificates to become effective.

== Creating multiple HTTPS web sites ==

=== Bugs ===

SelfSSL allows only one website to have SSL at a time

IIS Diagnostics Toolkit which has fixed SelfSSL but doesnt allow full control
http://www.microsoft.com/windowsserver2003/iis/diagnostictools/default.mspx

=== Solution ===

Use selfssl as follows:

#create certificate for a site in selfssl following the normal procedure
#export the certificate to a pfx file (IIS->Site->directory security->server certificate wizard)
#remove the certificate (IIS->Site->directory security->server certificate wizard)
#import pfx certificate back (IIS->Site->directory security->server certificate wizard)

Continue adding sites this way and they should work perfectly fine. Just follow the sequence here for each site being added.

=== Re-installing Certificates ===

Sometimes due to an unknown issue, site/s stop working and hence there is a need to re-install the site certificate. The following procedure to be followed (actually we follow the same procedure as install, but step 1 is to delete the existing certificate):

==== Re-installing Certificates from selfssl ====

#Delete the existing certificate (IIS->directory security->server certificate wizard)
#create certificate for site in SELFSSL
#export the certificate to a pfx file (IIS->directory security->server certificate wizard)
#remove certificate from site (IIS->directory security->server certificate wizard)
#import pfx from step 3 using same wizard
#Done

==== Re-installing Certificates from saved PFX files ====

#Delete the existing certificate (IIS->Site->directory security->server certificate wizard)
#import pfx certificate (IIS->Site->directory security->server certificate wizard)
#Done

Configuring NEOSYS Generally

2007-12-27T17:59:47Z

77.68.3.139: /* Configuring backup procedures */

=== Configuring letterhead ===
[[Configuring Letterhead]]

=== Configuring Client Security mark ===
All client installations are hardcoded with the name of the NEOSYS client allowed to use the software. This client mark is generated by the programmer and given to Technical Staff during installation and is a mandatory feature and cannot be removed. This Client security mark is printed on all documents generated out of NEOSYS and appears as below:

[[Image:clientsecuritymark.jpg]]

This can be changed incase the client's legal name changes.

The client security mark is configured by editing:

ED DEFINITIONS AGENCY.PARAMS

Line 1

This client mark can be displayed as an email hyperlink for all the reports generated (such as Media Diary, List of Ads Pending Booking, List of Invoices etc.) and this hyperlink can be configured by editing:

ED DOS SYSTEM.CFG

Line 10

=== Configuring fonts and colors for all users ===

Current latest version of NEOSYS software allows choice of font for all columnar reports and documents produced by NEOSYS.

The default for all NEOSYS reports and documents unless you follow this procedure is a dark and light buff yellow.

ED DEFINITIONS SYSTEM

line 46 then press Ctrl+E to edit multivalues (sublines)

mv 1: color for table column heading rows

mv 2: color for table body rows

mv 3: font

Press F9 to save, then Esc to get out of editing multivalues

Users can override the above the colors and fonts in their user details after login.

=== Changing the signatory ===

In Maintenance mode, press F5 and the following command:

ED DEFINITIONS AGENCY.PARAMS

Be careful not to insert lines except at the end. Moving other lines down will totally screw NEOSYS!

Than go to the bottom of the page (Ctrl+Page down). Once you reach at the bottom, ENTER enough times to add additional lines if required, than search for '''line 61''' (Ctrl+G) and edit the document / add this code:

 Name of General Manager General Manager 

=== Clearing files in database (done when you want to clean an old database) ===

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.

Clear data F5 CLEAROP (only clears transactions not reference files)

Clear suppliers F5 CLEARFILE SUPPLIERS

Clear Vehicles F5 CLEARFILE VEHICLES

Flush Index F5 FLUSH.INDEX

Clear all F5 CLEARALL (rather nasty command because clears all reference files as well)

=== Configuring backup procedures ===

There is no proper user interface to control the backup parameters and you must use NEOSYS maintenance mode and press F5 before the following commands.

ONE DATABASE - To control the backup of one database do this:

ED DEFINITIONS BACKUP

ONE INSTALLATION - To control the backup of all databases in one installation:

Any lines in the following override the above and affect all databases.

ED DOS BACKUP.CFG

MULTIPLE INSTALLATIONS - To control the backup of multiple parallel installations.

Any lines in the following override the above and affect all NEOSYS installations in the same folder.

ED DOS ..\..\BACKUP.CFG

What each line does is as follows:

*backup params
*1=date last attempted
**2= not used ... was workstation for backup (blank defaults to server)
*3=min time of day for backup to start (defaults to 02:00)
*4=max time of day for backup to start (defaults to 02:05)
*5=days to do backup 1234567 1=sun NIGHT!!! EG 2AM
*2/3/4/5 could be multivalued in parallel (to be programmed)
*6=tech support email addresse(s) separated by ';'
*7=backup disk letter
*8=mv list of datasets NOT to backup (press ctrl+E)
*9=1 disable both backup and shutdown completely
*10=email addresses to send backup.zip to OR replacement for 6 if 6 missing backups@neosys.com is excluded in NET from backup.zip recipients
*11=1=suppress backup but do shutdown (testdata)
*12=backup disk for uploads folder if different from 7
*13=backup media check method: blank is default (weekly rotation) 1=wrong media doesnt fail the backup

==== Configuring which days the backup will be done on ====

Line 5 should a list of digits indicating desired days of week 1-7 where 1 is Monday

e.g. 23456 to backup on Mon-Fri night

NB Assuming the backups are at the default time of 2am then you must put "2"
for Monday night since it actually takes place on Tuesday at 2am.

==== Configuring email backup alerts ====

See lines 6 and 10 above

==== Excluding TEST, historical or other databases from backing up every night ====
Database backup is automatically skipped if the last four characters of the database code are TEST or the word TESTING or TRAINING is found in the database name or if the database code is found in the list of database codes (ctrl+e) not to be backed up in line 8 of BACKUP.CFG or if line 11 is set to 1.

==== Backing up the Images folder ====

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 be installed. Incase of old installations, please follow the Cygwin re-installation procedure at [[Setting_up_and_using_remote_support#Upgrading_SSHD_.2F_Cygwin]].

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:

line 12 - and specify the Drive of the location to be backed up to. eg. E or F

=== Configuring automated emails in NEOSYS ===

Login to NEOSYS Maintenance

Press F5

ED DEFINITIONS SMTP.CFG

and press enter (F9/Esc to save and exit)

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS SMTP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations. Available in NEOSYS versions dated 24/4/2007 onwards.

ED DOS ..\..\SMTP.CFG

Lines are fixed (only first two lines are required)

#sender email (must be acceptable to the smtp host name following)
#smtp host name (domain name or ip number)
#smtp port number (blank for 25)
#smtp timeout in seconds (blank for 60?)
#smto use ssl (1=yes, blank for no) ssl is secure connection
#smtp authorization type (1)
#smtp user
#smtp pass

Typical configuration

in DOS SMTP.CFG

clientname@neosys.com
mailout.neosys.com
2500

Note that neosys mail server will accept email from anywhere as long as the sender email is @neosys.com

=== Copying a single record from one database to another ===

You need to know the file name and record key of the record to be copied.

In this case the file is DEFINITIONS and the key is AGENCY.PARAMS

You can invent any old style 8.3 filename instead of C:\AGP.DAT in the following example

On the source computer:

F5
COPY DEFINITIONS AGENCY.PARAMS TO: (DOS C:\AGP.DAT)

On the target computer:

F5
COPY DOS C:\AGP.DAT (ON) TO: (DEFINITIONS AGENCY.PARAMS)

The (O) option is required to force overwrite of the existing

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.

== NEOSYS Authorisation File ==

=== Preventing users from assigning their own passwords ===

The task AUTHORISATION INVENT OWN PASSWORDS should always have the lock NEOSYS to prevent users from creating their own passwords. Most users create unsafe passwords given the choice.

People nearly always ask to give their own passwords but you should tell them that NEOSYS always assigns random passwords for security reasons. It is not worth arguing and discussing the point with most people since they don't usually grasp the importance and soon learn their NEOSYS password anyway.

NEOSYS support staff who login as NEOSYS are still authorised to create their own passwords but it is better not to leak this information to clients immediately since people will grasp on to it and be disappointed or even offended that you are not granting this privilege to them.

Unfortunately there is no general way for people to change their own passwords at the moment. Only the few people who have access to the Support Menu and Authorisation File can do it. Changing your own passwords should be on the NEOSYS Help menu so everybody can do it.

== Allowing users temporary login as NEOSYS in maintenance mode ==

#Get them to login with any name even NEOSYS
#Get the to enter "?" for the pass without the quotes
#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
#Follow the NEOSYS lock/key procedure using the full contents of the lock including the user name
(to allow access EXCEPT access to authorisation screen use 132456 as the last number of the initial command)
#Give them the key and get them to enter and proceed

== Giving users access to the Support Menu ==

The Support Menu in NEOSYS enables users to access the following:

# List of Database processes
# List of Documents in use
# Stop/Restart NEOSYS service
# Backup
# Log
# Authorisation file

This menu is locked with the task SUPPORT MENU ACCESS and has the LS key. To give any user/I.T. administrator access to this menu, you have to give him the LS key.

== Configuring payment instruction text ==

NEOSYS picks up the first available payment instructions from the following locations and ignores any instructions in the later files.

#Client file
#Currency file
#Company file
#Configuration File

If, following the normal rules, the payment instructions are "NONE" then the instructions are blank.

There is a manually edited flag in the company file on one NEOSYS client (cannot remember which) which makes the company file payment instructions take precedence over any currency file payment instructions. This may be added to the Client File u/i as "For all currencies"

The usual way of configuring payment instructions is to put it in the Company file under Finance. However this does not allow for different payment instructions per currency. If you put the payment instructions in the currency file however, then these instructions apply to all companies unless you edit the manual flag in the company record to say that the company file instructions take precedence over. There is no way at the moment in NEOSYS to have different instructions per company AND per currency.

Tip: Since the rules of getting payment instructions are not simple, if you are *changing* payment instructions, locate where the old instructions are and simply change them without worrying about the rules.

== Configuring upload of photoshop "cs2" jpg files ==

Photoshop version "cs2" produces jpg files that cannot be viewed in Internet Explorer.

A solution is to rename the files extension from .jpg to .psjpg before uploading.

"psjpg" files are an invention of NEOSYS and IIS must be configured to handle .psjpg files as follows:

Windows Server 2003 (doesnt work on XP)

#Computer Management, Internet Information Server, Properties
#Click MIME Types
#Click New
#Extension: psjpg
#MIME Type: application/photoshop
#Click OK,OK,OK
#Restart IIS (Right click, All Tasks, Restart)

Configuring NEOSYS Generally

2007-12-27T17:52:00Z

77.68.3.139: /* Configuring backup procedures */

=== Configuring letterhead ===
[[Configuring Letterhead]]

=== Configuring Client Security mark ===
All client installations are hardcoded with the name of the NEOSYS client allowed to use the software. This client mark is generated by the programmer and given to Technical Staff during installation and is a mandatory feature and cannot be removed. This Client security mark is printed on all documents generated out of NEOSYS and appears as below:

[[Image:clientsecuritymark.jpg]]

This can be changed incase the client's legal name changes.

The client security mark is configured by editing:

ED DEFINITIONS AGENCY.PARAMS

Line 1

This client mark can be displayed as an email hyperlink for all the reports generated (such as Media Diary, List of Ads Pending Booking, List of Invoices etc.) and this hyperlink can be configured by editing:

ED DOS SYSTEM.CFG

Line 10

=== Configuring fonts and colors for all users ===

Current latest version of NEOSYS software allows choice of font for all columnar reports and documents produced by NEOSYS.

The default for all NEOSYS reports and documents unless you follow this procedure is a dark and light buff yellow.

ED DEFINITIONS SYSTEM

line 46 then press Ctrl+E to edit multivalues (sublines)

mv 1: color for table column heading rows

mv 2: color for table body rows

mv 3: font

Press F9 to save, then Esc to get out of editing multivalues

Users can override the above the colors and fonts in their user details after login.

=== Changing the signatory ===

In Maintenance mode, press F5 and the following command:

ED DEFINITIONS AGENCY.PARAMS

Be careful not to insert lines except at the end. Moving other lines down will totally screw NEOSYS!

Than go to the bottom of the page (Ctrl+Page down). Once you reach at the bottom, ENTER enough times to add additional lines if required, than search for '''line 61''' (Ctrl+G) and edit the document / add this code:

 Name of General Manager General Manager 

=== Clearing files in database (done when you want to clean an old database) ===

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.

Clear data F5 CLEAROP (only clears transactions not reference files)

Clear suppliers F5 CLEARFILE SUPPLIERS

Clear Vehicles F5 CLEARFILE VEHICLES

Flush Index F5 FLUSH.INDEX

Clear all F5 CLEARALL (rather nasty command because clears all reference files as well)

=== Configuring backup procedures ===

F5

ED DEFINITIONS BACKUP

You can change the email addresses and the Drive to backup.

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS BACKUP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations.

ED DOS ..\..\BACKUP.CFG

What each line does is as follows:

*backup params
*1=date last attempted
**2= not used ... was workstation for backup (blank defaults to server)
*3=min time of day for backup to start (defaults to 02:00)
*4=max time of day for backup to start (defaults to 02:05)
*5=days to do backup 1234567 1=sun NIGHT!!! EG 2AM
*2/3/4/5 could be multivalued in parallel (to be programmed)
*6=tech support email addresse(s) separated by ';'
*7=backup disk letter
*8=mv list of datasets NOT to backup (press ctrl+E)
*9=1 disable both backup and shutdown completely
*10=email addresses to send backup.zip to OR replacement for 6 if 6 missing backups@neosys.com is excluded in NET from backup.zip recipients
*11=1=suppress backup but do shutdown (testdata)
*12=backup disk for uploads folder if different from 7
*13=backup media check method: blank is default (weekly rotation) 1=wrong media doesnt fail the backup

==== Configuring which days the backup will be done on ====

Line 5 should a list of digits indicating desired days of week 1-7 where 1 is Monday

e.g. 23456 to backup on Mon-Fri night

NB Assuming the backups are at the default time of 2am then you must put "2"
for Monday night since it actually takes place on Tuesday at 2am.

==== Configuring email backup alerts ====

See lines 6 and 10 above

==== Excluding TEST, historical or other databases from backing up every night ====
Database backup is automatically skipped if the last four characters of the database code are TEST or the word TESTING or TRAINING is found in the database name or if the database code is found in the list of database codes (ctrl+e) not to be backed up in line 8 of BACKUP.CFG or if line 11 is set to 1.

==== Backing up the Images folder ====

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 be installed. Incase of old installations, please follow the Cygwin re-installation procedure at [[Setting_up_and_using_remote_support#Upgrading_SSHD_.2F_Cygwin]].

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:

line 12 - and specify the Drive of the location to be backed up to. eg. E or F

=== Configuring automated emails in NEOSYS ===

Login to NEOSYS Maintenance

Press F5

ED DEFINITIONS SMTP.CFG

and press enter (F9/Esc to save and exit)

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS SMTP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations. Available in NEOSYS versions dated 24/4/2007 onwards.

ED DOS ..\..\SMTP.CFG

Lines are fixed (only first two lines are required)

#sender email (must be acceptable to the smtp host name following)
#smtp host name (domain name or ip number)
#smtp port number (blank for 25)
#smtp timeout in seconds (blank for 60?)
#smto use ssl (1=yes, blank for no) ssl is secure connection
#smtp authorization type (1)
#smtp user
#smtp pass

Typical configuration

in DOS SMTP.CFG

clientname@neosys.com
mailout.neosys.com
2500

Note that neosys mail server will accept email from anywhere as long as the sender email is @neosys.com

=== Copying a single record from one database to another ===

You need to know the file name and record key of the record to be copied.

In this case the file is DEFINITIONS and the key is AGENCY.PARAMS

You can invent any old style 8.3 filename instead of C:\AGP.DAT in the following example

On the source computer:

F5
COPY DEFINITIONS AGENCY.PARAMS TO: (DOS C:\AGP.DAT)

On the target computer:

F5
COPY DOS C:\AGP.DAT (ON) TO: (DEFINITIONS AGENCY.PARAMS)

The (O) option is required to force overwrite of the existing

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.

== NEOSYS Authorisation File ==

=== Preventing users from assigning their own passwords ===

The task AUTHORISATION INVENT OWN PASSWORDS should always have the lock NEOSYS to prevent users from creating their own passwords. Most users create unsafe passwords given the choice.

People nearly always ask to give their own passwords but you should tell them that NEOSYS always assigns random passwords for security reasons. It is not worth arguing and discussing the point with most people since they don't usually grasp the importance and soon learn their NEOSYS password anyway.

NEOSYS support staff who login as NEOSYS are still authorised to create their own passwords but it is better not to leak this information to clients immediately since people will grasp on to it and be disappointed or even offended that you are not granting this privilege to them.

Unfortunately there is no general way for people to change their own passwords at the moment. Only the few people who have access to the Support Menu and Authorisation File can do it. Changing your own passwords should be on the NEOSYS Help menu so everybody can do it.

== Allowing users temporary login as NEOSYS in maintenance mode ==

#Get them to login with any name even NEOSYS
#Get the to enter "?" for the pass without the quotes
#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
#Follow the NEOSYS lock/key procedure using the full contents of the lock including the user name
(to allow access EXCEPT access to authorisation screen use 132456 as the last number of the initial command)
#Give them the key and get them to enter and proceed

== Giving users access to the Support Menu ==

The Support Menu in NEOSYS enables users to access the following:

# List of Database processes
# List of Documents in use
# Stop/Restart NEOSYS service
# Backup
# Log
# Authorisation file

This menu is locked with the task SUPPORT MENU ACCESS and has the LS key. To give any user/I.T. administrator access to this menu, you have to give him the LS key.

== Configuring payment instruction text ==

NEOSYS picks up the first available payment instructions from the following locations and ignores any instructions in the later files.

#Client file
#Currency file
#Company file
#Configuration File

If, following the normal rules, the payment instructions are "NONE" then the instructions are blank.

There is a manually edited flag in the company file on one NEOSYS client (cannot remember which) which makes the company file payment instructions take precedence over any currency file payment instructions. This may be added to the Client File u/i as "For all currencies"

The usual way of configuring payment instructions is to put it in the Company file under Finance. However this does not allow for different payment instructions per currency. If you put the payment instructions in the currency file however, then these instructions apply to all companies unless you edit the manual flag in the company record to say that the company file instructions take precedence over. There is no way at the moment in NEOSYS to have different instructions per company AND per currency.

Tip: Since the rules of getting payment instructions are not simple, if you are *changing* payment instructions, locate where the old instructions are and simply change them without worrying about the rules.

== Configuring upload of photoshop "cs2" jpg files ==

Photoshop version "cs2" produces jpg files that cannot be viewed in Internet Explorer.

A solution is to rename the files extension from .jpg to .psjpg before uploading.

"psjpg" files are an invention of NEOSYS and IIS must be configured to handle .psjpg files as follows:

Windows Server 2003 (doesnt work on XP)

#Computer Management, Internet Information Server, Properties
#Click MIME Types
#Click New
#Extension: psjpg
#MIME Type: application/photoshop
#Click OK,OK,OK
#Restart IIS (Right click, All Tasks, Restart)

Configuring NEOSYS Generally

2007-12-27T17:50:34Z

77.68.3.139:

=== Configuring letterhead ===
[[Configuring Letterhead]]

=== Configuring Client Security mark ===
All client installations are hardcoded with the name of the NEOSYS client allowed to use the software. This client mark is generated by the programmer and given to Technical Staff during installation and is a mandatory feature and cannot be removed. This Client security mark is printed on all documents generated out of NEOSYS and appears as below:

[[Image:clientsecuritymark.jpg]]

This can be changed incase the client's legal name changes.

The client security mark is configured by editing:

ED DEFINITIONS AGENCY.PARAMS

Line 1

This client mark can be displayed as an email hyperlink for all the reports generated (such as Media Diary, List of Ads Pending Booking, List of Invoices etc.) and this hyperlink can be configured by editing:

ED DOS SYSTEM.CFG

Line 10

=== Configuring fonts and colors for all users ===

Current latest version of NEOSYS software allows choice of font for all columnar reports and documents produced by NEOSYS.

The default for all NEOSYS reports and documents unless you follow this procedure is a dark and light buff yellow.

ED DEFINITIONS SYSTEM

line 46 then press Ctrl+E to edit multivalues (sublines)

mv 1: color for table column heading rows

mv 2: color for table body rows

mv 3: font

Press F9 to save, then Esc to get out of editing multivalues

Users can override the above the colors and fonts in their user details after login.

=== Changing the signatory ===

In Maintenance mode, press F5 and the following command:

ED DEFINITIONS AGENCY.PARAMS

Be careful not to insert lines except at the end. Moving other lines down will totally screw NEOSYS!

Than go to the bottom of the page (Ctrl+Page down). Once you reach at the bottom, ENTER enough times to add additional lines if required, than search for '''line 61''' (Ctrl+G) and edit the document / add this code:

 Name of General Manager General Manager 

=== Clearing files in database (done when you want to clean an old database) ===

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.

Clear data F5 CLEAROP (only clears transactions not reference files)

Clear suppliers F5 CLEARFILE SUPPLIERS

Clear Vehicles F5 CLEARFILE VEHICLES

Flush Index F5 FLUSH.INDEX

Clear all F5 CLEARALL (rather nasty command because clears all reference files as well)

=== Configuring backup procedures ===

F5

ED DEFINITIONS BACKUP

You can change the email addresses and the Drive to backup.

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS BACKUP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations.

ED DOS ..\..\BACKUP.CFG

What each line does is as follows:

*backup params
*1=date last attempted
**2= not used ... was workstation for backup (blank defaults to server)
*3=min time of day for backup to start (defaults to 02:00)
*4=max time of day for backup to start (defaults to 02:05)
*5=days to do backup 1234567 1=sun NIGHT!!! EG 2AM
*2/3/4/5 could be multivalued in parallel (to be programmed)
*6=tech support email addresse(s) separated by ';'
*7=backup disk letter
*8=mv list of datasets NOT to backup (press ctrl+E)
*9=1 disable both backup and shutdown completely
*10=email addresses to send backup.zip to OR replacement for 6 if 6 missing backups@neosys.com is excluded in NET from backup.zip recipients
*11=1=suppress backup but do shutdown (testdata)
*12=backup disk for uploads folder if different from 7
*13='' is default (weekly rotation) 1=wrong media doesnt fail the backup

==== Configuring which days the backup will be done on ====

Line 5 should a list of digits indicating desired days of week 1-7 where 1 is Monday

e.g. 23456 to backup on Mon-Fri night

NB Assuming the backups are at the default time of 2am then you must put "2"
for Monday night since it actually takes place on Tuesday at 2am.

==== Configuring email backup alerts ====

See lines 6 and 10 above

==== Excluding TEST, historical or other databases from backing up every night ====
Database backup is automatically skipped if the last four characters of the database code are TEST or the word TESTING or TRAINING is found in the database name or if the database code is found in the list of database codes (ctrl+e) not to be backed up in line 8 of BACKUP.CFG or if line 11 is set to 1.

==== Backing up the Images folder ====

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 be installed. Incase of old installations, please follow the Cygwin re-installation procedure at [[Setting_up_and_using_remote_support#Upgrading_SSHD_.2F_Cygwin]].

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:

line 12 - and specify the Drive of the location to be backed up to. eg. E or F

=== Configuring automated emails in NEOSYS ===

Login to NEOSYS Maintenance

Press F5

ED DEFINITIONS SMTP.CFG

and press enter (F9/Esc to save and exit)

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS SMTP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations. Available in NEOSYS versions dated 24/4/2007 onwards.

ED DOS ..\..\SMTP.CFG

Lines are fixed (only first two lines are required)

#sender email (must be acceptable to the smtp host name following)
#smtp host name (domain name or ip number)
#smtp port number (blank for 25)
#smtp timeout in seconds (blank for 60?)
#smto use ssl (1=yes, blank for no) ssl is secure connection
#smtp authorization type (1)
#smtp user
#smtp pass

Typical configuration

in DOS SMTP.CFG

clientname@neosys.com
mailout.neosys.com
2500

Note that neosys mail server will accept email from anywhere as long as the sender email is @neosys.com

=== Copying a single record from one database to another ===

You need to know the file name and record key of the record to be copied.

In this case the file is DEFINITIONS and the key is AGENCY.PARAMS

You can invent any old style 8.3 filename instead of C:\AGP.DAT in the following example

On the source computer:

F5
COPY DEFINITIONS AGENCY.PARAMS TO: (DOS C:\AGP.DAT)

On the target computer:

F5
COPY DOS C:\AGP.DAT (ON) TO: (DEFINITIONS AGENCY.PARAMS)

The (O) option is required to force overwrite of the existing

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.

== NEOSYS Authorisation File ==

=== Preventing users from assigning their own passwords ===

The task AUTHORISATION INVENT OWN PASSWORDS should always have the lock NEOSYS to prevent users from creating their own passwords. Most users create unsafe passwords given the choice.

People nearly always ask to give their own passwords but you should tell them that NEOSYS always assigns random passwords for security reasons. It is not worth arguing and discussing the point with most people since they don't usually grasp the importance and soon learn their NEOSYS password anyway.

NEOSYS support staff who login as NEOSYS are still authorised to create their own passwords but it is better not to leak this information to clients immediately since people will grasp on to it and be disappointed or even offended that you are not granting this privilege to them.

Unfortunately there is no general way for people to change their own passwords at the moment. Only the few people who have access to the Support Menu and Authorisation File can do it. Changing your own passwords should be on the NEOSYS Help menu so everybody can do it.

== Allowing users temporary login as NEOSYS in maintenance mode ==

#Get them to login with any name even NEOSYS
#Get the to enter "?" for the pass without the quotes
#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
#Follow the NEOSYS lock/key procedure using the full contents of the lock including the user name
(to allow access EXCEPT access to authorisation screen use 132456 as the last number of the initial command)
#Give them the key and get them to enter and proceed

== Giving users access to the Support Menu ==

The Support Menu in NEOSYS enables users to access the following:

# List of Database processes
# List of Documents in use
# Stop/Restart NEOSYS service
# Backup
# Log
# Authorisation file

This menu is locked with the task SUPPORT MENU ACCESS and has the LS key. To give any user/I.T. administrator access to this menu, you have to give him the LS key.

== Configuring payment instruction text ==

NEOSYS picks up the first available payment instructions from the following locations and ignores any instructions in the later files.

#Client file
#Currency file
#Company file
#Configuration File

If, following the normal rules, the payment instructions are "NONE" then the instructions are blank.

There is a manually edited flag in the company file on one NEOSYS client (cannot remember which) which makes the company file payment instructions take precedence over any currency file payment instructions. This may be added to the Client File u/i as "For all currencies"

The usual way of configuring payment instructions is to put it in the Company file under Finance. However this does not allow for different payment instructions per currency. If you put the payment instructions in the currency file however, then these instructions apply to all companies unless you edit the manual flag in the company record to say that the company file instructions take precedence over. There is no way at the moment in NEOSYS to have different instructions per company AND per currency.

Tip: Since the rules of getting payment instructions are not simple, if you are *changing* payment instructions, locate where the old instructions are and simply change them without worrying about the rules.

== Configuring upload of photoshop "cs2" jpg files ==

Photoshop version "cs2" produces jpg files that cannot be viewed in Internet Explorer.

A solution is to rename the files extension from .jpg to .psjpg before uploading.

"psjpg" files are an invention of NEOSYS and IIS must be configured to handle .psjpg files as follows:

Windows Server 2003 (doesnt work on XP)

#Computer Management, Internet Information Server, Properties
#Click MIME Types
#Click New
#Extension: psjpg
#MIME Type: application/photoshop
#Click OK,OK,OK
#Restart IIS (Right click, All Tasks, Restart)

Configuring NEOSYS Generally

2007-12-27T17:44:23Z

77.68.3.139: /* Backing up multiple databases on one installation */

=== Configuring letterhead ===
[[Configuring Letterhead]]

=== Configuring Client Security mark ===
All client installations are hardcoded with the name of the NEOSYS client allowed to use the software. This client mark is generated by the programmer and given to Technical Staff during installation and is a mandatory feature and cannot be removed. This Client security mark is printed on all documents generated out of NEOSYS and appears as below:

[[Image:clientsecuritymark.jpg]]

This can be changed incase the client's legal name changes.

The client security mark is configured by editing:

ED DEFINITIONS AGENCY.PARAMS

Line 1

This client mark can be displayed as an email hyperlink for all the reports generated (such as Media Diary, List of Ads Pending Booking, List of Invoices etc.) and this hyperlink can be configured by editing:

ED DOS SYSTEM.CFG

Line 10

=== Configuring fonts and colors for all users ===

Current latest version of NEOSYS software allows choice of font for all columnar reports and documents produced by NEOSYS.

The default for all NEOSYS reports and documents unless you follow this procedure is a dark and light buff yellow.

ED DEFINITIONS SYSTEM

line 46 then press Ctrl+E to edit multivalues (sublines)

mv 1: color for table column heading rows

mv 2: color for table body rows

mv 3: font

Press F9 to save, then Esc to get out of editing multivalues

Users can override the above the colors and fonts in their user details after login.

=== Changing the signatory ===

In Maintenance mode, press F5 and the following command:

ED DEFINITIONS AGENCY.PARAMS

Be careful not to insert lines except at the end. Moving other lines down will totally screw NEOSYS!

Than go to the bottom of the page (Ctrl+Page down). Once you reach at the bottom, ENTER enough times to add additional lines if required, than search for '''line 61''' (Ctrl+G) and edit the document / add this code:

 Name of General Manager General Manager 

=== Clearing files in database (done when you want to clean an old database) ===

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.

Clear data F5 CLEAROP (only clears transactions not reference files)

Clear suppliers F5 CLEARFILE SUPPLIERS

Clear Vehicles F5 CLEARFILE VEHICLES

Flush Index F5 FLUSH.INDEX

Clear all F5 CLEARALL (rather nasty command because clears all reference files as well)

=== Configuring which days the backup will be done on ===

F5

ED DEFINITIONS BACKUP

Line 5 should a list of digits indicating desired days of week 1-7 where 1 is Monday

e.g. 23456 to backup on Mon-Fri night

NB Assuming the backups are at the default time of 2am then you must put "2"
for Monday night since it actually takes place on Tuesday at 2am.

=== Configuring email backup alerts ===

F5

ED DEFINITIONS BACKUP

You can change the email addresses and the Drive to backup.

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS BACKUP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations.

ED DOS ..\..\BACKUP.CFG

What each line does is as follows:

*backup params
*1=date last attempted
**2= not used ... was workstation for backup (blank defaults to server)
*3=min time of day for backup to start (defaults to 02:00)
*4=max time of day for backup to start (defaults to 02:05)
*5=days to do backup 1234567 1=sun NIGHT!!! EG 2AM
*2/3/4/5 could be multivalued in parallel (to be programmed)
*6=tech support email addresse(s) separated by ';'
*7=backup disk letter
*8=mv list of datasets NOT to backup (press ctrl+E)
*9=1 disable both backup and shutdown completely
*10=email addresses to send backup.zip to OR replacement for 6 if 6 missing
*backups@neosys.com is excluded in NET from backup.zip recipients
*11=1=suppress backup but do shutdown (testdata)

==== Excluding TEST, historical or other databases from backing up every night ====
Database backup is automatically skipped if the last four characters of the database code are TEST or the word TESTING or TRAINING is found in the database name or if the database code is found in the list of database codes (ctrl+e) not to be backed up in line 8 of BACKUP.CFG or if line 11 is set to 1.

==== Backing up the Images folder ====

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 be installed. Incase of old installations, please follow the Cygwin re-installation procedure at [[Setting_up_and_using_remote_support#Upgrading_SSHD_.2F_Cygwin]].

Incase we need to configure the Images folder backup at another location other than the usual daily backup location than we need to edit:

ED DEFINITIONS BACKUP

line 12 - and specify the Drive of the location to be backed up to. eg. E or F

=== Configuring automated emails in NEOSYS ===

Login to NEOSYS Maintenance

Press F5

ED DEFINITIONS SMTP.CFG

and press enter (F9/Esc to save and exit)

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS SMTP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations. Available in NEOSYS versions dated 24/4/2007 onwards.

ED DOS ..\..\SMTP.CFG

Lines are fixed (only first two lines are required)

#sender email (must be acceptable to the smtp host name following)
#smtp host name (domain name or ip number)
#smtp port number (blank for 25)
#smtp timeout in seconds (blank for 60?)
#smto use ssl (1=yes, blank for no) ssl is secure connection
#smtp authorization type (1)
#smtp user
#smtp pass

Typical configuration

in DOS SMTP.CFG

clientname@neosys.com
mailout.neosys.com
2500

Note that neosys mail server will accept email from anywhere as long as the sender email is @neosys.com

=== Copying a single record from one database to another ===

You need to know the file name and record key of the record to be copied.

In this case the file is DEFINITIONS and the key is AGENCY.PARAMS

You can invent any old style 8.3 filename instead of C:\AGP.DAT in the following example

On the source computer:

F5
COPY DEFINITIONS AGENCY.PARAMS TO: (DOS C:\AGP.DAT)

On the target computer:

F5
COPY DOS C:\AGP.DAT (ON) TO: (DEFINITIONS AGENCY.PARAMS)

The (O) option is required to force overwrite of the existing

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.

== NEOSYS Authorisation File ==

=== Preventing users from assigning their own passwords ===

The task AUTHORISATION INVENT OWN PASSWORDS should always have the lock NEOSYS to prevent users from creating their own passwords. Most users create unsafe passwords given the choice.

People nearly always ask to give their own passwords but you should tell them that NEOSYS always assigns random passwords for security reasons. It is not worth arguing and discussing the point with most people since they don't usually grasp the importance and soon learn their NEOSYS password anyway.

NEOSYS support staff who login as NEOSYS are still authorised to create their own passwords but it is better not to leak this information to clients immediately since people will grasp on to it and be disappointed or even offended that you are not granting this privilege to them.

Unfortunately there is no general way for people to change their own passwords at the moment. Only the few people who have access to the Support Menu and Authorisation File can do it. Changing your own passwords should be on the NEOSYS Help menu so everybody can do it.

== Allowing users temporary login as NEOSYS in maintenance mode ==

#Get them to login with any name even NEOSYS
#Get the to enter "?" for the pass without the quotes
#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
#Follow the NEOSYS lock/key procedure using the full contents of the lock including the user name
(to allow access EXCEPT access to authorisation screen use 132456 as the last number of the initial command)
#Give them the key and get them to enter and proceed

== Giving users access to the Support Menu ==

The Support Menu in NEOSYS enables users to access the following:

# List of Database processes
# List of Documents in use
# Stop/Restart NEOSYS service
# Backup
# Log
# Authorisation file

This menu is locked with the task SUPPORT MENU ACCESS and has the LS key. To give any user/I.T. administrator access to this menu, you have to give him the LS key.

== Configuring payment instruction text ==

NEOSYS picks up the first available payment instructions from the following locations and ignores any instructions in the later files.

#Client file
#Currency file
#Company file
#Configuration File

If, following the normal rules, the payment instructions are "NONE" then the instructions are blank.

There is a manually edited flag in the company file on one NEOSYS client (cannot remember which) which makes the company file payment instructions take precedence over any currency file payment instructions. This may be added to the Client File u/i as "For all currencies"

The usual way of configuring payment instructions is to put it in the Company file under Finance. However this does not allow for different payment instructions per currency. If you put the payment instructions in the currency file however, then these instructions apply to all companies unless you edit the manual flag in the company record to say that the company file instructions take precedence over. There is no way at the moment in NEOSYS to have different instructions per company AND per currency.

Tip: Since the rules of getting payment instructions are not simple, if you are *changing* payment instructions, locate where the old instructions are and simply change them without worrying about the rules.

== Configuring upload of photoshop "cs2" jpg files ==

Photoshop version "cs2" produces jpg files that cannot be viewed in Internet Explorer.

A solution is to rename the files extension from .jpg to .psjpg before uploading.

"psjpg" files are an invention of NEOSYS and IIS must be configured to handle .psjpg files as follows:

Windows Server 2003 (doesnt work on XP)

#Computer Management, Internet Information Server, Properties
#Click MIME Types
#Click New
#Extension: psjpg
#MIME Type: application/photoshop
#Click OK,OK,OK
#Restart IIS (Right click, All Tasks, Restart)

Configuring NEOSYS Generally

2007-11-26T20:22:59Z

77.68.3.139: /* Configuring payment instruction text */

=== Configuring letterhead ===
[[Configuring Letterhead]]

=== Configuring Client Security mark ===
All client installations are hardcoded with the name of the NEOSYS client allowed to use the software. This client mark is generated by the programmer and given to Technical Staff during installation and is a mandatory feature and cannot be removed. This Client security mark is printed on all documents generated out of NEOSYS and appears as below:

[[Image:clientsecuritymark.jpg]]

This can be changed incase the client's legal name changes.

The client security mark is configured by editing:

ED DEFINITIONS AGENCY.PARAMS

Line 1

This client mark can be displayed as an email hyperlink for all the reports generated (such as Media Diary, List of Ads Pending Booking, List of Invoices etc.) and this hyperlink can be configured by editing:

ED DOS SYSTEM.CFG

Line 10

=== Configuring fonts and colors for all users ===

Current latest version of NEOSYS software allows choice of font for all columnar reports and documents produced by NEOSYS.

The default for all NEOSYS reports and documents unless you follow this procedure is a dark and light buff yellow.

ED DEFINITIONS SYSTEM

line 46 then press Ctrl+E to edit multivalues (sublines)

mv 1: color for table column heading rows

mv 2: color for table body rows

mv 3: font

Press F9 to save, then Esc to get out of editing multivalues

Users can override the above the colors and fonts in their user details after login.

=== Changing the signatory ===

In Maintenance mode, press F5 and the following command:

ED DEFINITIONS AGENCY.PARAMS

Be careful not to insert lines except at the end. Moving other lines down will totally screw NEOSYS!

Than go to the bottom of the page (Ctrl+Page down). Once you reach at the bottom, ENTER enough times to add additional lines if required, than search for '''line 61''' (Ctrl+G) and edit the document / add this code:

 Name of General Manager General Manager 

=== Clearing files in database (done when you want to clean an old database) ===

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.

Clear data F5 CLEAROP (only clears transactions not reference files)

Clear suppliers F5 CLEARFILE SUPPLIERS

Clear Vehicles F5 CLEARFILE VEHICLES

Flush Index F5 FLUSH.INDEX

Clear all F5 CLEARALL (rather nasty command because clears all reference files as well)

=== Configuring which days the backup will be done on ===

F5

ED DEFINITIONS BACKUP

Line 5 should a list of digits indicating desired days of week 1-7 where 1 is Monday

e.g. 23456 to backup on Mon-Fri night

NB Assuming the backups are at the default time of 2am then you must put "2"
for Monday night since it actually takes place on Tuesday at 2am.

=== Configuring email backup alerts ===

F5

ED DEFINITIONS BACKUP

You can change the email addresses and the Drive to backup.

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS BACKUP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations.

ED DOS ..\..\BACKUP.CFG

What each line does is as follows:

*backup params
*1=date last attempted
**2= not used ... was workstation for backup (blank defaults to server)
*3=min time of day for backup to start (defaults to 02:00)
*4=max time of day for backup to start (defaults to 02:05)
*5=days to do backup 1234567 1=sun NIGHT!!! EG 2AM
*2/3/4/5 could be multivalued in parallel (to be programmed)
*6=tech support email addresse(s) separated by ';'
*7=backup disk letter
*8=mv list of datasets NOT to backup (press ctrl+E)
*9=1 disable both backup and shutdown completely
*10=email addresses to send backup.zip to OR replacement for 6 if 6 missing
*backups@neosys.com is excluded in NET from backup.zip recipients
*11=1=suppress backup but do shutdown (testdata)

==== Excluding TEST, historical or other databases from backing up every night ====
Database backup is automatically skipped if the last four characters of the database code are TEST or the word TESTING or TRAINING is found in the database name or if the database code is found in the list of database codes (ctrl+e) not to be backed up in line 8 of BACKUP.CFG or if line 11 is set to 1.

==== Backing up multiple databases on one installation ====
There is no way to backup multiple databases on the same night but you can arrange for one database to be backed up on days 1357 and another on days 246. Three databases could be backed up every third day eg the first database on days 147, the second on 25 and the third on days 36.

Assuming backups are done at 2am then the day 1 backup is done at 2am on Monday night and therefore is the backup of work done on '''Sunday'''. If the working week starts on Sunday then the above numbers should be reduced by 1. If on Saturday then by 2. Reducing day 1 by 2 days makes it day 6. The reason is that backup over the weekend is less important and therefore the extra backup for the first database should be aligned on a less important day of the week.

==== Backing up the Images folder ====

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 be installed. Incase of old installations, please follow the Cygwin re-installation procedure at [[Setting_up_and_using_remote_support#Upgrading_SSHD_.2F_Cygwin]].

Incase we need to configure the Images folder backup at another location other than the usual daily backup location than we need to edit:

ED DEFINITIONS BACKUP

line 12 - and specify the Drive of the location to be backed up to. eg. E or F

=== Configuring automated emails in NEOSYS ===

Login to NEOSYS Maintenance

Press F5

ED DEFINITIONS SMTP.CFG

and press enter (F9/Esc to save and exit)

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS SMTP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations. Available in NEOSYS versions dated 24/4/2007 onwards.

ED DOS ..\..\SMTP.CFG

Lines are fixed (only first two lines are required)

#sender email (must be acceptable to the smtp host name following)
#smtp host name (domain name or ip number)
#smtp port number (blank for 25)
#smtp timeout in seconds (blank for 60?)
#smto use ssl (1=yes, blank for no) ssl is secure connection
#smtp authorization type ()
#smtp user
#smtp pass

Typical configuration

in DOS SMTP.CFG

clientname@neosys.com
mailout.neosys.com
2500

Note that neosys mail server will accept email from anywhere as long as the sender email is @neosys.com

=== Copying a single record from one database to another ===

You need to know the file name and record key of the record to be copied.

In this case the file is DEFINITIONS and the key is AGENCY.PARAMS

You can invent any old style 8.3 filename instead of C:\AGP.DAT in the following example

On the source computer:

F5
COPY DEFINITIONS AGENCY.PARAMS TO: (DOS C:\AGP.DAT)

On the target computer:

F5
COPY DOS C:\AGP.DAT (ON) TO: (DEFINITIONS AGENCY.PARAMS)

The (O) option is required to force overwrite of the existing

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.

== NEOSYS Authorisation File ==

=== Preventing users from assigning their own passwords ===

The task AUTHORISATION INVENT OWN PASSWORDS should always have the lock NEOSYS to prevent users from creating their own passwords. Most users create unsafe passwords given the choice.

People nearly always ask to give their own passwords but you should tell them that NEOSYS always assigns random passwords for security reasons. It is not worth arguing and discussing the point with most people since they don't usually grasp the importance and soon learn their NEOSYS password anyway.

NEOSYS support staff who login as NEOSYS are still authorised to create their own passwords but it is better not to leak this information to clients immediately since people will grasp on to it and be disappointed or even offended that you are not granting this privilege to them.

Unfortunately there is no general way for people to change their own passwords at the moment. Only the few people who have access to the Support Menu and Authorisation File can do it. Changing your own passwords should be on the NEOSYS Help menu so everybody can do it.

== Allowing users temporary login as NEOSYS in maintenance mode ==

#Get them to login with any name even NEOSYS
#Get the to enter "?" for the pass without the quotes
#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
#Follow the NEOSYS lock/key procedure using the full contents of the lock including the user name
(to allow access EXCEPT access to authorisation screen use 132456 as the last number of the initial command)
#Give them the key and get them to enter and proceed

== Giving users access to the Support Menu ==

The Support Menu in NEOSYS enables users to access the following:

# List of Database processes
# List of Documents in use
# Stop/Restart NEOSYS service
# Backup
# Log
# Authorisation file

This menu is locked with the task SUPPORT MENU ACCESS and has the LS key. To give any user/I.T. administrator access to this menu, you have to give him the LS key.

== Configuring payment instruction text ==

NEOSYS picks up the first available payment instructions from the following locations and ignores any instructions in the later files.

#Client file
#Currency file
#Company file
#Configuration File

If, following the normal rules, the payment instructions are "NONE" then the instructions are blank.

There is a manually edited flag in the company file on one NEOSYS client (cannot remember which) which makes the company file payment instructions take precedence over any currency file payment instructions. This may be added to the Client File u/i as "For all currencies"

The usual way of configuring payment instructions is to put it in the Company file under Finance. However this does not allow for different payment instructions per currency. If you put the payment instructions in the currency file however, then these instructions apply to all companies unless you edit the manual flag in the company record to say that the company file instructions take precedence over. There is no way at the moment in NEOSYS to have different instructions per company AND per currency.

Tip: Since the rules of getting payment instructions are not simple, if you are *changing* payment instructions, locate where the old instructions are and simply change them without worrying about the rules.

== Configuring upload of photoshop "cs2" jpg files ==

Photoshop version "cs2" produces jpg files that cannot be viewed in Internet Explorer.

A solution is to rename the files extension from .jpg to .psjpg before uploading.

"psjpg" files are an invention of NEOSYS and IIS must be configured to handle .psjpg files as follows:

Windows Server 2003 (doesnt work on XP)

#Computer Management, Internet Information Server, Properties
#Click MIME Types
#Click New
#Extension: psjpg
#MIME Type: application/photoshop
#Click OK,OK,OK
#Restart IIS (Right click, All Tasks, Restart)

Handling damaged files

2007-11-14T01:19:21Z

77.68.3.139: /* Recovery */

== Symptoms ==

"A Damaged file has been found..... ((the rest of this message to be completed))
Group format Error:
OS File : BOOKING.TEXTS
Group# : 00000932
Record length incorrect or frame linkage error.

== Cause ==
Rare but nasty problem on server 99% caused by power failure, killing NEOSYS or server hardware or operating system failure.

*Did somebody kill NEOSYS processes to reboot the server or any other reason?
*Was there a power cut?
*Any expected or unexpected reboots in the server log? (see Event Viewer > System Log)
*Enough disk free space especially on servers not dedicated to neosys?

== Solution==

Depends on the cause and usually often requires aggressive interrogation to discover the cause.

== Recovery==

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.

See the following sections how to patch the damaged files.

== Files that are automatically fixed ==

*LISTS
*LOCKS
*!INDEXING

The above files are automatically checked for corruption (and initialised to empty if so) when you
startup a NEOSYS process and do not require any manual intervention apart from locating and eliminating the initial cause of the damage.

If the !INDEXING file was damaged then strictly speaking you should also do REINDEXALL to reinstate any possibly missing index entries, but since this will take a long time
you should do this when everybody is off the system in the evening probably.

== Fixing damaged files that have no process for recreating them ==

Some damaged files can be rebuilt using NEOSYS utilities especially index files with filenames starting with !. Other damaged files can be “fixed” to prevent NEOSYS crashes as follows but some records will most probably be lost. 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

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:

F5

FIXFILE filename

(Select option 1 to update the file)

In case you get any Overwrite messages – type YES, as these are the actual files being updated.

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.

=== Using FIXFILE to repair corrupted files ===

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.

You can freely use FIXFILE on any file but it 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. Many files do not have programs to rebuild them and FIXFILE is a quick way to get the system back in operation.

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.

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.

You must prevent anyone from accessing NEOSYS while FIXFILE is running.

=== Fixing Damaged DEFINITIONS file ===

==== Non-Solution ====

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.

CAUTION: DO NOT USE FIXFILE TO TRY AND FIX THE DEFINITIONS FILE.

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.

==== Partial Restore ====

You can copy recent DEFINITIONS.LK and DEFINITIONS.OV files from the DATA\datasetcode\GENERAL folder.

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.

==== Full Restore ====

Restore from your latest backup losing all work done since that time and date.

=== Preventing users from accessing NEOSYS in order to do maintenance or repairs ===

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

# Stop the autostart program/script
# Put a file called NET.CFG with a single line saying AUTOSTART=NO in the neosys\neosys folder
# Stop the IIS server
# Stop/Pause the particular web in question

== Fixing damaged file that have a process to recreate them ==

ADS file can be recreated with F5 CREATEADS

ANALYSIS file can be recreated with F5 CREATEANALYSIS

== Fixing damaged index files (names starting with !) ==

Whilst backing up or using NEOSYS the following error message might appear:

"A Damaged file has been found.....
Group format Error:
OS File : !ADS
Group# : 00000932
Record length incorrect or frame linkage error.

#Ensure that no-one is using NEOSYS
#Log into NEOSYS on the server
#Press F5 to get a TCL command box
#Type REINDEXADS and press enter.
#Wait until it finishes and you get back to the command box
#Type OFF in the command box and you will quit NEOSYS.

Other reindex commands are:

*REINDEXACCOUNTS recreates !ACCOUNTS and !BATCHES
*REINDEXADDRESSES
*REINDEXADS
*REINDEXBOOKINGS recreates !BOOKING.ORDERS
*REINDEXBRANDS
*REINDEXCLIENTS
*REINDEXINVS recreates !INVOICES
*REINDEXJOBS
*REINDEXMATERIALS
*REINDEXPLANS
*REINDEXPRODINVS recreates !PRODUCTION.INVOICES
*REINDEXPRODORDERS recreates !PRODUCTION.ORDERS
*REINDEXRATECARDS
*REINDEXSCHEDULES
*REINDEXSUPPLIERS
*REINDEXTIMESHEETS
*REINDEXVEHICLES

REINDEXMEDIA does all the following
*REINDEXPLANS
*REINDEXSCHEDULES
*REINDEXADS
*REINDEXMATERIALS
*REINDEXBOOKINGS

REINDEXFILES does all the following
*REINDEXCLIENTS
*REINDEXBRANDS
*REINDEXSUPPLIERS
*REINDEXVEHICLES
*REINDEXRATECARDS

REINDEXPRODUCTION does all the following
*REINDEXJOBS
*REINDEXPRODORDERS
*REINDEXPRODINVS
*REINDEXTIMESHEETS

REINDEXALL does all the following
*REINDEXMEDIA
*REINDEXPRODUCTION
*REINDEXFILES
*REINDEXINVS
*REINDEXACCOUNTS
*REINDEXADDRESSES

== Dealing with damaged files that cannot be fixed ==

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.

THIS DOES NOT RELEASE NEOSYS SUPPORT STAFF FROM THE OBLIGATION TO PROACTIVELY INFORM THE CLIENT OF MEASURES TO PREVENT THE RECURRENCE OF THE EVENT.

The following are the steps to follow:

# Ascertain the cause of the damage to the database by looking at the internal logs
# Create a new database from the damaged one as it will contain the up to date but damaged database.
# Restore the database from the backup media so that the database is in the last good known state.
# 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.
# 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.

Handling damaged files

2007-11-14T01:13:51Z

77.68.3.139: /* Fixing damaged index files (names starting with !) */

== Symptoms ==

"A Damaged file has been found..... ((the rest of this message to be completed))
Group format Error:
OS File : BOOKING.TEXTS
Group# : 00000932
Record length incorrect or frame linkage error.

== Cause ==
Rare but nasty problem on server 99% caused by power failure, killing NEOSYS or server hardware or operating system failure.

*Did somebody kill NEOSYS processes to reboot the server or any other reason?
*Was there a power cut?
*Any expected or unexpected reboots in the server log? (see Event Viewer > System Log)
*Enough disk free space especially on servers not dedicated to neosys?

== Solution==

Depends on the cause and usually often requires aggressive interrogation to discover the cause.

== Recovery==

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

== Fixing damaged files that have no process for recreating them ==

Some damaged files can be rebuilt using NEOSYS utilities especially index files with filenames starting with !. Other damaged files can be “fixed” to prevent NEOSYS crashes as follows but some records will most probably be lost. 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

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:

F5

FIXFILE filename

(Select option 1 to update the file)

In case you get any Overwrite messages – type YES, as these are the actual files being updated.

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.

=== Using FIXFILE to repair corrupted files ===

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.

You can freely use FIXFILE on any file but it 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. Many files do not have programs to rebuild them and FIXFILE is a quick way to get the system back in operation.

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.

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.

You must prevent anyone from accessing NEOSYS while FIXFILE is running.

=== Fixing Damaged DEFINITIONS file ===

==== Non-Solution ====

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.

CAUTION: DO NOT USE FIXFILE TO TRY AND FIX THE DEFINITIONS FILE.

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.

==== Partial Restore ====

You can copy recent DEFINITIONS.LK and DEFINITIONS.OV files from the DATA\datasetcode\GENERAL folder.

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.

==== Full Restore ====

Restore from your latest backup losing all work done since that time and date.

=== Preventing users from accessing NEOSYS in order to do maintenance or repairs ===

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

# Stop the autostart program/script
# Put a file called NET.CFG with a single line saying AUTOSTART=NO in the neosys\neosys folder
# Stop the IIS server
# Stop/Pause the particular web in question

== Fixing damaged file that have a process to recreate them ==

ADS file can be recreated with F5 CREATEADS

ANALYSIS file can be recreated with F5 CREATEANALYSIS

== Fixing damaged index files (names starting with !) ==

Whilst backing up or using NEOSYS the following error message might appear:

"A Damaged file has been found.....
Group format Error:
OS File : !ADS
Group# : 00000932
Record length incorrect or frame linkage error.

#Ensure that no-one is using NEOSYS
#Log into NEOSYS on the server
#Press F5 to get a TCL command box
#Type REINDEXADS and press enter.
#Wait until it finishes and you get back to the command box
#Type OFF in the command box and you will quit NEOSYS.

Other reindex commands are:

*REINDEXACCOUNTS recreates !ACCOUNTS and !BATCHES
*REINDEXADDRESSES
*REINDEXADS
*REINDEXBOOKINGS recreates !BOOKING.ORDERS
*REINDEXBRANDS
*REINDEXCLIENTS
*REINDEXINVS recreates !INVOICES
*REINDEXJOBS
*REINDEXMATERIALS
*REINDEXPLANS
*REINDEXPRODINVS recreates !PRODUCTION.INVOICES
*REINDEXPRODORDERS recreates !PRODUCTION.ORDERS
*REINDEXRATECARDS
*REINDEXSCHEDULES
*REINDEXSUPPLIERS
*REINDEXTIMESHEETS
*REINDEXVEHICLES

REINDEXMEDIA does all the following
*REINDEXPLANS
*REINDEXSCHEDULES
*REINDEXADS
*REINDEXMATERIALS
*REINDEXBOOKINGS

REINDEXFILES does all the following
*REINDEXCLIENTS
*REINDEXBRANDS
*REINDEXSUPPLIERS
*REINDEXVEHICLES
*REINDEXRATECARDS

REINDEXPRODUCTION does all the following
*REINDEXJOBS
*REINDEXPRODORDERS
*REINDEXPRODINVS
*REINDEXTIMESHEETS

REINDEXALL does all the following
*REINDEXMEDIA
*REINDEXPRODUCTION
*REINDEXFILES
*REINDEXINVS
*REINDEXACCOUNTS
*REINDEXADDRESSES

== Dealing with damaged files that cannot be fixed ==

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.

THIS DOES NOT RELEASE NEOSYS SUPPORT STAFF FROM THE OBLIGATION TO PROACTIVELY INFORM THE CLIENT OF MEASURES TO PREVENT THE RECURRENCE OF THE EVENT.

The following are the steps to follow:

# Ascertain the cause of the damage to the database by looking at the internal logs
# Create a new database from the damaged one as it will contain the up to date but damaged database.
# Restore the database from the backup media so that the database is in the last good known state.
# 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.
# 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.

Handling damaged files

2007-11-14T00:37:25Z

77.68.3.139: /* Fixing damaged index files (names starting with !) */

== Symptoms ==

"A Damaged file has been found..... ((the rest of this message to be completed))
Group format Error:
OS File : BOOKING.TEXTS
Group# : 00000932
Record length incorrect or frame linkage error.

== Cause ==
Rare but nasty problem on server 99% caused by power failure, killing NEOSYS or server hardware or operating system failure.

*Did somebody kill NEOSYS processes to reboot the server or any other reason?
*Was there a power cut?
*Any expected or unexpected reboots in the server log? (see Event Viewer > System Log)
*Enough disk free space especially on servers not dedicated to neosys?

== Solution==

Depends on the cause and usually often requires aggressive interrogation to discover the cause.

== Recovery==

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

== Fixing damaged files that have no process for recreating them ==

Some damaged files can be rebuilt using NEOSYS utilities especially index files with filenames starting with !. Other damaged files can be “fixed” to prevent NEOSYS crashes as follows but some records will most probably be lost. 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

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:

F5

FIXFILE filename

(Select option 1 to update the file)

In case you get any Overwrite messages – type YES, as these are the actual files being updated.

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.

=== Using FIXFILE to repair corrupted files ===

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.

You can freely use FIXFILE on any file but it 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. Many files do not have programs to rebuild them and FIXFILE is a quick way to get the system back in operation.

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.

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.

You must prevent anyone from accessing NEOSYS while FIXFILE is running.

=== Fixing Damaged DEFINITIONS file ===

==== Non-Solution ====

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.

CAUTION: DO NOT USE FIXFILE TO TRY AND FIX THE DEFINITIONS FILE.

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.

==== Partial Restore ====

You can copy recent DEFINITIONS.LK and DEFINITIONS.OV files from the DATA\datasetcode\GENERAL folder.

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.

==== Full Restore ====

Restore from your latest backup losing all work done since that time and date.

=== Preventing users from accessing NEOSYS in order to do maintenance or repairs ===

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

# Stop the autostart program/script
# Put a file called NET.CFG with a single line saying AUTOSTART=NO in the neosys\neosys folder
# Stop the IIS server
# Stop/Pause the particular web in question

== Fixing damaged file that have a process to recreate them ==

ADS file can be recreated with F5 CREATEADS

ANALYSIS file can be recreated with F5 CREATEANALYSIS

== Fixing damaged index files (names starting with !) ==

Whilst backing up or using NEOSYS the following error message might appear:

"A Damaged file has been found.....
Group format Error:
OS File : !ADS
Group# : 00000932
Record length incorrect or frame linkage error.

#Ensure that no-one is using NEOSYS
#Log into NEOSYS on the server
#Press F5 to get a TCL command box
#Type REINDEXADS and press enter.
#Wait until it finishes and you get back to the command box
#Type OFF in the command box and you will quit NEOSYS.

The LISTS, LOCKS and !INDEXING files are automatically checked for corruption (and initialised to empty if so) when you
startup the first Neosys process, and does not require this command to be run. You should probably
also do REINDEXALL to reinstate any possibly missing index entries, but since this will take a long time
you should do this when everybody is off the system in the evening probably.

Other reindex commands are:

*REINDEXACCOUNTS recreates !ACCOUNTS and !BATCHES
*REINDEXADDRESSES
*REINDEXADS
*REINDEXBOOKINGS recreates !BOOKING.ORDERS
*REINDEXBRANDS
*REINDEXCLIENTS
*REINDEXINVS recreates !INVOICES
*REINDEXJOBS
*REINDEXMATERIALS
*REINDEXPLANS
*REINDEXPRODINVS recreates !PRODUCTION.INVOICES
*REINDEXPRODORDERS recreates !PRODUCTION.ORDERS
*REINDEXRATECARDS
*REINDEXSCHEDULES
*REINDEXSUPPLIERS
*REINDEXTIMESHEETS
*REINDEXVEHICLES

REINDEXMEDIA does all the following
*REINDEXPLANS
*REINDEXSCHEDULES
*REINDEXADS
*REINDEXMATERIALS
*REINDEXBOOKINGS

REINDEXFILES does all the following
*REINDEXCLIENTS
*REINDEXBRANDS
*REINDEXSUPPLIERS
*REINDEXVEHICLES
*REINDEXRATECARDS

REINDEXPRODUCTION does all the following
*REINDEXJOBS
*REINDEXPRODORDERS
*REINDEXPRODINVS
*REINDEXTIMESHEETS

REINDEXALL does all the following
*REINDEXMEDIA
*REINDEXPRODUCTION
*REINDEXFILES
*REINDEXINVS
*REINDEXACCOUNTS
*REINDEXADDRESSES

== Dealing with damaged files that cannot be fixed ==

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.

THIS DOES NOT RELEASE NEOSYS SUPPORT STAFF FROM THE OBLIGATION TO PROACTIVELY INFORM THE CLIENT OF MEASURES TO PREVENT THE RECURRENCE OF THE EVENT.

The following are the steps to follow:

# Ascertain the cause of the damage to the database by looking at the internal logs
# Create a new database from the damaged one as it will contain the up to date but damaged database.
# Restore the database from the backup media so that the database is in the last good known state.
# 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.
# 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.

Handling damaged files

2007-11-14T00:34:55Z

77.68.3.139: /* Fixing damaged index files (names starting with !) */

== Symptoms ==

"A Damaged file has been found..... ((the rest of this message to be completed))
Group format Error:
OS File : BOOKING.TEXTS
Group# : 00000932
Record length incorrect or frame linkage error.

== Cause ==
Rare but nasty problem on server 99% caused by power failure, killing NEOSYS or server hardware or operating system failure.

*Did somebody kill NEOSYS processes to reboot the server or any other reason?
*Was there a power cut?
*Any expected or unexpected reboots in the server log? (see Event Viewer > System Log)
*Enough disk free space especially on servers not dedicated to neosys?

== Solution==

Depends on the cause and usually often requires aggressive interrogation to discover the cause.

== Recovery==

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

== Fixing damaged files that have no process for recreating them ==

Some damaged files can be rebuilt using NEOSYS utilities especially index files with filenames starting with !. Other damaged files can be “fixed” to prevent NEOSYS crashes as follows but some records will most probably be lost. 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

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:

F5

FIXFILE filename

(Select option 1 to update the file)

In case you get any Overwrite messages – type YES, as these are the actual files being updated.

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.

=== Using FIXFILE to repair corrupted files ===

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.

You can freely use FIXFILE on any file but it 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. Many files do not have programs to rebuild them and FIXFILE is a quick way to get the system back in operation.

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.

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.

You must prevent anyone from accessing NEOSYS while FIXFILE is running.

=== Fixing Damaged DEFINITIONS file ===

==== Non-Solution ====

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.

CAUTION: DO NOT USE FIXFILE TO TRY AND FIX THE DEFINITIONS FILE.

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.

==== Partial Restore ====

You can copy recent DEFINITIONS.LK and DEFINITIONS.OV files from the DATA\datasetcode\GENERAL folder.

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.

==== Full Restore ====

Restore from your latest backup losing all work done since that time and date.

=== Preventing users from accessing NEOSYS in order to do maintenance or repairs ===

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

# Stop the autostart program/script
# Put a file called NET.CFG with a single line saying AUTOSTART=NO in the neosys\neosys folder
# Stop the IIS server
# Stop/Pause the particular web in question

== Fixing damaged file that have a process to recreate them ==

ADS file can be recreated with F5 CREATEADS

ANALYSIS file can be recreated with F5 CREATEANALYSIS

== Fixing damaged index files (names starting with !) ==

Whilst backing up or using NEOSYS the following error message might appear:

"A Damaged file has been found.....
Group format Error:
OS File : !ADS
Group# : 00000932
Record length incorrect or frame linkage error.

#Ensure that no-one is using NEOSYS
#Log into NEOSYS on the server
#Press F5 to get a TCL command box
#Type REINDEXADS and press enter.
#Wait until it finishes and you get back to the command box
#Type OFF in the command box and you will quit NEOSYS.

The LISTS, LOCKS and !INDEXING files are automatically checked for corruption and rebuilt when you
startup the first Neosys process, and does not require this command to be run. You should probably
also do REINDEXALL to reinstate any possibly missing index entries, but since this will take a long time
you should do this when everybody is off the system in the evening probably.

Other reindex commands are:

*REINDEXACCOUNTS recreates !ACCOUNTS and !BATCHES
*REINDEXADDRESSES
*REINDEXADS
*REINDEXBOOKINGS recreates !BOOKING.ORDERS
*REINDEXBRANDS
*REINDEXCLIENTS
*REINDEXINVS recreates !INVOICES
*REINDEXJOBS
*REINDEXMATERIALS
*REINDEXPLANS
*REINDEXPRODINVS recreates !PRODUCTION.INVOICES
*REINDEXPRODORDERS recreates !PRODUCTION.ORDERS
*REINDEXRATECARDS
*REINDEXSCHEDULES
*REINDEXSUPPLIERS
*REINDEXTIMESHEETS
*REINDEXVEHICLES

REINDEXMEDIA does all the following
*REINDEXPLANS
*REINDEXSCHEDULES
*REINDEXADS
*REINDEXMATERIALS
*REINDEXBOOKINGS

REINDEXFILES does all the following
*REINDEXCLIENTS
*REINDEXBRANDS
*REINDEXSUPPLIERS
*REINDEXVEHICLES
*REINDEXRATECARDS

REINDEXPRODUCTION does all the following
*REINDEXJOBS
*REINDEXPRODORDERS
*REINDEXPRODINVS
*REINDEXTIMESHEETS

REINDEXALL does all the following
*REINDEXMEDIA
*REINDEXPRODUCTION
*REINDEXFILES
*REINDEXINVS
*REINDEXACCOUNTS
*REINDEXADDRESSES

== Dealing with damaged files that cannot be fixed ==

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.

THIS DOES NOT RELEASE NEOSYS SUPPORT STAFF FROM THE OBLIGATION TO PROACTIVELY INFORM THE CLIENT OF MEASURES TO PREVENT THE RECURRENCE OF THE EVENT.

The following are the steps to follow:

# Ascertain the cause of the damage to the database by looking at the internal logs
# Create a new database from the damaged one as it will contain the up to date but damaged database.
# Restore the database from the backup media so that the database is in the last good known state.
# 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.
# 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.

Configuring STARTALL.cmd command to auto start all processess

2007-05-06T20:43:10Z

77.68.3.139: /* Setting up the file */

=== Setting up the file ===

Create a .cmd file with the following command lines:

start cmd /c "D:\hosts\markone\Start MARKONE.cmd"
c:\cygwin\bin\sleep 3
start cmd /c "D:\hosts\orange\Start ORANGERIE.cmd"
c:\cygwin\bin\sleep 3

The c:\cygwin\bin\sleep 3 is to give a 3 second gap between each process startup.

Likewise you can add additional lines to start up additional processes.

Incase you need to disable a process startup temporarily, instead of deleting the line, you may add the word REM (meaning REMARK) before the start of the line and the line will be ignored till such time the remark is there.

Troubleshooting NEOSYS Generally

2007-04-27T10:09:07Z

77.68.3.139:

=== Handling damaged files ===

[[Handling damaged files]]

=== Checking for corrupt database files ===

Login to NEOSYS Maintenance

Press F5

CHK.FILES

or

CHK.FILES filename

=== Troubleshooting Internet Explorer ===

[[Troubleshooting IE]]

=== Resolving slow speed ===

[[Benchmarking NEOSYS]]

=== Handling failure and warning on nightly backup alerts ===

[[Handling failure and warning messages on nightly backup alerts]]

== Resolving permissions errors while logging in ==

=== Problem ===

While logging in, you get the following error message:
[[Image:login_error_message.jpg]]

=== Solution ===

Add the internet guest account to the security list of the data folder with the default permission of list/read/write

Make sure the read&execute permission is removed
[[Image:permissions_on_data.jpg]]

== Enabling File Security option on Win XP Professional ==

=== Problem ===

In the Properties of any folders, the Security option does not show, hence you cannot modify the Read, Write options.

=== Solution ===

The solution would be to untick the 'Simple File Sharing' option from Tools > Folder Options > View:
[[Image:simplefilesharingoff.jpg]]

== B10 & B12 Errors ==

These errors are in the software and should be immediately escalated to the programmer.

== Internet Explorer Menu, View, Text Size doesnt change font size as expected ==

Cause: This is because the font size is now user definable in NEOSYS and View, Text Size does not override predefined font sizes.

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.

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.

== Error on process window "Not enough string space - Out of Memory" ==

=== Message ===

‘RTP27’ Line 1. [B29] Not enough string space – Out of Memory.

Not enough memory to execute Debugger; current program aborted.
Press any key to continue

[[Image:out_of_memory.jpg]]

=== Cause ===
Unknown perhaps related to some large document or report

=== Solution ===
Ask users for any hanging transactions.
None other than closing and starting another process

== Uploaded jpg files fail to display in internet explorer ==

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.

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.

=== Partial solution ===
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.

Configuring NEOSYS Generally

2007-04-24T09:02:01Z

77.68.3.139: /* Configuring automated emails in NEOSYS */

=== Configuring letterhead ===
[[Configuring Letterhead]]

=== Configuring fonts and colors for all users ===

Current latest version of NEOSYS software allows choice of font for all columnar reports and documents produced by NEOSYS.

The default for all NEOSYS reports and documents unless you follow this procedure is a dark and light buff yellow.

ED DEFINITIONS SYSTEM

line 46 then press Ctrl+E to edit multivalues (sublines)

mv 1: color for table column heading rows

mv 2: color for table body rows

mv 3: font

Press F9 to save, then Esc to get out of editing multivalues

Users can override the above the colors and fonts in their user details after login.

=== Changing the signatory ===

In Maintenance mode, press F5 and the following command:

ED DEFINITIONS AGENCY.PARAMS

Be careful not to insert lines except at the end. Moving other lines down will totally screw NEOSYS!

Than go to the bottom of the page (Ctrl+Page down). Once you reach at the bottom, ENTER enough times to add additional lines if required, than search for '''line 61''' (Ctrl+G) and edit the document / add this code:

 Name of General Manager General Manager 

=== Clearing files in database (done when you want to clean an old database) ===

Clear data F5 CLEAROP (only clears transactions not reference files)

Clear suppliers F5 CLEARFILE SUPPLIERS

Clear Vehicles F5 CLEARFILE VEHICLES

Flush Index F5 FLUSH.INDEX

Clear all F5 CLEARALL (rather nasty command because clears all reference files as well)

=== Configuring which days the backup will be done on ===

F5

ED DEFINITIONS BACKUP

Line 5 should a list of digits indicating desired days of week 1-7 where 1 is Monday

e.g. 23456 to backup on Mon-Fri night

NB Assuming the backups are at the default time of 2am then you must put "2"
for Monday night since it actually takes place on Tuesday at 2am.

=== Configuring email backup alerts ===

F5

ED DEFINITIONS BACKUP

You can change the email addresses and the Drive to backup.

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS BACKUP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations.

ED DOS ..\..\BACKUP.CFG

What each line does is as follows:

*backup params
*1=date last attempted
**2= not used ... was workstation for backup (blank defaults to server)
*3=min time of day for backup to start (defaults to 02:00)
*4=max time of day for backup to start (defaults to 02:05)
*5=days to do backup 1234567 1=sun NIGHT!!! EG 2AM
*2/3/4/5 could be multivalued in parallel (to be programmed)
*6=tech support email addresse(s) separated by ';'
*7=backup disk letter
*8=mv list of datasets NOT to backup (press ctrl+E)
*9=1 disable both backup and shutdown completely
*10=email addresses to send backup.zip to OR replacement for 6 if 6 missing
*backups@neosys.com is excluded in NET from backup.zip recipients
*11=1=suppress backup but do shutdown (testdata)

==== Excluding TEST, historical or other databases from backing up every night ====
Database backup is automatically skipped if the last four characters of the database code are TEST or the word TESTING or TRAINING is found in the database name or if the database code is found in the list of database codes (ctrl+e) not to be backed up in line 8 of BACKUP.CFG or if line 11 is set to 1.

==== Backing up multiple databases on one installation ====
There is no way to backup multiple databases on the same night but you can arrange for one database to be backed up on days 1357 and another on days 246. Three databases could be backed up every third day eg the first database on days 147, the second on 25 and the third on days 36.

Assuming backups are done at 2am then the day 1 backup is done at 2am on Monday night and therefore is the backup of work done on '''Sunday'''. If the working week starts on Sunday then the above numbers should be reduced by 1. If on Saturday then by 2. Reducing day 1 by 2 days makes it day 6. The reason is that backup over the weekend is less important and therefore the extra backup for the first database should be aligned on a less important day of the week.

=== Configuring automated emails in NEOSYS ===

Login to NEOSYS Maintenance

Press F5

ED DEFINITIONS SMTP.CFG

and press enter (F9/Esc to save and exit)

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS SMTP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations. Available in NEOSYS versions dated 24/4/2007 onwards.

ED DOS ..\..\SMTP.CFG

Lines are fixed (only first two lines are required)

#sender email (must be acceptable to the smtp host name following)
#smtp host name (domain name or ip number)
#smtp port number (blank for 25)
#smtp timeout in seconds (blank for 60?)
#smto use ssl (1=yes, blank for no) ssl is secure connection
#smtp authorization type ()
#smtp user
#smtp pass

Typical configuration

in DOS SMTP.CFG

clientname@neosys.com
mailout.neosys.com
2500

Note that neosys mail server will accept email from anywhere as long as the sender email is @neosys.com

=== Copying a single record from one database to another ===

You need to know the file name and record key of the record to be copied.

In this case the file is DEFINITIONS and the key is AGENCY.PARAMS

You can invent any old style 8.3 filename instead of C:\AGP.DAT in the following example

On the source computer:

F5
COPY DEFINITIONS AGENCY.PARAMS TO: (DOS C:\AGP.DAT)

On the target computer:

F5
COPY DOS C:\AGP.DAT (ON) TO: (DEFINITIONS AGENCY.PARAMS)

The (O) option is required to force overwrite of the existing

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.

== NEOSYS Authorisation File ==

=== Preventing users from assigning their own passwords ===

The task AUTHORISATION INVENT OWN PASSWORDS should always have the lock NEOSYS to prevent users from creating their own passwords. Most users create unsafe passwords given the choice.

People nearly always ask to give their own passwords but you should tell them that NEOSYS always assigns random passwords for security reasons. It is not worth arguing and discussing the point with most people since they don't usually grasp the importance and soon learn their NEOSYS password anyway.

NEOSYS support staff who login as NEOSYS are still authorised to create their own passwords but it is better not to leak this information to clients immediately since people will grasp on to it and be disappointed or even offended that you are not granting this privilege to them.

Unfortunately there is no general way for people to change their own passwords at the moment. Only the few people who have access to the Support Menu and Authorisation File can do it. Changing your own passwords should be on the NEOSYS Help menu so everybody can do it.

== Configuring payment instruction text ==

NEOSYS picks up the first available payment instructions from the following locations and ignores any instructions in the later files.

#Client file
#Currency file
#Company file
#AGENCY.PARAMS field 38

If, following the normal rules, the payment instructions are "NONE" then the instructions are blank.

There is a manually edited flag in the company file on one NEOSYS client (cannot remember which) which makes the company file payment instructions take precedence over any currency file payment instructions. This may be added to the Client File u/i as "For all currencies"

The usual way of configuring payment instructions is to put it in the Company file under Finance. However this does not allow for different payment instructions per currency. If you put the payment instructions in the currency file however, then these instructions apply to all companies unless you edit the manual flag in the company record to say that the company file instructions take precedence over. There is no way at the moment in NEOSYS to have different instructions per company AND per currency.

Tip: Since the rules of getting payment instructions are not simple, if you are *changing* payment instructions, locate where the old instructions are and simply change them without worrying about the rules.

Configuring NEOSYS Generally

2007-04-24T08:10:55Z

77.68.3.139: /* Excluding TEST datasets from backing up every night */

=== Configuring letterhead ===
[[Configuring Letterhead]]

=== Configuring fonts and colors for all users ===

Current latest version of NEOSYS software allows choice of font for all columnar reports and documents produced by NEOSYS.

The default for all NEOSYS reports and documents unless you follow this procedure is a dark and light buff yellow.

ED DEFINITIONS SYSTEM

line 46 then press Ctrl+E to edit multivalues (sublines)

mv 1: color for table column heading rows

mv 2: color for table body rows

mv 3: font

Press F9 to save, then Esc to get out of editing multivalues

Users can override the above the colors and fonts in their user details after login.

=== Changing the signatory ===

In Maintenance mode, press F5 and the following command:

ED DEFINITIONS AGENCY.PARAMS

Be careful not to insert lines except at the end. Moving other lines down will totally screw NEOSYS!

Than go to the bottom of the page (Ctrl+Page down). Once you reach at the bottom, ENTER enough times to add additional lines if required, than search for '''line 61''' (Ctrl+G) and edit the document / add this code:

 Name of General Manager General Manager 

=== Clearing files in database (done when you want to clean an old database) ===

Clear data F5 CLEAROP (only clears transactions not reference files)

Clear suppliers F5 CLEARFILE SUPPLIERS

Clear Vehicles F5 CLEARFILE VEHICLES

Flush Index F5 FLUSH.INDEX

Clear all F5 CLEARALL (rather nasty command because clears all reference files as well)

=== Configuring which days the backup will be done on ===

F5

ED DEFINITIONS BACKUP

Line 5 should a list of digits indicating desired days of week 1-7 where 1 is Monday

e.g. 23456 to backup on Mon-Fri night

NB Assuming the backups are at the default time of 2am then you must put "2"
for Monday night since it actually takes place on Tuesday at 2am.

=== Configuring email backup alerts ===

F5

ED DEFINITIONS BACKUP

You can change the email addresses and the Drive to backup.

Any lines in the following overrides the above and affects all datasets in the current neosys installation. Useful to control many datasets.

ED DOS BACKUP.CFG

Any any lines in the following overrides the above and affects all datasets in parallel neosys installations in the same folder. Useful to control many installations.

ED DOS ..\..\BACKUP.CFG

What each line does is as follows:

*backup params
*1=date last attempted
**2= not used ... was workstation for backup (blank defaults to server)
*3=min time of day for backup to start (defaults to 02:00)
*4=max time of day for backup to start (defaults to 02:05)
*5=days to do backup 1234567 1=sun NIGHT!!! EG 2AM
*2/3/4/5 could be multivalued in parallel (to be programmed)
*6=tech support email addresse(s) separated by ';'
*7=backup disk letter
*8=mv list of datasets NOT to backup (press ctrl+E)
*9=1 disable both backup and shutdown completely
*10=email addresses to send backup.zip to OR replacement for 6 if 6 missing
*backups@neosys.com is excluded in NET from backup.zip recipients
*11=1=suppress backup but do shutdown (testdata)

==== Excluding TEST, historical or other databases from backing up every night ====
Database backup is automatically skipped if the last four characters of the database code are TEST or the word TESTING or TRAINING is found in the database name or if the database code is found in the list of database codes (ctrl+e) not to be backed up in line 8 of BACKUP.CFG or if line 11 is set to 1.

==== Backing up multiple databases on one installation ====
There is no way to backup multiple databases on the same night but you can arrange for one database to be backed up on days 1357 and another on days 246. Three databases could be backed up every third day eg the first database on days 147, the second on 25 and the third on days 36.

Assuming backups are done at 2am then the day 1 backup is done at 2am on Monday night and therefore is the backup of work done on '''Sunday'''. If the working week starts on Sunday then the above numbers should be reduced by 1. If on Saturday then by 2. Reducing day 1 by 2 days makes it day 6. The reason is that backup over the weekend is less important and therefore the extra backup for the first database should be aligned on a less important day of the week.

=== Configuring automated emails in NEOSYS ===

Login to NEOSYS Maintenance

Press F5

ED DOS SMTP.CFG

and press enter (F9/Esc to save and exit)

Lines are fixed (only first two lines are required)

#sender email (must be acceptable to the smtp host name following)
#smtp host name (domain name or ip number)
#smtp port number (blank for 25)
#smtp timeout in seconds (blank for 60?)
#smto use ssl (1=yes, blank for no) ssl is secure connection
#smtp authorization type ()
#smtp user
#smtp pass

=== Copying a single record from one database to another ===

You need to know the file name and record key of the record to be copied.

In this case the file is DEFINITIONS and the key is AGENCY.PARAMS

You can invent any old style 8.3 filename instead of C:\AGP.DAT in the following example

On the source computer:

F5
COPY DEFINITIONS AGENCY.PARAMS TO: (DOS C:\AGP.DAT)

On the target computer:

F5
COPY DOS C:\AGP.DAT (ON) TO: (DEFINITIONS AGENCY.PARAMS)

The (O) option is required to force overwrite of the existing

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.

== NEOSYS Authorisation File ==

=== Preventing users from assigning their own passwords ===

The task AUTHORISATION INVENT OWN PASSWORDS should always have the lock NEOSYS to prevent users from creating their own passwords. Most users create unsafe passwords given the choice.

People nearly always ask to give their own passwords but you should tell them that NEOSYS always assigns random passwords for security reasons. It is not worth arguing and discussing the point with most people since they don't usually grasp the importance and soon learn their NEOSYS password anyway.

NEOSYS support staff who login as NEOSYS are still authorised to create their own passwords but it is better not to leak this information to clients immediately since people will grasp on to it and be disappointed or even offended that you are not granting this privilege to them.

Unfortunately there is no general way for people to change their own passwords at the moment. Only the few people who have access to the Support Menu and Authorisation File can do it. Changing your own passwords should be on the NEOSYS Help menu so everybody can do it.

== Configuring payment instruction text ==

NEOSYS picks up the first available payment instructions from the following locations and ignores any instructions in the later files.

#Client file
#Currency file
#Company file
#AGENCY.PARAMS field 38

If, following the normal rules, the payment instructions are "NONE" then the instructions are blank.

There is a manually edited flag in the company file on one NEOSYS client (cannot remember which) which makes the company file payment instructions take precedence over any currency file payment instructions. This may be added to the Client File u/i as "For all currencies"

The usual way of configuring payment instructions is to put it in the Company file under Finance. However this does not allow for different payment instructions per currency. If you put the payment instructions in the currency file however, then these instructions apply to all companies unless you edit the manual flag in the company record to say that the company file instructions take precedence over. There is no way at the moment in NEOSYS to have different instructions per company AND per currency.

Tip: Since the rules of getting payment instructions are not simple, if you are *changing* payment instructions, locate where the old instructions are and simply change them without worrying about the rules.

Troubleshooting NEOSYS Generally

2007-04-23T14:51:22Z

77.68.3.139: