Configuring MAS90 and Sage100 - Revision history

Nenjin: /* MAS90, ITrack and Crystal Reports */

2016-08-30T22:19:46Z

MAS90, ITrack and Crystal Reports

← Older revision		Revision as of 17:19, 30 August 2016
Line 88:		Line 88:
	#Delete the entire ITrack Enterprise Program folder and registry entries. (This isn't strictly necessary but I have had the best results with this process starting from a clean slate, and that means a full ITrack Enterprise re-install. You may be able to get away with just uninstalling Crystal 11 Test.)		#Delete the entire ITrack Enterprise Program folder and registry entries. (This isn't strictly necessary but I have had the best results with this process starting from a clean slate, and that means a full ITrack Enterprise re-install. You may be able to get away with just uninstalling Crystal 11 Test.)
	#Uninstall and/or delete the MAS90 Program.		#Uninstall and/or delete the MAS90 Program.
	#Delete the "Business Objects Folder" (Probably in Program Files (x86)		#Delete the "Business Objects Folder" (Probably in C:/Program Files (x86))
	#Uninstall Crystal 11 Test.		#Uninstall Crystal 11 Test.
	#Use Regedit and delete the SOFTWARE/Business Objects folder. (May reside in the WOW6432Node.)		#Use Regedit and delete the SOFTWARE/Business Objects folder. (May reside in the WOW6432Node.)

Nenjin: /* MAS90, ITrack and Crystal Reports */

2016-08-30T22:18:42Z

MAS90, ITrack and Crystal Reports

← Older revision		Revision as of 17:18, 30 August 2016
Line 84:		Line 84:
	#That's it! It should work!		#That's it! It should work!

	MAS90 and ITrack should both be able to print and preview without issues. If ITrack or MAS90 throw errors on print or preview there was a problem. Uninstall/delete ~~everything~~ (~~MAS90, ITrack,~~ Crystal 11 Test.~~) ALSO run regedit~~ and delete the SOFTWARE/Business Objects ~~Folder~~.		MAS90 and ITrack should both be able to print and preview without issues. If ITrack or MAS90 throw errors on print or preview there was a problem. If this is the case you should:

			#Delete the entire ITrack Enterprise Program folder and registry entries. (This isn't strictly necessary but I have had the best results with this process starting from a clean slate, and that means a full ITrack Enterprise re-install. You may be able to get away with just uninstalling Crystal 11 Test.)
			#Uninstall and/or delete the MAS90 Program.
			#Delete the "Business Objects Folder" (Probably in Program Files (x86)
			#Uninstall Crystal 11 Test.
			#Use Regedit and delete the SOFTWARE/Business Objects folder. (May reside in the WOW6432Node.)

	Then try the process from the top again.		Then try the process from the top again.

Nenjin: /* MAS90, ITrack and Crystal Reports */

2016-04-06T14:24:13Z

MAS90, ITrack and Crystal Reports

← Older revision		Revision as of 09:24, 6 April 2016
Line 94:		Line 94:
	'''Note 3''': Virtually any application that uses Crystal can break printing compatibility. When Wheeler got this working, it was only with MAS90 and ITrack present. If you receive an error message during MAS90 installation that refers to "craxdrt.dll", chances are there is another piece of software on the system that is causing a conflict. There is no current solution to that problem, as we do not have the resources or knowledge to fix the compatibility issue. We only support fixing this when it is just ITrack and MAS90 on a workstation.		'''Note 3''': Virtually any application that uses Crystal can break printing compatibility. When Wheeler got this working, it was only with MAS90 and ITrack present. If you receive an error message during MAS90 installation that refers to "craxdrt.dll", chances are there is another piece of software on the system that is causing a conflict. There is no current solution to that problem, as we do not have the resources or knowledge to fix the compatibility issue. We only support fixing this when it is just ITrack and MAS90 on a workstation.

	List of programs known to break compatibility:		List of programs known to or which may break compatibility:
	#~~Pending~~		#Infor Visual 8.0
			#Infor Visual CRM 8.0
			#Team Developer 6.2

	[[Category:Integrations]]		[[Category:Integrations]]

Nenjin: /* MAS90, ITrack and Crystal Reports */

2016-04-05T21:41:33Z

MAS90, ITrack and Crystal Reports

← Older revision		Revision as of 16:41, 5 April 2016
Line 81:		Line 81:
	#Run the ITrack Enterprise Installer		#Run the ITrack Enterprise Installer
	#Make sure that "Printing Support Options" is checked AND "Quickbooks Support" is checked.		#Make sure that "Printing Support Options" is checked AND "Quickbooks Support" is checked.
	#Run the installer for MAS90. ~~Nothing special needs~~ to ~~be done here~~.		#Run the installer for MAS90. See the above section for how to do this correctly.
	#That's it! It should work!		#That's it! It should work!

Nenjin: /* MAS90, ITrack and Crystal Reports */

2016-04-05T21:39:27Z

MAS90, ITrack and Crystal Reports

← Older revision		Revision as of 16:39, 5 April 2016
Line 93:		Line 93:

	'''Note 3''': Virtually any application that uses Crystal can break printing compatibility. When Wheeler got this working, it was only with MAS90 and ITrack present. If you receive an error message during MAS90 installation that refers to "craxdrt.dll", chances are there is another piece of software on the system that is causing a conflict. There is no current solution to that problem, as we do not have the resources or knowledge to fix the compatibility issue. We only support fixing this when it is just ITrack and MAS90 on a workstation.		'''Note 3''': Virtually any application that uses Crystal can break printing compatibility. When Wheeler got this working, it was only with MAS90 and ITrack present. If you receive an error message during MAS90 installation that refers to "craxdrt.dll", chances are there is another piece of software on the system that is causing a conflict. There is no current solution to that problem, as we do not have the resources or knowledge to fix the compatibility issue. We only support fixing this when it is just ITrack and MAS90 on a workstation.

			List of programs known to break compatibility:
			#Pending

	[[Category:Integrations]]		[[Category:Integrations]]

Nenjin: /* Installing MAS90 At Valley Truck Parts */

2016-04-05T21:36:13Z

Installing MAS90 At Valley Truck Parts

← Older revision		Revision as of 16:36, 5 April 2016
Line 69:		Line 69:
	#Make sure the workstation has a mapped network drive pointed to M:/MAS90. Someone at Valley should be capable of setting that up.		#Make sure the workstation has a mapped network drive pointed to M:/MAS90. Someone at Valley should be capable of setting that up.
	#When you go to start the installation, navigate to M:/MAS90/Wksetup folder.		#When you go to start the installation, navigate to M:/MAS90/Wksetup folder.
	#Run ~~Wkstep~~.exe.		#Run Wksetup.exe.
	#Do not run AUTORUN.exe! Even though MAS90 will install it will not function properly, and you'll have wasted a bunch of time!		#Do not run AUTORUN.exe! Even though MAS90 will install and even launch using this installation method, it will not function properly and will have to be uninstalled, and you'll have wasted a bunch of time!
	#Early on in the installation process you will probably see a message like "Setup could not verify the presence of MDAC 2.7 or 2.8 on this system." That is normal and does not affect the installation process.		#Early on in the installation process you will probably see a setup message like "Setup could not verify the presence of MDAC 2.7 or 2.8 on this system." That is normal and does not affect the installation process.
	#If during the installation process MAS90 prompts you to specify an installation directory, you've done it wrong. Done correctly the installer does not ask for an installation location.		#If during the installation process MAS90 prompts you to specify an installation directory, you've done it wrong. Done correctly the installer does not ask for an installation location and skips that part of the installation process.
	#That's all that should need to be done!		#That's all that should need to be done!

Nenjin at 21:34, 5 April 2016

2016-04-05T21:34:01Z

← Older revision		Revision as of 16:34, 5 April 2016
Line 65:		Line 65:
	# Choose 'Add Task to Menu', pick the job name of 'ISoft GL Import', set the Role to Default, and then Finish.		# Choose 'Add Task to Menu', pick the job name of 'ISoft GL Import', set the Role to Default, and then Finish.

	== ~~Install~~ MAS90 At Valley Truck Parts ==		== Installing MAS90 At Valley Truck Parts ==
	Valley installs MAS90 as a distributed client. Essentially that means it is both installed from and installed to a network path. If someone from Valley calls and asks for us to help install MAS90, do the following things:		Valley installs MAS90 as a distributed client. Essentially that means it is both installed from and installed to a network path. If someone from Valley calls and asks for us to help install MAS90, do the following things:
	#Make sure the workstation has a mapped network drive pointed to M:/MAS90. Someone at Valley should be capable of setting that up.		#Make sure the workstation has a mapped network drive pointed to M:/MAS90. Someone at Valley should be capable of setting that up.

