Troubleshooting NEOSYS Generally - Revision history

Arvind at 08:38, 9 September 2022

2022-09-09T08:38:45Z

@@ Line 52: / Line 52: @@
 #Press F8 or click Close - to refresh the form
 #The form should now be filled in correctly including any hidden fields.
 ==[[Administering_NEOSYS_Server#Clearing_File_Locks| Troubleshooting "Document is being updated" message]]==

Gregory: /* Fixing "UNABLE TO OPEN BOOT MEDIA MAP" error */ (minor improvement to add headings for a section's cause and solution.

2021-02-21T07:28:46Z

Fixing "UNABLE TO OPEN BOOT MEDIA MAP" error: (minor improvement to add headings for a section's cause and solution.

← Older revision		Revision as of 07:28, 21 February 2021
Line 852:		Line 852:
	Unable to open boot media map.		Unable to open boot media map.

	Cause:		====Cause====

	AREV.EXE is unable to access the REVMEDIA.LK file.		AREV.EXE is unable to access the REVMEDIA.LK file.
Line 858:		Line 858:
	Possibly due to windows permissions problems. For example after using CYGWIN RSYNC without the --no-perms option.		Possibly due to windows permissions problems. For example after using CYGWIN RSYNC without the --no-perms option.

	Solution:		====Solution====

	If cygwin rsync has screwed up the permissions you can reset the permissions for all files on the D: disk		If cygwin rsync has screwed up the permissions you can reset the permissions for all files on the D: disk

Gregory: /* Fixing issue where NEOSYS processes do not start-up at all or start-up and close immediately */

2021-02-09T08:11:34Z

Fixing issue where NEOSYS processes do not start-up at all or start-up and close immediately

← Older revision		Revision as of 08:11, 9 February 2021
Line 872:		Line 872:
	[[Image:Unableopenbootmediamap.png]]		[[Image:Unableopenbootmediamap.png]]

	===~~Fixing issue where~~ NEOSYS processes do not start-up at all or start-up and close immediately===		===NEOSYS Maintenance or processes do not start-up at all or start-up and close immediately===

	~~Fixing~~ issue ~~where NEOSYS processes do not start-up at all or start-up and close immediately.~~		To fix the issue try:

	#Check if a file with the name global.end exists in the root directory of the NEOSYS installation. Eg D:\global.end . If you find such a file, rename it to global.end.temp - for more information on global.end and what it does, refer to [[Administering_NEOSYS_Server#Closing_NEOSYS_Services\|Closing NEOSYS Services]]		#Check if a file with the name global.end exists in the root directory of the NEOSYS installation. Eg D:\global.end . If you find such a file, rename it to global.end.temp - for more information on global.end and what it does, refer to [[Administering_NEOSYS_Server#Closing_NEOSYS_Services\|Closing NEOSYS Services]]
	#~~If the above didn't fix the problem and NEOSYS still does not start, do a windows search~~ for the entire NEOSYS folder for *.end (i.e. any file ending with .end extension). You may find a (databasecode).end file in D:\neosys\neosys folder which is created by the NEOSYS program during backup at 1 am and later on removed automatically. In this case NEOSYS program might have crashed during the backup and left this file behind. (databasecode).end files prevent other other NEOSYS processes starting up on the database while exclusive processes (like backup) are being done.		#Search for the entire NEOSYS folder for *.end (i.e. any file ending with .end extension). You may find a (databasecode).end file in D:\neosys\neosys folder which is created by the NEOSYS program during backup at 1 am and later on removed automatically. In this case NEOSYS program might have crashed during the backup and left this file behind. (databasecode).end files prevent other other NEOSYS processes starting up on the database while exclusive processes (like backup) are being done.
			#If on Windows 10, check 16 bit Legacy mode is active. [[Configuring_NEOSYS_on_Windows_10#Get_NEOSYS_process_running \| Configuring 16bit Virtual Memory Legacy mode]]
	~~Or try:~~ Delete the read-only file REVBOOT file (under d:/neosys/neosys folder). REVBOOT file is recreated when you start maintenance mode.		#Delete the read-only file REVBOOT file (under d:/neosys/neosys folder). REVBOOT file is recreated when you start maintenance mode.

	In case the above didn't fix the problem then escalate to the programmer immediately.		In case the above didn't fix the problem then escalate to the programmer immediately.

Arvind: /* Solving "Control Record" error in maintenance mode or GUI */

2020-02-02T11:19:43Z

Solving "Control Record" error in maintenance mode or GUI

← Older revision		Revision as of 11:19, 2 February 2020
Line 1,015:		Line 1,015:

	====Problem====		====Problem====
	*~~If processes doesn~~'t start after you log into maintenance mode.
	*When saving various files in GUI such as BRANDS.		*Processes don't start after you log into maintenance mode and get the error message shown above.
			*When saving various files in GUI such as BRANDS you get the error message shown above.

	====Cause====		====Cause====

	What is "QUICKDEX"? - [[~~Troubleshooting_NEOSYS_Generally~~#~~Solving_~~.~~22Control_Record~~.~~22_error_in_maintenance_mode~~ \| Installing "QUICKDEX" on some files]]		What is "QUICKDEX"? - [[Troubleshooting NEOSYS Generally#Installing .22QUICKDEX.22 on some files\|Installing "QUICKDEX" on some files]]

	For example CURRENCIES file average key size, is 13. This means that the maximum number of records in the file would be 65535/(13+1) = 4681.		For example, for the CURRENCIES file average key size is 13. This means that the maximum number of records in the file would be 65535/(13+1) = 4681.
	If the limit is reached then the error described here is thrown. (~~Generally~~ there would be more than a few thousand records in the file.)
			If the limit is reached then the error described here is thrown (generally there would be more than a few thousand records in the file).

	====Solution====		====Solution====
	QUICKDEX needs to be ~~uninstalled on~~ the appropriate file.		QUICKDEX needs to be removed from the appropriate file. The error message does not mention the file name in which the problem exists, so you are left guessing which file needs QUICKDEX removing.
	~~Which~~ file needs QUICKDEX ~~uninstalled?~~

	~~1. The error message does not mention the file name, but it~~ may be obvious which file, from the operation being done. (~~For~~ example in the problem ~~case of~~ saving a file)		It may be obvious which file, from the operation being done (for example if the problem occurs when saving a file). Otherwise you have to search for the file, by checking which have oversized control records (%RECORDS%) and try uninstalling the most likely first.

	~~Otherwise~~ you ~~have to search for the file, by checking which have~~ oversized ~~control records (~~%RECORDS%) and ~~try uninstalling~~ the ~~most likely first~~.		* In recent versions of NEOSYS you can find all files with oversized "%RECORDS%" control records as follows and sort by size by clicking on the column heading.

	~~2. In recent versions of NEOSYS you can find all files with oversized "%RECORDS%" control records as follows and sort by size by clicking on the column heading.~~
	LIST FILES WITH QUICKDEX_SIZE		LIST FILES WITH QUICKDEX_SIZE
	~~3.In older versions you can get a list of all files with QUICKDEX installed and laboriously check each one by one using ED filename %RECORDS% and F6, Statistics~~

			* In older versions you can get a list of all files with QUICKDEX installed and laboriously check each one by one using

	~~To view a QUICKDEX record for a file:~~
	ED filename %RECORDS%		ED filename %RECORDS%

			and then F6, Statistics


Line 1,074:		Line 1,075:

	[[File:Record4.jpg]]		[[File:Record4.jpg]]


	'''5.'''Restart NEOSYS to see if the problem has been solved		'''5.'''Restart NEOSYS to see if the problem has been solved


			Below is an example of removing QUICKDEX from the BRANDS file, to solve the problem of error appearing when saving the client and brand file.
			Media Production Finance Ma╔═════════════════Dictionary═════════════════╗
			▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒║ ║▒
			▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒║ File name BRANDS ║▒
			▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒║ Field name ║▒
			▒╒═══════════════════════════════║ ║▒
			▒│ ║ Dict type ║▒
			▒│ :dict brands ║ Single/Multi ║▒
			▒│ ║ Data type ║▒
			▒╘═════════════════╔═[B202]══════════════════════════════════╗ ║▒
			▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒║ ║ ║▒
			▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒║ "BRANDS" has ║ ║▒
			▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒║ "QUICKDEX" installed. ║part ║▒
			▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒║ ║ ║▒
			▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒║ Do you want to remove "QUICKDEX"? [Y/N] ║ ║▒
			▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒║ ║ ║▒
			▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒║<Y >║ ║▒
			▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒╚═════════════════════════════════════════╝length ║▒
			▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒║ Description ║▒
			▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒║ ║▒
			▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒║ ║▒
			▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒╚════════════════════════════════════════════╝▒
			<br />
	==Solving “page not found” or "HTTP Error 404.3 - Not Found" when downloading some file types after uploading them successfully==		==Solving “page not found” or "HTTP Error 404.3 - Not Found" when downloading some file types after uploading them successfully==

Gregory: /* Problem */

2020-02-02T10:50:20Z

Problem

← Older revision		Revision as of 10:50, 2 February 2020
Line 1,016:		Line 1,016:
	====Problem====		====Problem====
	*If processes doesn't start after you log into maintenance mode.		*If processes doesn't start after you log into maintenance mode.
	*When saving various files in GUI such as BRANDS ~~or DEFINITIONS~~.		*When saving various files in GUI such as BRANDS.

	====Cause====		====Cause====

Gregory: /* Installing "QUICKDEX" on some files */

2020-02-02T10:40:33Z

Installing "QUICKDEX" on some files

← Older revision		Revision as of 10:40, 2 February 2020
Line 1,233:		Line 1,233:
	==Installing "QUICKDEX" on some files==		==Installing "QUICKDEX" on some files==
	"Quickdex" is a type of index that keeps an alphabetical order on small files, files such as CURRENCIES or SUPPLIERS.		"Quickdex" is a type of index that keeps an alphabetical order on small files, files such as CURRENCIES or SUPPLIERS.
	~~Generally there would be more than a few thousand records in the file.~~		In some maintenance procedures you may be asked to "install Quickdex" to, for example the UNITS file.

	~~For example the CURRENCIES file average key size, is 13. This means that the maximum number of records in the file would be 65535/(13+1) = 4681.~~
	~~If the limit is reached then the error described here is thrown.~~

	~~[[Troubleshooting_NEOSYS_Generally#Solving_.22Control_Record.22_error_in_maintenance_mode \| Solving Control Record Error]]~~

	In some maintenance procedures you may be asked to "install Quickdex".


	~~For~~ example ~~to add a quickdex to~~ the UNITS file.

	Maintenance mode press F5		Maintenance mode press F5

Gregory: /* Solving "Control Record" error in maintenance mode or GUI */

2020-02-02T10:40:28Z

Solving "Control Record" error in maintenance mode or GUI

← Older revision		Revision as of 10:40, 2 February 2020
Line 1,018:		Line 1,018:
	*When saving various files in GUI such as BRANDS or DEFINITIONS.		*When saving various files in GUI such as BRANDS or DEFINITIONS.

	~~QUICKDEX needs to be uninstalled on the appropriate file.~~		====Cause====

	What is "QUICKDEX"? - [[Troubleshooting_NEOSYS_Generally#Solving_.22Control_Record.22_error_in_maintenance_mode \| Installing "QUICKDEX" on some files]]		What is "QUICKDEX"? - [[Troubleshooting_NEOSYS_Generally#Solving_.22Control_Record.22_error_in_maintenance_mode \| Installing "QUICKDEX" on some files]]

			For example CURRENCIES file average key size, is 13. This means that the maximum number of records in the file would be 65535/(13+1) = 4681.
			If the limit is reached then the error described here is thrown. (Generally there would be more than a few thousand records in the file.)

	====Solution====		====Solution====
			QUICKDEX needs to be uninstalled on the appropriate file.
	Which file needs QUICKDEX uninstalled?		Which file needs QUICKDEX uninstalled?

Line 1,032:		Line 1,036:
	LIST FILES WITH QUICKDEX_SIZE		LIST FILES WITH QUICKDEX_SIZE
	3.In older versions you can get a list of all files with QUICKDEX installed and laboriously check each one by one using ED filename %RECORDS% and F6, Statistics		3.In older versions you can get a list of all files with QUICKDEX installed and laboriously check each one by one using ED filename %RECORDS% and F6, Statistics


			To view a QUICKDEX record for a file:
			ED filename %RECORDS%

Gregory: /* Solving "Control Record" error in maintenance mode */

2020-02-02T10:08:55Z

Solving "Control Record" error in maintenance mode

← Older revision		Revision as of 10:08, 2 February 2020
Line 1,003:		Line 1,003:
	In case the above didn't fix the problem then escalate to the programmer immediately.		In case the above didn't fix the problem then escalate to the programmer immediately.

	===Solving "Control Record" error in maintenance mode===		===Solving "Control Record" error in maintenance mode or GUI===

	~~If processes dont start after you log into maintenance mode and you get an error message~~
	<pre>		<pre>
	╔════[FS152]═══════════════════════════════════════╗		╔════[FS152]═══════════════════════════════════════╗
Line 1,015:		Line 1,013:
	╚══════════════════════════════════════════════════╝		╚══════════════════════════════════════════════════╝
	</pre>		</pre>
	~~[[File:Record1.jpg]]~~

	'''1'''. Press space to get rid of the error message and you should then get this menu		====Problem====
			*If processes doesn't start after you log into maintenance mode.
			*When saving various files in GUI such as BRANDS or DEFINITIONS.

			QUICKDEX needs to be uninstalled on the appropriate file.

			What is "QUICKDEX"? - [[Troubleshooting_NEOSYS_Generally#Solving_.22Control_Record.22_error_in_maintenance_mode \| Installing "QUICKDEX" on some files]]

			====Solution====
			Which file needs QUICKDEX uninstalled?

			1. The error message does not mention the file name, but it may be obvious which file, from the operation being done. (For example in the problem case of saving a file)

			Otherwise you have to search for the file, by checking which have oversized control records (%RECORDS%) and try uninstalling the most likely first.

			2. In recent versions of NEOSYS you can find all files with oversized "%RECORDS%" control records as follows and sort by size by clicking on the column heading.
			LIST FILES WITH QUICKDEX_SIZE
			3.In older versions you can get a list of all files with QUICKDEX installed and laboriously check each one by one using ED filename %RECORDS% and F6, Statistics


			'''1'''. Press space to get rid of the error message and you should then get this menu. (Do only if error from Maintenance)

	[[File:Record2.jpg]]		[[File:Record2.jpg]]

	~~'''2'''. Press F5 and run this command (case sensitive)~~

	DICT ~~DEFINITIONS~~		'''2'''. Press F5 and run this command. (If error from Maintenance use "DEFINITIONS" as filename) (case sensitive)

			DICT filename

	or Press Alt+S and run this command (case sensitive)		or Press Alt+S and run this command (case sensitive)

Gregory: /* Installing "QUICKDEX" on some files */

2020-02-02T09:04:04Z

Installing "QUICKDEX" on some files

← Older revision		Revision as of 09:04, 2 February 2020
Line 1,206:		Line 1,206:

	==Installing "QUICKDEX" on some files==		==Installing "QUICKDEX" on some files==
	"Quickdex" is a type of index that keeps an alphabetical order on small files, files such as ~~CURRENIES~~ or SUPPLIERS.		"Quickdex" is a type of index that keeps an alphabetical order on small files, files such as CURRENCIES or SUPPLIERS.
	Generally there would be more than a few thousand records in the file.		Generally there would be more than a few thousand records in the file.

	For example the CURRENCIES file average key size, is 13. This means that the maximum number of records in the file would be 65535/(13+1) = 4681.		For example the CURRENCIES file average key size, is 13. This means that the maximum number of records in the file would be 65535/(13+1) = 4681.
	If the limit is reached then the error described here is thrown. ([[~~index.php/~~Troubleshooting_NEOSYS_Generally#Solving_.22Control_Record.22_error_in_maintenance_mode]]		If the limit is reached then the error described here is thrown.

			[[Troubleshooting_NEOSYS_Generally#Solving_.22Control_Record.22_error_in_maintenance_mode \| Solving Control Record Error]]

	In some maintenance procedures you may be asked to "install Quickdex".		In some maintenance procedures you may be asked to "install Quickdex".

Gregory: /* Installing "QUICKDEX" on some files */

2020-02-02T09:02:21Z

Installing "QUICKDEX" on some files

← Older revision		Revision as of 09:02, 2 February 2020
Line 1,206:		Line 1,206:

	==Installing "QUICKDEX" on some files==		==Installing "QUICKDEX" on some files==
	"Quickdex" is a type of index that keeps an alphabetical order on small files. In some maintenance procedures you may be asked to "install Quickdex".		"Quickdex" is a type of index that keeps an alphabetical order on small files, files such as CURRENIES or SUPPLIERS.
			Generally there would be more than a few thousand records in the file.
			For example the CURRENCIES file average key size, is 13. This means that the maximum number of records in the file would be 65535/(13+1) = 4681.
			If the limit is reached then the error described here is thrown. ([[index.php/Troubleshooting_NEOSYS_Generally#Solving_.22Control_Record.22_error_in_maintenance_mode]]

			In some maintenance procedures you may be asked to "install Quickdex".


	For example to add a quickdex to the UNITS file.		For example to add a quickdex to the UNITS file.