Access denied error when attempting to launch Image Editor in CuteEdit 5.0

Last post 06-09-2006, 3:37 PM by ludis. 7 replies.
Sort Posts: Previous Next
  •  10-18-2005, 3:14 PM 11815

    Access denied error when attempting to launch Image Editor in CuteEdit 5.0

    When I select an image and then click the button to launch the image editor, I get the following error information (note: this is a custom error stack/email msg that we get to use in troubleshooting).  Also - the folder in question has Everyone-Full Control access + FileMon reports no access denied errors in the file system.  The file in the error msg exists at the path in the error information...

    Any ideas?

    Jeramie
     
    URL Requested: /GMADemo/CuteSoft_Client/CuteEditor/ImageEditor/ImageEditor.aspx?settinghash=ce87e15&GP=/GMADemo/Uploads&C_GP=/GMADemo/Uploads&Upload=True&UC=en-US&BG=%23efefef&Th_W=80&Th_H=80&Th_C=5&Th_R=4&MaxW=640&MaxH=640&Resize=True&Restriction=True&MaxImageSize=100&f=/GMADemo/Assets/Images/logo.JPG&p=/GMADemo/CuteSoft_Client/CuteEditor/

    Stack Trace:
    System.Web.HttpUnhandledException: Exception of type System.Web.HttpUnhandledException was thrown. ---> System.UnauthorizedAccessException: Access to the path "C:\GMAMimswareCMSDemo\Tier1\CuteSoft_Client\CuteEditor\ImageEditor\TempFiles\2548884e-54bc-4490-a025-3f09736aaa97000001.tmp" is denied.
       at System.IO.__Error.WinIOError(Int32 errorCode, String str)
       at System.IO.File.Delete(String path)
       at CuteEditor.ImageEditor.ApplicationRecords..ctor(String temppath)
       at CuteEditor.ImageEditor.ImageEditor.OnPreRender(EventArgs e)
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Page.ProcessRequestMain()
       --- End of inner exception stack trace ---
       at System.Web.UI.Page.HandleError(Exception e)
       at System.Web.UI.Page.ProcessRequestMain()
       at System.Web.UI.Page.ProcessRequest()
       at System.Web.UI.Page.ProcessRequest(HttpContext context)
       at System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

    Regards,
    Jeramie
  •  10-18-2005, 5:37 PM 11824 in reply to 11815

    Re: Access denied error when attempting to launch Image Editor in CuteEdit 5.0

    Jeramie,

    Can you give everyone full control to CuteSoft_Client\CuteEditor\ImageEditor\TempFiles\ as well?

    Keep me posted
     

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  10-21-2005, 11:58 AM 11917 in reply to 11824

    Re: Access denied error when attempting to launch Image Editor in CuteEdit 5.0

    Hi Adam,
     
    Everyone is set to Full Control.  It was that way when I reported the issue (e.g. still get that Access Denied error).  As I noted earlier, FileMon doesn't report an Access Denied at the file system level which would indicate that some other problem is occurring (e.g. if it was ACL related on the file system, FileMon would report the error.
     
    Any ideas?
     
    Jeramie

    Regards,
    Jeramie
  •  10-22-2005, 2:19 AM 11937 in reply to 11824

    Re: Access denied error when attempting to launch Image Editor in CuteEdit 5.0

     Adam wrote:
    Jeramie,

    Can you give everyone full control to CuteSoft_Client\CuteEditor\ImageEditor\TempFiles\ as well?

    Keep me posted
     
     
    Are you sure you have give ASPNET user write access to CuteSoft_Client\CuteEditor\ImageEditor\TempFiles???

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  10-23-2005, 7:53 PM 11951 in reply to 11937

    Re: Access denied error when attempting to launch Image Editor in CuteEdit 5.0

     
    Hi Adam, as you can see, the permissions are set.  Not to belabor the issue, but since FileMon doesn't report an Access Denied error, this isn't likely a file system ACL issue (e.g. if it was, I'd see Access Denied in the results from FileMon).  Any ideas?
     
    Thanks in advance for the help,
    Jeramie

    Regards,
    Jeramie
  •  10-23-2005, 7:56 PM 11952 in reply to 11951

    Re: Access denied error when attempting to launch Image Editor in CuteEdit 5.0

    For some reason, the image didn't post in the last post.  Another thing is that the temp files are being written - I've verified that the file in the error message exists, so seems to be something else (e.g. can't read the file or some other error in code being reported as access denied).
     
    Again, no access denied is trapped at the file system level by FileMon, so this would appear to be something in code that is assuming an access denied condition.
     
    Any help is much appreciated.
     
    Thanks again,
    Jeramie

    Regards,
    Jeramie
  •  10-24-2005, 2:34 PM 11964 in reply to 11952

    Re: Access denied error when attempting to launch Image Editor in CuteEdit 5.0

    Hi Adam,

    I resolved the issue.  It ended up being that the files under the CuteSoft_Client folder were marked read only (e.g. as the result of being pulled from a version control system that way...).  I made all files read/write and the editor now works.  Big note is that it didn't have anything to do with the ACL on the folders/files, but instead, the config on the files themselves (e.g. flagged as read only).  As a suggestion, it would be a good idea to have the exception report the difference between ("I can't read the file because it's read only" and "I can't read the file because an ACL is preventing me from doing so").  It would cut down the resolution time on the issue...
     
    Take care,
    Jeramie

    Regards,
    Jeramie
  •  06-09-2006, 3:37 PM 19976 in reply to 11964

    Re: Access denied error when attempting to launch Image Editor in CuteEdit 5.0

    I had the same problem on a win2k3 machine...I could not unset the Read-Only attribute of the properties...microsoft has published a workaround, essentially

    attrib -r -s c:path\directory

    background info:

    CAUSE

    Unlike the Read-only attribute for a file, the Read-only attribute for a folder is typically ignored by Windows, Windows components and accessories, and other programs. For example, you can delete, rename, and change a folder with the Read-only attribute by using Windows Explorer. The Read-only and System attributes is only used by Windows Explorer to determine whether the folder is a special folder, such as a system folder that has its view customized by Windows (for example, My Documents, Favorites, Fonts, Downloaded Program Files), or a folder that you customized by using the Customize tab of the folder's Properties dialog box. As a result, Windows Explorer does not allow you to view or change the Read-only or System attributes of folders. When a folder has the Read-Only attribute set it causes Explorer to request the Desktop.ini of that folder to see if any special folder settings need to be set. It has been seen where if a network share that has a large amount of folders set to Read-only, it can cause Explorer to take longer then what is expected to render the contents of that share while it waits on the retrieval of the Desktop.ini files. The slower the network connectivity to the share the longer this process can take to the point where Explorer may timeout waiting for the data and render nothing or appear to hang.

    Note In some previous versions of Windows, you can change the Read-only attribute for folders by using the Properties dialog box for the folder, but no versions of Windows permit you to change the System attribute by using Windows Explorer.

    WORKAROUND

    To work around this issue, use the Attrib command at a command prompt (Cmd.exe) to view or remove the Read-only or System attributes of folders. Type attrib /? at the command prompt to view the syntax for the Attrib command.

    Warning If you remove the Read-only or System attribute from a folder, it may appear as a ordinary folder and some customizations may be lost. For example, Windows customizes the Fonts folder and provides a special folder view that permits you to hide variations, such as bold and italic. It also permits you to change the folder's view settings in ways that are specific to fonts. If you remove the Read-only and System attributes of the Fonts folder, these customized view settings are not available. For folders that you have customized by using the Customize tab of the folder's Properties dialog box, the folder icon and other other customizations may be lost when you remove the Read-only attribute.

    If a program cannot save files to a folder with the Read-only attribute, such as My Documents, change the Read-only attribute to System by using the Attrib command at a command prompt.

    For example, to change the Read-only attribute to System for the C:\Test folder, use the following command:
    attrib -r +s c:\test
    Note that some programs may not operate correctly with folders that have the System attribute set. To remove both the Read-only and System attributes from the C:\Test folder, use the following command:
    attrib -r -s c:\test


View as RSS news feed in XML