ITrack/IDispatch error 14534 - Access Denied - Revision history

Duff: Fixing category, image, formatting

2011-10-31T17:24:34Z

Fixing category, image, formatting

← Older revision		Revision as of 12:24, 31 October 2011
Line 1:		Line 1:
	[[Image:IDispatch_Error_14534.PNG~~\|400px\|thumb\|left~~]]		[[Image:IDispatch_Error_14534.PNG]]

	This error occurs because of an issue where Windows does not immediately recognize the reports directory on the server. Once you navigate to the reports directory this error message should no longer appear. However, this is only a temporary solution; this error will appear each time the user starts his/her computer (until they go to their reports directory).		== Cause ==
			This error occurs because of an issue where Windows does not immediately recognize the reports directory on the server.

	~~To solve~~ this ~~problem~~, ~~simply map~~ the ~~ITrack folder on the server~~ to ~~a network drive, then reflect that change within ITrack (change where ITrack looks for the~~ reports directory ~~- now a mapped network drive~~).		Once you navigate to the reports directory this error message should no longer appear. However, this is only a temporary solution; this error will appear each time the user starts his/her computer (until they go to their reports directory).

	Another possible issue is that the reports directory may not have the proper permissions.		Another possible issue is that the reports directory may not have the proper permissions.

	[[Category:Printing Error Messages ~~(ITrack)~~]]		== Solution ==
			Simply map the ITrack folder on the server to a network drive, then reflect that change within ITrack (change where ITrack looks for the reports directory - now a mapped network drive).

			[[Category:ITrack/Printing Error Messages]]

	[[Category:ITrack/Support]]		[[Category:ITrack/Support]]

Codeman at 20:44, 1 December 2010

2010-12-01T20:44:05Z

← Older revision		Revision as of 15:44, 1 December 2010
Line 4:		Line 4:

	To solve this problem, simply map the ITrack folder on the server to a network drive, then reflect that change within ITrack (change where ITrack looks for the reports directory - now a mapped network drive).		To solve this problem, simply map the ITrack folder on the server to a network drive, then reflect that change within ITrack (change where ITrack looks for the reports directory - now a mapped network drive).

			Another possible issue is that the reports directory may not have the proper permissions.

	[[Category:Printing Error Messages (ITrack)]]		[[Category:Printing Error Messages (ITrack)]]

	[[Category:ITrack/Support]]		[[Category:ITrack/Support]]

Codeman: Logging a new IDispatch Error I found

2009-09-21T16:49:10Z

Logging a new IDispatch Error I found

New page

[[Image:IDispatch_Error_14534.PNG|400px|thumb|left]]

This error occurs because of an issue where Windows does not immediately recognize the reports directory on the server. Once you navigate to the reports directory this error message should no longer appear. However, this is only a temporary solution; this error will appear each time the user starts his/her computer (until they go to their reports directory).

To solve this problem, simply map the ITrack folder on the server to a network drive, then reflect that change within ITrack (change where ITrack looks for the reports directory - now a mapped network drive).

[[Category:Printing Error Messages (ITrack)]]

[[Category:ITrack/Support]]