Difference between revisions of "ITrack/IDispatch error 14534 - Access Denied"

From ISoft Wiki
Jump to navigationJump to search
(Logging a new IDispatch Error I found)
 
(Fixing category, image, formatting)
 
(One intermediate revision by one other user not shown)
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).


[[Category:Printing Error Messages (ITrack)]]
Another possible issue is that the reports directory may not have the proper permissions.
 
== 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]]

Latest revision as of 11:24, 31 October 2011

IDispatch Error 14534.PNG

Cause

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).

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

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).