If you use the IEE exe file from your test environment to log into your prod environment, does it work then? My memory of these errors is that there is a problem with the build of the client (so not a bug from the R&D version of the exe).

Hi @Mathias Dahl , 

Thank you very much for the suggestion. Unfortunately It didn’t help. I tried to: 

• delete whole 2.0 folder, then reinstall IFS instances (test and prod)
• delete prod Ifs.Fnd.Explorer.exe and copy there the test .exe 
• delete windows registry keys regarding IFS

Neither above steps helped. 

Ifs.Fnd.FndSystemException: Explorer: An Unhandled Exception has occurred ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at Ifs.Application.Docman.cEdmRepository.___DownloadDocument(String sourceFileName, String destinationFileName, String sDocClass, String sDocNo, String sDocSheet, String sDocRev, String sDocType, String sTicket)
   at Ifs.Application.Docman.cEdmRepository._GetCopyOfCheckedOutFileFromRepo(SalString sDocClass, SalString sDocNo, SalString sDocSheet, SalString sDocRev, SalString sDocType, SalString sTicket)
   at Ifs.Application.Docman.cEdm.ViewCopyExecute()
   at Ifs.Application.DocumentConnectionsAttachmentPlugin.DocumentConnectionsAttachmentPlugin.flvDocConnection_MouseDoubleClick(Object sender, MouseEventArgs e)
   at System.Windows.Forms.Control.OnMouseDoubleClick(MouseEventArgs e)
   at System.Windows.Forms.ListView.WndProc(Message& m)
   at Ifs.Fnd.Windows.Forms.FndListView.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   --- End of inner exception stack trace ---

Do you have other ideas? 

Thank you very much for any thoughts. 

Best regards, 

Balazs

How does the document repository setup look in Prod vs Test? Do you use database, FTP or Shared repositories?

Hi @Mathias Dahl ,

Document repository settings is exactly the same, we use database repository. 

We investigated a lot and it looks like this message pops up when we attach documents also. So not just when we would like to open an attached doc. We saw somehow our Live environment is not able to write and read records to edm_file_storage_tab. 

We receive the error above when we have record in edm_file_tab but somehow the connected record is missing from edm_file_storage_tab.

Currently we don’t know how is this possible. Probably this is not permission issue, because IFSAPP user also not able to add record. 

Thank you very much for your thoughts!

Best regards, 

Balazs

We receive the error above when we have record in edm_file_tab but somehow the connected record is missing from edm_file_storage_tab.

That sounds familiar. Could there be some custom event that is stopping that record from being created?

Hi @bapehu 

Are you getting this error consistently when you do any kind of document operation, such as attaching documents and viewing them? If so then this could be an issue due to DOCUMENT_TICKET_TEMP_PATH parameter. Check if the path you have defined for DOCUMENT_TICKET_TEMP_PATH under document basic data is a valid path in the application server or not. If it is a valid path, then you can try to reconfigure the instance and in one step it will ask for the temp path parameter and give the same path value there as well.

Thanks and Regards,

Amila