Problem with pb11 and scc pb native. impossible to open a workspace
jc
I have not a problem to open any workspace. Chek in/ Check out OK.
But my colleague, when he opening only workspace with 2 targets, he receive
this message:
Connection to source control established
Refreshing source control status ...........
That's all! He not receive the message "Source control is ready".
He wait 5, 10, 30 minutes and nothing.
Impossible for hem to open this workspace. But queerly, sometimes it's OK.
Without source control, he have'nt never problems.
he have already reinstall PB11 and no change.
I have not a problem with this workspace.
Help!
Thank's
JCC
Paul Horan[TeamSybase]
- Problems with the SCC integration;
- It happens on one machine but not all machines;
- It happens at seemingly random times;
Check for duplicate PB*.DLL files somewhere on the offending machine.
Paul Horan[TeamSybase]
"jc" <jc.cu...@mouscron.be> wrote in message news:477cc7b3@forums-1-dub...
jc
The duplicate PB*.DLL already verified.
This problem is with one and only one workspace, not all workspaces.
After creation a new workspace with same 2 targets, always the same problem.
I have'nt problem but my colleague have always the problem.
No response of PB after refreshing source control status message. It happens
random times.
New information:
My colleague can reproduce the problem.
If he open the workspace with only the library list open then always the
same problem with only this workspace.
If he open this workspace with the system-tree window open then no problems.
If he open this workspace with system-tree window and library list open then
no problems.
If he open this workspace without system-tree window and library list then
no problems.
It's really strange!
And i repeat only one workspace, no with others worspaces.
And me, no problem with all workspaces.
Have you an idea?
Thank's
"Paul Horan[TeamSybase]" <phoran AT sybase DOT com> a écrit dans le message
de news: 477cfe00$1@forums-1-dub...
Paul Horan[TeamSybase]
which SCC provider are you using?
Paul Horan[TeamSybase]
"jc" <jc.cu...@mouscron.be> wrote in message
news:477e0509$1@forums-1-dub...
jc
SCC: PB Native
"Paul Horan[TeamSybase]" <phoran AT sybase DOT com> a écrit dans le message
de news: 477e37bf$1@forums-1-dub...
Paul Horan[TeamSybase]
Does each developer have a complete set of the PBLs on their local machine,
and is the PBNative project folder is located out on a shared LAN drive?
Paul Horan[TeamSybase]
"jc" <jc.cu...@mouscron.be> wrote in message news:477e5837@forums-1-dub...
jc
development server.(local root directory on the properties of workspace)
No the complete set of PBLs on the local machine of each developer.
The project is located on the other shared LAN Drive on this same
development server. (Project on the properties of workspace)
We are the newbies with PBNative.
Each developer must have a complete set of the PBLs? It's necessary?. The
PBLs on a shared drive it's an error?
Thank's
JCC
"Paul Horan[TeamSybase]" <phoran AT sybase DOT com> a écrit dans le message
de news: 477ea4c2$1@forums-1-dub...
Roland Smith [TeamSybase]
a network drive that is their personal share.
The 'Project' directory should be located on a shared network drive.
When developer A does a check in, all other developers will do a 'Get Latest
Version'. This copies the updated object down to their personal copy.
Paul Horan[TeamSybase]
separate set of PBLs. This is true for any SCC provider, not just PBNative.
Paul Horan[TeamSybase]
"jc" <jc.cu...@mouscron.be> wrote in message news:4781e892@forums-1-dub...
jc
shared drive and no problem for check in/check out.
Why for each developer? It's absolutly necessary?
"Paul Horan[TeamSybase]" <phoran AT sybase DOT com> a écrit dans le message
de news: 47822bd7$1@forums-1-dub...
Paul Horan[TeamSybase]
your "work" PBL, which isolated your work from that of your co-developers.
Starting with PB8, you check objects out "in place". They don't go
anywhere. So your work-in-progress is immediately seen by your colleagues
as soon as you click SAVE. This violates one of the basic concepts of
source code management, in which MY changes are isolated from the active
code branch until I specifically check them in (or merge them, as in the
case of CVS, SubVersion, etc).
You can achieve this with shared PBLs, as long as each developer has a
separate "work" PBL of their very own. You'd check the object out "in
place" from the shared PBL on the LAN, manually copy it into the work PBL,
edit/debug it there, then at checkin time, you'd have to copy the revised
object back into its "home" PBL and perform the checkin. This would save
the other team members from ever having to do a "get latest version", but I
can't recommend it. Disk space is cheap - give everyone their own set of
PBLs and solve all your problems. Then get a separate machine that only
does GLVs and performs the build.
Paul Horan[TeamSybase]
"jc" <jc.cu...@mouscron.be> wrote in message
news:47835b6b$1@forums-1-dub...
Jeremy Lakeman
> Hello,
>
> The duplicate PB*.DLL already verified.
> This problem is with one and only one workspace, not all workspaces.
> After creation a new workspace with same 2 targets, always the same problem.
> I have'nt problem but my colleague have always the problem.
> No response of PB after refreshing source control status message. It happens
> random times.
>
> New information:
> My colleague can reproduce the problem.
> If he open the workspace with only the library list open then always the
> same problem with only this workspace.
> If he open this workspace with the system-tree window open then no problems.
> If he open this workspace with system-tree window and library list open then
> no problems.
> If he open this workspace without system-tree window and library list then
> no problems.
> It's really strange!
> And i repeat only one workspace, no with others worspaces.
> And me, no problem with all workspaces.
>
> Have you an idea?
>
> Thank's
Hmmm, I'd check for other pb dll's or perhaps other dll's that are
confusing your source control system in the same folder as the
workspace file.
My guess is, the difference between when it works, and when it doesn't
is the current directory of the IDE. If you open a file browse dialog
to open the workspace your current directory will change. If the IDE
(or source control system) then attempts to load a dll for the first
time and that dll exists in the current folder it will be loaded
instead.
I had some weird problems once when I started PB with a current
directory that included a different version of the pb runtimes. This
might be similar.
jc
the same workspace.
"Paul Horan[TeamSybase]" <phoran AT sybase DOT com> a écrit dans le message
de news: 4783811e$1@forums-1-dub...
Ronny Plontke
jc schrieb:
> We have a problem with PB Enterprise and the source control.
> I have not a problem to open any workspace. Chek in/ Check out OK.
> But my colleague, when he opening only workspace with 2 targets, he receive
> this message:
>
> Connection to source control established
> Refreshing source control status ...........
>
We have the same problem with PB 10.5.2. In PB 10.2.1 SCC was
working fine.
The crash happens randomly. We have also checked for double
DLLs, but everything seems to be ok (especially with pbnat105.dll).
I have no idea where it comes from. Apparently it is not occuring
on all machines. Wich OS do you use?
Regards
Ronny
Andreas Holz
After deleting the registry key
HKCU\Software\Sybase\Powerbuilder\10.5\Layout
I was able to reconnect to the PBNative Repository properly.
Andreas
Ronny Plontke schrieb:
Andreas Holz
Andreas Holz schrieb:
