cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X

Unable to upload files in Windchill PDMLink 12.0

ahoerl
8-Gravel

Unable to upload files in Windchill PDMLink 12.0

I am using Windchill PDMLink Release 12.0 and Datecode with CPS 12.0.2.0

Uploading any file will result in an error that a file of the same name already exists in the vault. Reseeding sequence value as shown here:

https://www.ptc.com/en/support/article/CS374128

did not work. Deleting the files in the current folder from the sequence value onward temporarily resolves the issue (but probably leads to unwanted data loss)

Here are the errors that I faced
2024-04-23 18:17:51,471 ERROR [ajp-nio-127.0.0.1-8010-exec-5] wt.objectstorage.ContentFileWriter - This file cannot be saved because a file named "E:\Vaults\defaultsystemrootfolder\defaultsystemrootfolder_Folder_234\000000011d115e" already exists.
2024-04-23 18:17:51,487 ERROR [ajp-nio-127.0.0.1-8010-exec-5] wt.fv.uploadtocache - (wt.fv.fvResource/63) wt.objectstorage.exception.ContentFileAlreadyExistsException: This file cannot be saved because a file named "E:\Vaults\defaultsystemrootfolder\defaultsystemrootfolder_Folder_234\000000011d115e" already exists.
at wt.objectstorage.ContentFileWriter.storeStream(ContentFileWriter.java:106)
at wt.fv.uploadtocache.DoUploadToCache_Server.storeContentInVaultOnMaster(DoUploadToCache_Server.java:630)
at wt.fv.uploadtocache.DoUploadToCache_Server.storeSingleFile(DoUploadToCache_Server.java:1944)
at wt.fv.uploadtocache.DoUploadToCache_Server.doMultiPartUploadToCache_Server(DoUploadToCache_Server.java:1728)
at wt.fv.uploadtocache.DoUploadToCache_Server.doUploadToCache_Master(DoUploadToCache_Server.java:133)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at wt.httpgw.HTTPServer.processRequest(HTTPServer.java:346)
at wt.httpgw.MethodRequestHandler.handleRequest(MethodRequestHandler.java:88)
at wt.httpgw.HTTPGatewayServlet.serviceWithoutFilters(HTTPGatewayServlet.java:336)
at wt.httpgw.FilterChainImpl.doFilter(FilterChainImpl.java:94)
at wt.session.SessionContextDestroyer.doFilterInternal(SessionContextDestroyer.java:136)
at wt.session.SessionContextDestroyer.doFilter(SessionContextDestroyer.java:184)
at wt.httpgw.FilterChainImpl.doFilter(FilterChainImpl.java:81)
at wt.httpgw.HTTPGatewayServlet.service(HTTPGatewayServlet.java:235)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:733)

...

4 REPLIES 4

I recommend you run remove unreferenced files from vault and select the choice to archive instead of delete so they can be restored if necessary. 

 

https://www.ptc.com/en/support/article/CS56539

avillanueva
22-Sapphire II
(To:ahoerl)

@SWeiler_9940261 tip is good. Strange that you had that issue. Was there a DB rollback or other issue? what should happen is that the file counter which makes the filename should continually advance forward. Its important to keep database and vaults in sync. If the database was ever behind the vaults, this can occur. 

Might also be worthwhile to open the file in the vault with a text editor to see what kind of a file it is. If it is a Creo file, it will have the CAD header and what not. then back up the file just in case it is still needed for some reason and wasn't saved elsewhere.

 

I probably wouldn't do a remove unreferenced files just yet because it is unnecessary to troubleshoot/fix this issue.

Thanks for the answers so far. I think what you described is indeed the cause of the problem. It occurs on a Windchill test instance created from a backup of the DB and Vault of the live instance, which can be out of sync with the way the backups are created right now. I guess this is also why any of the other proposed fixes (delete unreferenced files etc) did not work. I will press "Accept as Solution" on this post if the error does not persist the next time the server is started with a fresh (and properly synced) backup.

Announcements


Top Tags