Nenjin at 21:33, 5 April 2016

2016-04-05T21:33:47Z

← Older revision		Revision as of 16:33, 5 April 2016
Line 63:		Line 63:
	# Click the magnifying glass next to Job Name and choose ISOFT GL IMPORT		# Click the magnifying glass next to Job Name and choose ISOFT GL IMPORT
	# On the Configuration tab, click Menu		# On the Configuration tab, click Menu
	# Choose 'Add Task to Menu', pick the job name of 'ISoft GL Import', set the Role to Default, and then Finish		# Choose 'Add Task to Menu', pick the job name of 'ISoft GL Import', set the Role to Default, and then Finish.

			== Install MAS90 At Valley Truck Parts ==
			Valley installs MAS90 as a distributed client. Essentially that means it is both installed from and installed to a network path. If someone from Valley calls and asks for us to help install MAS90, do the following things:
			#Make sure the workstation has a mapped network drive pointed to M:/MAS90. Someone at Valley should be capable of setting that up.
			#When you go to start the installation, navigate to M:/MAS90/Wksetup folder.
			#Run Wkstep.exe.
			#Do not run AUTORUN.exe! Even though MAS90 will install it will not function properly, and you'll have wasted a bunch of time!
			#Early on in the installation process you will probably see a message like "Setup could not verify the presence of MDAC 2.7 or 2.8 on this system." That is normal and does not affect the installation process.
			#If during the installation process MAS90 prompts you to specify an installation directory, you've done it wrong. Done correctly the installer does not ask for an installation location.
			#That's all that should need to be done!

	== MAS90, ITrack and Crystal Reports ==		== MAS90, ITrack and Crystal Reports ==

Nenjin: /* MAS90, ITrack and Crystal Reports */

2016-04-05T19:50:32Z

MAS90, ITrack and Crystal Reports

← Older revision		Revision as of 14:50, 5 April 2016
Line 81:		Line 81:

	'''Note 2''': The Enterprise Installer will try to grab the Quickbooks SDK from our downloads space, and won't find it. You'll want to get QBSDK80.exe from dl.isoftdata.com and install it manually after the Enterprise installation has completed.		'''Note 2''': The Enterprise Installer will try to grab the Quickbooks SDK from our downloads space, and won't find it. You'll want to get QBSDK80.exe from dl.isoftdata.com and install it manually after the Enterprise installation has completed.

			'''Note 3''': Virtually any application that uses Crystal can break printing compatibility. When Wheeler got this working, it was only with MAS90 and ITrack present. If you receive an error message during MAS90 installation that refers to "craxdrt.dll", chances are there is another piece of software on the system that is causing a conflict. There is no current solution to that problem, as we do not have the resources or knowledge to fix the compatibility issue. We only support fixing this when it is just ITrack and MAS90 on a workstation.

	[[Category:Integrations]]		[[Category:Integrations]]

Nenjin: /* MAS90, ITrack and Crystal Reports */

2015-12-10T17:11:18Z

MAS90, ITrack and Crystal Reports

← Older revision		Revision as of 12:11, 10 December 2015
Line 79:		Line 79:

	'''Note''': If you're dealing with Valley and you click the Print or Preview in ITrack and it simply does NOTHING (no error, no response), you need to specify the path to Valley's report/images/attachment directories in the host.ini file for ITrack. You can find these paths in Valley's company case file.		'''Note''': If you're dealing with Valley and you click the Print or Preview in ITrack and it simply does NOTHING (no error, no response), you need to specify the path to Valley's report/images/attachment directories in the host.ini file for ITrack. You can find these paths in Valley's company case file.

			'''Note 2''': The Enterprise Installer will try to grab the Quickbooks SDK from our downloads space, and won't find it. You'll want to get QBSDK80.exe from dl.isoftdata.com and install it manually after the Enterprise installation has completed.

	[[Category:Integrations]]		[[Category:Integrations]]