Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ProjectWise
  • Product Communities
ProjectWise
ProjectWise Design Integration Forum Error changing document file
    • Sign In

    • State Not Answered
    • +2 person also asked this people also asked this
    • Replies 5 replies
    • Subscribers 65 subscribers
    • Views 1409 views
    • Users 0 members are here

    Error changing document file

    Luc Poulin
    Offline Luc Poulin over 2 years ago

    Anyone familiar with this error message

    ProjectWise error 59054

    Error changing document file

    An existing connection was closed by the remote host

    Seems I have this error with only one user but cannot pin point the reason.

    This happen when we drag a file from explorer to ProjectWise, user is being ask to create a new version.  Then somewhere in the transfer we get the error message above.

    • Sign in to reply
    • Cancel
    Parents
    • Goda Kutkeviciute
      0 Offline Goda Kutkeviciute Wed, Jul 28 2021 9:55 AM

      Hi Luc,

      I would suggest filling Service Request as to investigate this issue detailed Server and Client-side logs will be required to be collected. I would suggest including the file size of the document when filling the Service Request.

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Luc Poulin
      0 Offline Luc Poulin Wed, Jul 28 2021 3:47 PM in reply to Goda Kutkeviciute

      OK thank you

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Randy Roethle
      0 Offline Randy Roethle Tue, Aug 2 2022 12:53 PM in reply to Luc Poulin

      Hello, curious if a solution was ever found.  I have a member who is experiancing the same issue when trying to save to a PW folder from a local drive. Thank you for any information you can provide!

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Christopher Macsurak
      0 Offline Christopher Macsurak Wed, Nov 16 2022 6:30 PM in reply to Randy Roethle

      Hello, any news? I've got a user getting the same error: 

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Luc Poulin
      0 Offline Luc Poulin Thu, Nov 17 2022 8:48 AM in reply to Luc Poulin

      Hello All

      Sorry never get back on this one

      We manage to get around but can't remember exactly the steps.

      I believe I had to recreate this area and the document version history

      I vaguely recall few things:

      1) we had a file on the server, but no document where showing under PW

      2) Verson exist, but had different name. Like V1 had a document name 123 and V3 ad a document name 456. It is like someone had rename a document after the version was create.

      3) we had a not recognize character in the name something like " ; " or " . " etc.... We still have project that enter a long description in the document name.

      One way to investigate, copy the initial version of the document to a different folder having similar security. Then copy the next version and recreate the version history. Then drag your latest version and see if you have the same problem. This will help narrow down.

      You can as well drop the lates version alone in a folder with similar security to see if the same error popup. 

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    Reply
    • Luc Poulin
      0 Offline Luc Poulin Thu, Nov 17 2022 8:48 AM in reply to Luc Poulin

      Hello All

      Sorry never get back on this one

      We manage to get around but can't remember exactly the steps.

      I believe I had to recreate this area and the document version history

      I vaguely recall few things:

      1) we had a file on the server, but no document where showing under PW

      2) Verson exist, but had different name. Like V1 had a document name 123 and V3 ad a document name 456. It is like someone had rename a document after the version was create.

      3) we had a not recognize character in the name something like " ; " or " . " etc.... We still have project that enter a long description in the document name.

      One way to investigate, copy the initial version of the document to a different folder having similar security. Then copy the next version and recreate the version history. Then drag your latest version and see if you have the same problem. This will help narrow down.

      You can as well drop the lates version alone in a folder with similar security to see if the same error popup. 

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    Children
    No Data

    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies