Package export failed error
I am trying to export a set of applications. The package includes three applications and a workspace. When I generate the package including a particular application, the package export fails and says to review the error log for details. The error log says, "Unable to open a Repository File for this Module, either because it doesn't exist, or it is locked by another process. Please make sure this file exists in your configured Repository Files directory, or remove and re-add the Attachment for this Module." I cannot see anything locking this application. I have restarted IIS and the services. There is noone else in this environment.
Any help in resolving the issue would be fantastic.
Thanks a lot,
- Community Thread
- Forum Thread
- RSA Archer
- RSA Archer Suite
There are a few reasons that this error appears, but the most prevalent ones is a application has an attachment (on the General tab) and that file is deleted from the file respository directory. This could likely occur with a database is copied to another environment, but the file repository was not copied.
Further down the error stack, it will tell you exactly which file is missing. Depending upon your circumstances, you can either create a dummy file which has the same name or copy the file from the file repository from where it originated.
Ok, BCPAplicationExport.xml was a file attached to that application? I can just create a file called the same thing and attach it to the application?
<Message>Unable to open a Repository File for this Module, either because it doesn't exist, or it is locked by another process. Please make sure this file exists in your configured Repository Files directory, or remove and re-add the Attachment for this Module.</Message>
<Module>Business Recovery Plans</Module>
The fact that it is an XML file is a bit concerning, since that looks like it's an application. I have only ever seen Word and Text files with this issue. The file that you would create would be called "12952.xml" and you would put it in the file repository directory on the server.
You might try creating the package from scratch. If the package existed prior to you attempting to generate it and the database was copied from one place to another, that could be part of the problem.
I just created that xml file and attached it to the application, regenerated the package, and got the same error. The module that is giving me trouble is Devices, but the error looks like it is referring to Business Recovery Plans. I have also noticed that Devices is part of the Busines Continuity Solution, but I don't see a cross-reference to that application. I do see a related record, though.
This is a new package I created today, and I have recreated it several times.
If you added the file to the attachment field in the application, I would expect for you to receive the same error. When you did that, it changed the name of the file when it added to the file repository. That is why you must copy the file directly into the file repository.
I am als getting package failures. However, the issue seems to be that there's a "retired" application that had a null body in the notification template. However, the notification that's "null" is not one of the applications that I'm packaging. Why do packages fail to build if there's an issue in an unrelated application?
The error message was: The template for the body of notification 'Assignment Notification' is null