Error in PBG files when add to source control fails

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Create a new object
2. Configure SVN with pre-commit hook
3. User makes an "add to source control" operation and SVN rejects (comment 
don't contains issue number or whatever)

Output example:
---------- Source Control
Adding selected items to source control...
PBSCC Proxy : svn: Commit failed (details follow):
svn: Commit blocked by pre-commit hook (exit code 1) with output:
Access to SCC Provider failed during SccAdd(). Try again.
Failed to add C:\Mis Fuentes\Autonet11\dw_zzz.srd
Operation Completed
---------- Done Source Control

What is the expected output? What do you see instead?
Retry the operation with the comment corrected, PBSCC Proxy shows a warning 
saying the pbg file is locked by a user (user is the same who tried "add to 
source control")

---------- Source Control
Adding selected items to source control...
PBSCC Proxy : svn: warning: Path '/PB/trunk/mypbl.pbg' is already locked by 
user 'admin' in filesystem 'C:/csvn/data/repositories/repo/db'
Access to SCC Provider failed during SccCheckout(). Try again.
PBG Synch FAILED: C:\PB\mypbl.pbg
C:\PB\dw_zzz.srd version 811 successfully added to source control
Operation Completed
---------- Done Source Control

This problem causes the object to be added to repository but the file. PBG 
remains unchanged.

What version of the product are you using? On what operating system?
PBSCC Proxy 2.01.78
PB11.5 4740
Windows XP

Original issue reported on code.google.com by lmerrin on 6 Jul 2011 at 9:23

[GoogleCodeExporter]

we have the same issue, exactly the same, there is "some" solution for this 
bug? thnaks for the reply, sorry for my english

Original comment by joaspa...@gmail.com on 2 Jul 2012 at 3:37

[GoogleCodeExporter]

Please provide additional info:

- pbscc version number
- svn version
- lock strategy
- pbscc log file

Original comment by daggett....@gmail.com on 2 Jul 2012 at 9:12

[GoogleCodeExporter]

hi thanks for the quick answer
- pbscc version number  - 2.01.80
- svn version - 1.7
- lock strategy - lock.strategy=lock
- pbscc log file - sorry but i dont know where is the log file

the problem seems to only appears in power builder 9 we use 10 also and this 
issue dont appears

Original comment by joaspa...@gmail.com on 3 Jul 2012 at 2:17

[GoogleCodeExporter]

this doc describes how to create log file:
http://code.google.com/p/pbscc-proxy/wiki/Troubleshooting

Original comment by daggett....@gmail.com on 3 Jul 2012 at 5:43

[GoogleCodeExporter]

Same issue here.
- pbscc version number  - 2.01.80
- svn version - 1.8.1.62114
- TortoiseSVN 1.8.1, Build 24570 - 32 Bit , 2013/07/22 18:28:29
- lock strategy - lock.strategy=lock
- pbscc log file - see attachs

Original comment by wjat....@gmail.com on 23 Aug 2013 at 1:46

Attachments:

• pbscc120.log
• pbscc.zip

[GoogleCodeExporter]

I forget, my PB version is: 12.5.2 build 5550

Original comment by wjat....@gmail.com on 23 Aug 2013 at 1:48

[GoogleCodeExporter]

Hello,

We had worked normally with SVN and Tortoise 
- pbscc version number  - 2.01.80
- SVN Windows – Versión TortoiseSVN-1.6.12. 
- CollabNetSubversion-client-1.6.15-1
- PBuilder 11.5.1 Build 4011

Now, we updated the TortoiseSVN Version to 1.7.8 and CollabNet Client 1.7.6.

The problems is that now, the applications doesn´t connect to the repository 
and all objects appear as if they were new to the repository.

We need to update the Tortoise version because, we support at the same time 
others java systems that require this version of the repository (TortoiseSVN 
Version to 1.7.8).

Thanks for any information to help us to solve this problem.....

Original comment by andres.c...@ceiba.com.co on 27 Sep 2013 at 6:57