EEE Notification warnings - Revision history

Trevor at 04:17, 6 August 2012

2012-08-06T04:17:30Z

← Older revision		Revision as of 04:17, 6 August 2012
Line 1:		Line 1:
	Created: 02 February 2011. Last Reviewed: ~~02 February 2011~~		Created: 02 February 2011. Last Reviewed: 06 August 2012


Line 13:		Line 13:
	The till may have the notifications path configured incorrectly or the folder security is incorrect.		The till may have the notifications path configured incorrectly or the folder security is incorrect.

	This has happened a number of times at ~~Banks~~, so the information below relates to fixing the problem on ~~Banks~~ server.		This has happened a number of times at one client, so the information below relates to fixing the problem on their server.


	To fix the issue, use Process Explorer on the SQL Server.		To fix the issue, use Process Explorer on the SQL Server.

	At ~~Banks~~, this can be located in D:\Temp\ProcessExplorer\procexp64.exe.		At this client, this can be located in D:\Temp\ProcessExplorer\procexp64.exe.

	- Click the Find menu, then 'Find Handle or dll...'		- Click the Find menu, then 'Find Handle or dll...'

Robert at 21:59, 10 February 2011

2011-02-10T21:59:08Z

← Older revision		Revision as of 21:59, 10 February 2011
Line 18:		Line 18:
	To fix the issue, use Process Explorer on the SQL Server.		To fix the issue, use Process Explorer on the SQL Server.

	At Banks, this can be located in D:\Temp\ProcessExplorer\procexp64.exe. Further information on using Process Explorer, plus a download link can be found here: [http://technet.microsoft.com/en-us/sysinternals/bb896653 http://technet.microsoft.com/en-us/sysinternals/bb896653]		At Banks, this can be located in D:\Temp\ProcessExplorer\procexp64.exe.


	- Click the Find menu, then 'Find Handle or dll...'		- Click the Find menu, then 'Find Handle or dll...'
Line 30:		Line 29:

	- You'll be prompted to confirm, say OK, then the errors should stop and SQL should be able to update the file next time a change is detected.		- You'll be prompted to confirm, say OK, then the errors should stop and SQL should be able to update the file next time a change is detected.


			Further information on using Process Explorer, plus a download link can be found here: [http://technet.microsoft.com/en-us/sysinternals/bb896653 http://technet.microsoft.com/en-us/sysinternals/bb896653]

Robert at 21:58, 10 February 2011

2011-02-10T21:58:38Z

← Older revision		Revision as of 21:58, 10 February 2011
Line 16:		Line 16:


	To fix the issue, use Process Explorer on the SQL Server. At Banks, this can be located in D:\Temp\ProcessExplorer\~~procexp54~~.exe. Further information on using Process Explorer, plus a download link can be found here: [http://technet.microsoft.com/en-us/sysinternals/bb896653 http://technet.microsoft.com/en-us/sysinternals/bb896653]		To fix the issue, use Process Explorer on the SQL Server.

			At Banks, this can be located in D:\Temp\ProcessExplorer\procexp64.exe. Further information on using Process Explorer, plus a download link can be found here: [http://technet.microsoft.com/en-us/sysinternals/bb896653 http://technet.microsoft.com/en-us/sysinternals/bb896653]

Trevor at 14:50, 1 February 2011

2011-02-01T14:50:06Z

← Older revision		Revision as of 14:50, 1 February 2011
Line 8:		Line 8:
	for till: 232302		for till: 232302
	with content: 0		with content: 0
	failed with error: mscorlib The process cannot access the file 'd:\eeedata\production\notifications\2323\232302.NOT' because it is being used by another process..		failed with error: mscorlib The process cannot access the file
			'd:\eeedata\production\notifications\2323\232302.NOT' because it is being used
			by another process..
	The till may have the notifications path configured incorrectly or the folder security is incorrect.		The till may have the notifications path configured incorrectly or the folder security is incorrect.

Line 21:		Line 23:
	- Search for the name of the file that is being reported as locked in the alert email.		- Search for the name of the file that is being reported as locked in the alert email.

	- Select the result and the bottom half of the screen will show the file handle. Most ~~likley~~ this will be locked by sqlservr.exe.		- Select the result and the bottom half of the screen will show the file handle. Most likely this will be locked by sqlservr.exe.

	- Right click the handle and select close handle		- Right click the handle and select close handle

	- You'll be prompted to confirm, say OK, then the errors should stop and SQL should be able to update the file next time a change is detected.		- You'll be prompted to confirm, say OK, then the errors should stop and SQL should be able to update the file next time a change is detected.

Trevor: New page: Created: 02 February 2011. Last Reviewed: 02 February 2011 If you receive an alert email titled EEE Notifications Warning, and the email is similar to below, the most likely explanation ...

2011-02-01T14:44:45Z

New page: Created: 02 February 2011. Last Reviewed: 02 February 2011 If you receive an alert email titled EEE Notifications Warning, and the email is similar to below, the most likely explanation ...

New page

Created: 02 February 2011. Last Reviewed: 02 February 2011

If you receive an alert email titled EEE Notifications Warning, and the email is similar to below, the most likely explanation is the SQL Server has locked the file and not released the lock.

Failed to created the notifications file at: d:\eeedata\production\notifications\2323\232302.NOT
for till: 232302
with content: 0
failed with error: mscorlib The process cannot access the file 'd:\eeedata\production\notifications\2323\232302.NOT' because it is being used by another process..
The till may have the notifications path configured incorrectly or the folder security is incorrect.

This has happened a number of times at Banks, so the information below relates to fixing the problem on Banks server.

To fix the issue, use Process Explorer on the SQL Server. At Banks, this can be located in D:\Temp\ProcessExplorer\procexp54.exe. Further information on using Process Explorer, plus a download link can be found here: [http://technet.microsoft.com/en-us/sysinternals/bb896653 http://technet.microsoft.com/en-us/sysinternals/bb896653]

- Click the Find menu, then 'Find Handle or dll...'

- Search for the name of the file that is being reported as locked in the alert email.

- Select the result and the bottom half of the screen will show the file handle. Most likley this will be locked by sqlservr.exe.

- Right click the handle and select close handle

- You'll be prompted to confirm, say OK, then the errors should stop and SQL should be able to update the file next time a change is detected.