java.io.FileNotFoundException: /opt/work/ptd/kfs/attachments/9/1/9/1/1/6/91911657-509E-2C9A-1F13-55A7D046206D/16290C83-77FD-969A-6C4D-CB1EF3E467CB (No such file or directory)

Kuali JIRA | Barb Sutton | 4 years ago
  1. 0

    When an attachment is deleted from a Vendor doc, it still shows on the doc as an attachment. - To Recreate - Create a new Vendor with an attachment, approve the Vendor doc to FINAL status or Blanket Approve, click on the Vendor link and do a Vendor search for your new Vendor, click on edit, now delete the attachment that you attached to your new Vendor, Blanket Approve this change. Now search for your new Vendor again, click on the vendor name to open the Vendor Inquiry, scroll down to the Notes/Attachments area and the attachment is still there. The attachment should no longer show in this scenario as it's been deleted. - Result - The attachment is still showing on the Vendor doc and when you click on the attachment, you get a stack trace error. java.io.FileNotFoundException: /opt/work/ptd/kfs/attachments/9/1/9/1/1/6/91911657-509E-2C9A-1F13-55A7D046206D/16290C83-77FD-969A-6C4D-CB1EF3E467CB (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:137) at java.io.FileInputStream.(FileInputStream.java:96) at org.kuali.rice.kns.service.impl.AttachmentServiceImpl.retrieveAttachmentContents(AttachmentServiceImpl.java:198) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) - Reason for Error - The attachment file has been deleted and no longer exists so the file is unable to be found. The reason the attachment still shows on the doc even though it's been deleted is because the attachment record in the KRNS_ATT_T table was not deleted and the note record in the KRNS_NTE_T table was not deleted. Once these two records are deleted, it no longer shows in the vendor.

    Kuali JIRA | 4 years ago | Barb Sutton
    java.io.FileNotFoundException: /opt/work/ptd/kfs/attachments/9/1/9/1/1/6/91911657-509E-2C9A-1F13-55A7D046206D/16290C83-77FD-969A-6C4D-CB1EF3E467CB (No such file or directory)
  2. 0

    When an attachment is deleted from a Vendor doc, it still shows on the doc as an attachment. - To Recreate - Create a new Vendor with an attachment, approve the Vendor doc to FINAL status or Blanket Approve, click on the Vendor link and do a Vendor search for your new Vendor, click on edit, now delete the attachment that you attached to your new Vendor, Blanket Approve this change. Now search for your new Vendor again, click on the vendor name to open the Vendor Inquiry, scroll down to the Notes/Attachments area and the attachment is still there. The attachment should no longer show in this scenario as it's been deleted. - Result - The attachment is still showing on the Vendor doc and when you click on the attachment, you get a stack trace error. java.io.FileNotFoundException: /opt/work/ptd/kfs/attachments/9/1/9/1/1/6/91911657-509E-2C9A-1F13-55A7D046206D/16290C83-77FD-969A-6C4D-CB1EF3E467CB (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:137) at java.io.FileInputStream.(FileInputStream.java:96) at org.kuali.rice.kns.service.impl.AttachmentServiceImpl.retrieveAttachmentContents(AttachmentServiceImpl.java:198) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) - Reason for Error - The attachment file has been deleted and no longer exists so the file is unable to be found. The reason the attachment still shows on the doc even though it's been deleted is because the attachment record in the KRNS_ATT_T table was not deleted and the note record in the KRNS_NTE_T table was not deleted. Once these two records are deleted, it no longer shows in the vendor.

    Kuali JIRA | 4 years ago | Barb Sutton
    java.io.FileNotFoundException: /opt/work/ptd/kfs/attachments/9/1/9/1/1/6/91911657-509E-2C9A-1F13-55A7D046206D/16290C83-77FD-969A-6C4D-CB1EF3E467CB (No such file or directory)
  3. 0

    absence of ../hash/mameROMs.xml.gz causing NPEs (I think).

    GitHub | 4 years ago | victort
    java.io.IOException: java.io.FileNotFoundException: ../hash/mameROMs.xml.gz (No such file or directory)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    can't find ebs.pem file

    GitHub | 4 years ago | yegor256
    com.netbout.inf.index.EbsVolume: #path(): failed with java.io.IOException: com.jcraft.jsch.JSchException: java.io.FileNotFoundException: file:/opt/tomcat7/webapps/ROOT/WEB-INF/lib/netbout-inf-2.0-SNAPSHOT.jar!/com/netbout/inf/index/ebs.pem (No such file or directory)
  6. 0

    deploy war into tomcat staging environment failed

    GitHub | 5 years ago | quorak
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'SassResourceMapper': Cannot resolve reference to bean 'SassResourceMapperInstance' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'SassResourceMapperInstance': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [SassResourceMapper]: Constructor threw exception; nested exception is java.io.FileNotFoundException: /var/lib/tomcat6/grails-app/conf/DefaultGrassConfig.groovy (No such file or directory)

  1. gehel 2 times, last 1 week ago
  2. Kialandei 100 times, last 1 week ago
  3. Reich 1 times, last 2 weeks ago
  4. bluebunnty 1 times, last 2 weeks ago
  5. Aria Pahlavan 1 times, last 2 weeks ago
43 more registered users
52 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. java.io.FileNotFoundException

    /opt/work/ptd/kfs/attachments/9/1/9/1/1/6/91911657-509E-2C9A-1F13-55A7D046206D/16290C83-77FD-969A-6C4D-CB1EF3E467CB (No such file or directory)

    at java.io.FileInputStream.open()
  2. Java RT
    FileInputStream.<init>
    1. java.io.FileInputStream.open(Native Method)
    2. java.io.FileInputStream.<init>(FileInputStream.java:137)
    3. java.io.FileInputStream.<init>(FileInputStream.java:96)
    3 frames
  3. org.kuali.rice
    AttachmentServiceImpl.retrieveAttachmentContents
    1. org.kuali.rice.kns.service.impl.AttachmentServiceImpl.retrieveAttachmentContents(AttachmentServiceImpl.java:198)
    1 frame
  4. Java RT
    NativeMethodAccessorImpl.invoke0
    1. sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    1 frame