• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • TFS check-in would prompt a "Parameter is not valid"

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (5)

Resolved TFS check-in would prompt a "Parameter is not valid"

  1. Issue
0
Votes
Undo
  1. Song Tom
    Song Tom
  2. PowerBuilder
  3. Tuesday, 11 June 2019 02:38 AM UTC

recently our TFS 2012 want to migrate to MS devops 2019 to catch the latest DEVOPS trend, but seems only TFS 2013 explore and related scc plugin can support that,
but when we installed,  there is error message

*Phenomenon:
each check-in would prompt a  "Parameter is not valid" which lead to a fail
  
*Reproduce Steps:
1. download and install teamexplore 2013 and scc plugin (Visual Studio Team Foundation Server MSSCCI Provider (64-bit).msi)

2. create pb workspace  and connect to the DEVOPS server

3. add source code and make change then check-in, currently, this would be fine


4. check out code and make change again, and re-check in, error  "Parameter is not valid"


5. whatever check-in , error  "Parameter is not valid"  still prompt

Remarks:
can help us find a solution on that, our TFS SERVER is MS DEVOPS 2019 and TFS team explore client version 2013 with its SCCI 64BIT plugin

Use private font in PB application
PB 2021 SVN issues
Responses (5)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 11 June 2019 03:43 AM UTC
  2. PowerBuilder
  3. # 1

For a Git repository, which is what MS DevOps 2019 supports, you should be using the native Git interface of PB 2019 instead of the MSCCI interface.  The TortoiseGit client should interface with the Git repository, and PB 2019 has built-in support for the TortoiseGit client.  We kept the MSCCI interface in the product purely for backwards compatibility with older version control systems, such as TFVC.

Here are some links you may find useful:

https://docs.microsoft.com/en-us/azure/devops/user-guide/code-with-git?view=azure-devops

https://community.appeon.com/index.php/articles-blogs/tutorials-articles/2-powerbuilder/202-powerbuilder-2017-r3-new-feature-git-enhancements

https://community.appeon.com/index.php/articles-blogs/tips-tricks-techniques-articles/17-powerbuilder/227-tips-on-using-git-with-powerbuilder

https://community.appeon.com/index.php/articles-blogs/tips-tricks-techniques-articles/17-powerbuilder/238-working-with-branches-in-git

 

Comment
There are no comments made yet.
Song Tom
Song Tom Accepted Answer Pending Moderation
  1. Tuesday, 11 June 2019 05:13 AM UTC
  2. PowerBuilder
  3. # 2

Dear Armeen:

      Thanks your advice, The reason we use TFS is due to complexity on Git for PowerBuilder, The difficult two phrases of commit and push can often lead to a confusion,  and multiple user change in one pbl can always got error when push code; the handful thing is that we even cannot directly figure out whether local repository has been synced with the git server. so base on our friendly experience on TFS 2012 before, we have suggest our boss using TFS, but we are disappointed to get error like that, can help us to resolve it?  is there better way for source control on server and client mode can cater for the DEVOPS CI/CD trend？

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 11 June 2019 15:07 PM UTC
You can still use Git and enable file locking. If file locked then it should eliminate merge conflicts.
  1. Helpful
There are no comments made yet.
Song Tom
Song Tom Accepted Answer Pending Moderation
  1. Tuesday, 11 June 2019 13:14 PM UTC
  2. PowerBuilder
  3. # 3

I think maybe it is a small issue, whenever I restart the PB, the check-in would be fine, but it always fail after that during PB IDE open.

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 11 June 2019 15:06 PM UTC
Please open a support ticket. This does not sound like a configuration issue.
  1. Helpful
There are no comments made yet.
Rick Hiebert
Rick Hiebert Accepted Answer Pending Moderation
  1. Tuesday, 14 December 2021 15:41 PM UTC
  2. PowerBuilder
  3. # 4

My PB2019 and PB2021 just started having this issue. Was this ever resolved?

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 14 December 2021 16:59 PM UTC
Are you using Git repository?
  1. Helpful
Rick Hiebert
  1. Rick Hiebert
  2. Tuesday, 14 December 2021 17:08 PM UTC
No, Native TFS version control.

Was working in PB2019 for years, then last month I started getting the "Parameter is not valid" error. None of my coworkers are getting the error. I was hoping that when I migrated my application to PB2021 the error would be fixed, but it is there as well. And now that I think back, it was around the time I first installed PB2021 that the error started in PB2019. None of my coworkers have installed 2021 yet.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 14 December 2021 17:29 PM UTC
Appeon is not fixing or enhancing the old source control options. Microsoft has made Git is the default repository now for TFS. https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/comparison-git-tfvc?view=azure-devops

I would recommend migrating to Git. Microsoft has created a tool and instructions to help customers migrate: https://github.com/git-tfs/git-tfs/blob/master/doc/usecases/migrate_tfs_to_git.md

With that said, if worked fine for years and your TFVC version is the same as before, then chances are something got corrupted. Might be worthwhile to test from other computers to see specific to your machine.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Tuesday, 14 December 2021 20:02 PM UTC
  2. PowerBuilder
  3. # 5

I think your step 1. is wrong. You should install the 32 bit version, not the 64 bit. Let me know if you need it and I can upload it to my google drive.

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Tuesday, 14 December 2021 20:05 PM UTC
Your team explorer should also be 32 bit, not 64.
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Tuesday, 14 December 2021 20:05 PM UTC
(We don't use Devops, but on premises TFS server and everything works GREAT! ).
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.