Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


calbzam last won the day on May 23

calbzam had the most liked content!

Community Reputation

62 Excellent

About calbzam

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

46,405 profile views
  1. Hi, As you comment, I'm afraid the users will need to manually upgrade. The auto-upgrade feature will only work if the client and server version are not actually compatible. If they are compatible (7.0.16.X), I'm afraid that the auto-upgrade feature will not work. Regards, Carlos.
  2. Hi again, In order to restart your local macOS server: https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide#Serverstartup sudo launchctl unload /Library/LaunchDaemons/com.codicesoftware.plasticscm.server.plist sudo launchctl load /Library/LaunchDaemons/com.codicesoftware.plasticscm.server.plist After that, the lock should be released. Regards, Carlos.
  3. Hi, We were not reported false positive issues specifically with Bitdefender in the past. We are going to report it to Bitdefender guys. We would appreciate if you do the same in the following link: https://www.bitdefender.com/support/what-to-do-when-bitdefender-detected-a-clean-file-as-infected-(false-positive)-851.html Regards, Carlos.
  4. Hi, If you restart your local Plastic server ("Plastic Server 6" under Windows services), is the issue still reproducible?The items may be locked for a few minutes due to this uncontrolled quit operation. Is the issue still reproducible today? In that case, we can try to manually release the lock in the cloud server. Regards, Carlos.
  5. Hi, are you paying customer? In that case, please reach us at support@codicesoftware.com so we can always assist you faster and even arrange a meeting session.Could you attach your "jet.conf"?Are your Jet databases stored at E:\? Could you create an "e:\jet" folder, move all the databases ("repositories", "rep_1", "rep_2"...) to the new location and edit the basepath in the "jet.conf" to the new location? You can check in the following link how to edit the jet database path: https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide#ConfigurePlasticSCMwithJet Finally, after editing the basepath, restart the Plastic server service and check if the issue persist.According to the error, it seems to be a problem with the path when the server tries to reach the databases. PD: If the issue is urgent, you can reach us at support@codicesoftware.comRegards,Carlos.
  6. You can remove/backup the file and when re-opening the GUI, a new clean "client.conf" will be created. Regards, Carlos.
  7. this issue is normally triggered by a lack of disk space when saving some changes. If you attach your file, we can try to fix it. Otherwise, you can remove/backup the file and re-configure the client again. It will automatically create a new "client.conf". Regards, Carlos.
  8. You can manually edit the ".plastic/plastic.selector" file to point to a branch and restart the GUI. eg: repository "MyProject@Myplasticlcoud@cloud" path "/" smartbranch "/main/Car Regards, Carlos.
  9. Hi, I think you may be affected by the following bug already fixed: [Bug] Windows - Visual Studio Package - Cloud Edition: The credentials dialog appeared every time you switch from using any Plastic GUI to Visual Studio plugin in Cloud Edition installations. Now it's fixed. Regards, Carlos.
  10. After deleting the "plastic.wktree", did you update your workspace? Note: As Pablo explained, your workspace selector needs to be pointing to a branch (not changeset). I don't understand why it doesn't work for you. You can always create a new local workspace and apply your changes in this new workspace. Regards, Carlos.
  11. Hi, 2. If the specific changeset id is not set, the workspace should be pointing to the head of the %BRACH%. Regards, Carlos.
  12. Hi, This is a local client configuration setting (not configurable on the server-side). By default, the "Pending changes" is not checking the file content (only the timestamp), because it would take a very long time in big workspaces with slow disks. Checking only the timestamp is very fast. Anyway, if you try to check in an item that appears as changed in "Pending changes" but the file content is actually the same (not changed), Plastic won't create a new file revision in the repository. Regards, Carlos.
  13. Hi, Is it possible that the file timestamp has changed? You can change this default behavior If you open the Plastic GUI --> Preferences --> Other options --> Check content to set a file as "Changed". Regards, Carlos.
  • Create New...