EEE SQL Server Errors in Microsoft .NET Framework - Revision history

Bevan at 23:14, 8 March 2009

2009-03-08T23:14:02Z

← Older revision		Revision as of 23:14, 8 March 2009
Line 1:		Line 1:
	Created: 03 March 2009. Last Reviewed: 03 March 2009		Created: 03 March 2009. Last Reviewed: 9 March 2009


	The EEE database in SQL Server utilises a .NET assembly (DLL) to provide extended functionality which is accessible from within SQL Server. For example, to provide access to the local file system on the SQL Server from inside TSQL stored procedures.		The EEE database in SQL Server utilises a .NET assembly (DLL) to provide extended functionality which is accessible from within SQL Server. For example, to provide access to the local file system on the SQL Server from inside TSQL stored procedures.

	If the registration of this assembly with SQL Server is incorrect or inadvertantly damaged then some features of EEE may stop working. For example, inter-store transfer requests will fail, because SQL Server uses the assembly to send the stock request notification to the target store. If this happens, ~~stores~~ users will see a message to the effect that the stock transfer request was not successful.		If the registration of this assembly with SQL Server is incorrect or inadvertantly damaged then some features of EEE may stop working. For example, inter-store transfer requests will fail, because SQL Server uses the assembly to send the stock request notification to the target store. If this happens, store users will see a message to the effect that the stock transfer request was not successful.

	SQL Server will return error messages similar to:		SQL Server will return error messages similar to:
Line 27:		Line 27:
	Substitute the correct database name and file path as required.		Substitute the correct database name and file path as required.

	Note that these settings are required for each EEE database, so if ~~you have~~ a test database or separate databases for different brands/chains ~~that you operate~~, these steps should be repeated for each database. If these steps fail to resolve the problem, contact Magenta Support. Please try to have full details of error messages available.		Note that these settings are required for each EEE database, so if a server hosts a test database or separate databases for different brands/chains, these steps should be repeated for each database. If these steps fail to resolve the problem, contact Magenta Support. Please try to have full details of error messages available.

	= See Also: =		= See Also: =

Bevan at 04:21, 3 March 2009

2009-03-03T04:21:45Z

← Older revision		Revision as of 04:21, 3 March 2009
Line 23:		Line 23:
	# Run the SQL Server Command:		# Run the SQL Server Command:

	~~<tt>~~'''EXEC usp_ClrUpdate 'EEE', 'C:\EEE\SQLDLL\Magenta_SQL.DLL''''~~</tt>~~		'''EXEC usp_ClrUpdate 'EEE', 'C:\EEE\SQLDLL\Magenta_SQL.DLL''''

	Substitute the correct database name and file path as required.		Substitute the correct database name and file path as required.

Bevan at 04:20, 3 March 2009

2009-03-03T04:20:59Z

← Older revision		Revision as of 04:20, 3 March 2009
Line 23:		Line 23:
	# Run the SQL Server Command:		# Run the SQL Server Command:

	<tt>'''EXEC usp_ClrUpdate 'EEE', 'C:\EEE\SQLDLL\Magenta_SQL.DLL''''</tt>Substitute the correct database name and file path as ~~requiredNote~~ that these settings are required for each EEE database, so if you have a test database or separate databases for different brands/chains that you operate, these steps should be repeated for each database. If these steps fail to resolve the problem, contact Magenta Support. Please try to have full details of error messages available.= See Also: =		<tt>'''EXEC usp_ClrUpdate 'EEE', 'C:\EEE\SQLDLL\Magenta_SQL.DLL''''</tt>

			Substitute the correct database name and file path as required.

			Note that these settings are required for each EEE database, so if you have a test database or separate databases for different brands/chains that you operate, these steps should be repeated for each database. If these steps fail to resolve the problem, contact Magenta Support. Please try to have full details of error messages available.

			= See Also: =

Bevan at 04:19, 3 March 2009

2009-03-03T04:19:10Z

← Older revision		Revision as of 04:19, 3 March 2009
Line 21:		Line 21:
	=== To Resolve This Issue: ===		=== To Resolve This Issue: ===
	# Determine the location of Magenta_SQL.DLL. Usually this is installed in c:\EEE\SQLDLL.		# Determine the location of Magenta_SQL.DLL. Usually this is installed in c:\EEE\SQLDLL.
	# Run the SQL Server Command:~~<br/> <tt>'''EXEC usp_ClrUpdate 'EEE', 'C:\EEE\SQLDLL\Magenta_SQL.DLL''''</tt>Substitute the correct database name and file path as required.~~		# Run the SQL Server Command:
	# Note that these settings are required for each EEE database, so if you have a test database or separate databases for different brands/chains that you operate, these steps should be repeated for each database.
	~~# If these steps fail to resolve the problem, contact Magenta Support. Please try to have full details of error messages available.~~

	= See Also: =		<tt>'''EXEC usp_ClrUpdate 'EEE', 'C:\EEE\SQLDLL\Magenta_SQL.DLL''''</tt>Substitute the correct database name and file path as requiredNote that these settings are required for each EEE database, so if you have a test database or separate databases for different brands/chains that you operate, these steps should be repeated for each database. If these steps fail to resolve the problem, contact Magenta Support. Please try to have full details of error messages available.= See Also: =

Bevan at 04:16, 3 March 2009

2009-03-03T04:16:36Z

← Older revision		Revision as of 04:16, 3 March 2009
Line 21:		Line 21:
	=== To Resolve This Issue: ===		=== To Resolve This Issue: ===
	# Determine the location of Magenta_SQL.DLL. Usually this is installed in c:\EEE\SQLDLL.		# Determine the location of Magenta_SQL.DLL. Usually this is installed in c:\EEE\SQLDLL.
	# Run the SQL Server Command:		# Run the SQL Server Command:<br/> <tt>'''EXEC usp_ClrUpdate 'EEE', 'C:\EEE\SQLDLL\Magenta_SQL.DLL''''</tt>Substitute the correct database name and file path as required.
	'''EXEC usp_ClrUpdate 'EEE', 'C:\EEE\SQLDLL\Magenta_SQL.DLL''''
	</tt>Substitute the correct database name and file path as required.
	# Note that these settings are required for each EEE database, so if you have a test database or separate databases for different brands/chains that you operate, these steps should be repeated for each database.		# Note that these settings are required for each EEE database, so if you have a test database or separate databases for different brands/chains that you operate, these steps should be repeated for each database.
	# If these steps fail to resolve the problem, contact Magenta Support. Please try to have full details of error messages available.		# If these steps fail to resolve the problem, contact Magenta Support. Please try to have full details of error messages available.

	= See Also: =		= See Also: =

Bevan at 04:10, 3 March 2009

2009-03-03T04:10:58Z

← Older revision		Revision as of 04:10, 3 March 2009
Line 21:		Line 21:
	=== To Resolve This Issue: ===		=== To Resolve This Issue: ===
	# Determine the location of Magenta_SQL.DLL. Usually this is installed in c:\EEE\SQLDLL.		# Determine the location of Magenta_SQL.DLL. Usually this is installed in c:\EEE\SQLDLL.
	# Run the SQL Server Command:~~<tt>~~'''EXEC usp_ClrUpdate 'EEE', 'C:\EEE\SQLDLL\Magenta_SQL.DLL''''</tt>Substitute the correct database name and file path as required.		# Run the SQL Server Command:
			'''EXEC usp_ClrUpdate 'EEE', 'C:\EEE\SQLDLL\Magenta_SQL.DLL''''
			</tt>Substitute the correct database name and file path as required.
	# Note that these settings are required for each EEE database, so if you have a test database or separate databases for different brands/chains that you operate, these steps should be repeated for each database.		# Note that these settings are required for each EEE database, so if you have a test database or separate databases for different brands/chains that you operate, these steps should be repeated for each database.
	# If these steps fail to resolve the problem, contact Magenta Support. Please try to have full details of error messages available.		# If these steps fail to resolve the problem, contact Magenta Support. Please try to have full details of error messages available.

	= See Also: =		= See Also: =

Bevan at 04:08, 3 March 2009

2009-03-03T04:08:59Z

← Older revision		Revision as of 04:08, 3 March 2009
Line 14:		Line 14:
	To test if this problem is present, open SQL Server Management Studio and open a new query against the EEE database. Run this query:		To test if this problem is present, open SQL Server Management Studio and open a new query against the EEE database. Run this query:

	~~<tt>~~'''select dbo.ufn_CLRFileExists ('~~[../../../../../../myfile.txt~~ c:\myfile.txt]')'''~~</tt>~~		'''select dbo.ufn_CLRFileExists ('c:\myfile.txt')'''

	This query should return 0 or 1 depending if the file exists. If the assembly registration with SQL Server is incorrect an error message, possibly similar to the above, will be returned.		This query should return 0 or 1 depending if the file exists. If the assembly registration with SQL Server is incorrect an error message, possibly similar to the above, will be returned.

Bevan at 04:07, 3 March 2009

2009-03-03T04:07:08Z

Bevan at 04:03, 3 March 2009

2009-03-03T04:03:05Z

← Older revision		Revision as of 04:03, 3 March 2009
Line 2:		Line 2:


	~~== EEE SQL Server Errors in Microsoft .NET Framework ==~~
	The EEE database SQL Server utilises a .NET assembly (DLL) to provide extended functionality from within SQL Server. For example, to provide access to the local file system on the SQL Server.		The EEE database SQL Server utilises a .NET assembly (DLL) to provide extended functionality from within SQL Server. For example, to provide access to the local file system on the SQL Server.

Line 20:		Line 19:


	~~Corrective Steps~~:		=== To Resolve This Issue: ===

	# Determine the location of Magenta_SQL.DLL. Usually this is installed in c:\EEE\SQLDLL.		# Determine the location of Magenta_SQL.DLL. Usually this is installed in c:\EEE\SQLDLL.
	# Run the SQL Server Command:<tt>'''EXEC usp_ClrUpdate 'EEE', 'C:\EEE\SQL\DLL\Magenta_SQL.DLL''''</tt>Substitute the correct database name and file path as required		# Run the SQL Server Command:<tt>'''EXEC usp_ClrUpdate 'EEE', 'C:\EEE\SQL\DLL\Magenta_SQL.DLL''''</tt>Substitute the correct database name and file path as required

Bevan at 04:01, 3 March 2009

2009-03-03T04:01:56Z

← Older revision		Revision as of 04:01, 3 March 2009
Line 1:		Line 1:
	= Created: 03 March 2009. Last Reviewed: 03 March 2009 =		Created: 03 March 2009. Last Reviewed: 03 March 2009


	== EEE SQL Server Errors in Microsoft .NET Framework ==		== EEE SQL Server Errors in Microsoft .NET Framework ==
	The EEE database SQL Server utilises a .NET assembly (DLL) to provide extended functionality from within SQL Server. For example, to provide access to the local file system on the SQL Server.		The EEE database SQL Server utilises a .NET assembly (DLL) to provide extended functionality from within SQL Server. For example, to provide access to the local file system on the SQL Server.

← Older revision		Revision as of 04:07, 3 March 2009
Line 2:		Line 2:


	The EEE database SQL Server utilises a .NET assembly (DLL) to provide extended functionality from within SQL Server. For example, to provide access to the local file system on the SQL Server.		The EEE database in SQL Server utilises a .NET assembly (DLL) to provide extended functionality which is accessible from within SQL Server. For example, to provide access to the local file system on the SQL Server from inside TSQL stored procedures.

	If the registration of this ~~assebly~~ with SQL Server is incorrect or inadvertantly damaged then some features of EEE may stop working. For example, inter-store transfer requests will fail, because SQL Server uses the assembly to send the stock request notification to the target store. If this happens, stores users will ~~get~~ a message that the stock transfer request was not successful.		If the registration of this assembly with SQL Server is incorrect or inadvertantly damaged then some features of EEE may stop working. For example, inter-store transfer requests will fail, because SQL Server uses the assembly to send the stock request notification to the target store. If this happens, stores users will see a message to the effect that the stock transfer request was not successful.

	SQL Server will return error messages similar to:		SQL Server will return error messages similar to:
Line 10:		Line 10:
	Msg 10314, Level 16, State 11, Line 1An error occurred in the Microsoft .NET Framework while trying to load assembly id 65544. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error: System.IO.FileLoadException: Could not load file or assembly 'magenta_sql, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Exception from HRESULT: 0x80FC0E21System.IO.FileLoadException:    at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)   at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)   at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)   at System.Reflection.Assembly.Load(String assemblyString)		Msg 10314, Level 16, State 11, Line 1An error occurred in the Microsoft .NET Framework while trying to load assembly id 65544. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error: System.IO.FileLoadException: Could not load file or assembly 'magenta_sql, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Exception from HRESULT: 0x80FC0E21System.IO.FileLoadException:    at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)   at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)   at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)   at System.Reflection.Assembly.Load(String assemblyString)

	The error messages may be logged in the Windows application event log or returned to the user.		The error messages may be logged in the Windows application event log or returned to the user, depending on where the error occurs.

	To test if this problem is present, open SQL Server ~~Maangement~~ Studio and open a new query against the EEE database. Run this query:		To test if this problem is present, open SQL Server Management Studio and open a new query against the EEE database. Run this query:

	select dbo.ufn_CLRFileExists ('[../../../../../../myfile.txt c:\myfile.txt]').		<tt>'''select dbo.ufn_CLRFileExists ('[../../../../../../myfile.txt c:\myfile.txt]')'''</tt>

	~~The function~~ should return 0 or 1 depending if the file exists. If the assembly registration with SQL Server is incorrect an error message, possibly similar to the above, will be returned.		This query should return 0 or 1 depending if the file exists. If the assembly registration with SQL Server is incorrect an error message, possibly similar to the above, will be returned.


	=== To Resolve This Issue: ===		=== To Resolve This Issue: ===
	# Determine the location of Magenta_SQL.DLL. Usually this is installed in c:\EEE\SQLDLL.		# Determine the location of Magenta_SQL.DLL. Usually this is installed in c:\EEE\SQLDLL.
	# Run the SQL Server Command:<tt>'''EXEC usp_ClrUpdate 'EEE', 'C:\EEE\~~SQL\DLL~~\Magenta_SQL.DLL''''</tt>Substitute the correct database name and file path as required		# Run the SQL Server Command:<tt>'''EXEC usp_ClrUpdate 'EEE', 'C:\EEE\SQLDLL\Magenta_SQL.DLL''''</tt>Substitute the correct database name and file path as required.
	# Note that these settings are required for each EEE database, so if you have a test database or separate databases for different brands/chains that you operate, these steps should be repeated for each database.		# Note that these settings are required for each EEE database, so if you have a test database or separate databases for different brands/chains that you operate, these steps should be repeated for each database.
	# If these steps fail to resolve the problem, contact Magenta Support. Please try to have full details of error messages available.		# If these steps fail to resolve the problem, contact Magenta Support. Please try to have full details of error messages available.

	= See Also: =		= See Also: =