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

Resolved PB 2022R3 not able to connect to SVN 2.1.5

  1. Issue
0
Votes
Undo
  1. Malek Taha
    Malek Taha
  2. PowerBuilder
  3. Saturday, 3 February 2024 16:57 PM UTC

Hi

   I have an svn repository version 2.1.5 running on Window server 2012 R2.

I created a repository for 2022R2 and have our application connected to it and all is good.

When i upgrade to 2022R3 it updated my 2022R3 Powerbuilder version and i no longer have the R2 version which worked fine.

WIth the 2022r3 version i cannot connect to my repository. 

Something to do with unsupported protocol

 

How do i revert to the R2 version?

 

or any advise on what need to be done to get support

Please advise I do not want to revert back to 2021

Thanks

Malek

pictures don't distribute in exe file
PB2022 R3 64bit does not appear to support MSOLEDB...
Responses (5)
kitty he @Appeon
kitty he @Appeon Accepted Answer Pending Moderation
  1. Monday, 5 February 2024 02:36 AM UTC
  2. PowerBuilder
  3. # 1

Hi Malek,

Your SVN server is on Server 2012R2. What operating system does your PB IDE run on? What is the specific error message?

 

Regards,

Kitty

Comment
There are no comments made yet.
Malek Taha
Malek Taha Accepted Answer Pending Moderation
  1. Monday, 5 February 2024 17:20 PM UTC
  2. PowerBuilder
  3. # 2

Hi Kitty

     The IDE is on Windows 10 Pro version 10.0.19045

Thanks for your help

Malek

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 6 February 2024 19:23 PM UTC
  2. PowerBuilder
  3. # 3

Hi Malek;

  I am not having any issues using SVN with my Apps in PB 2022 R2 or R3. However, I am using SVN version 5.3.2. I wonder if the issue is because you are on such an old version of SVN?

Setup ...

PB App ...

Log ...

24-02-06 14:18:51 INFO: SVN Get Lock
24-02-06 14:19:03 INFO: Locking file: C:\Dev\PB2022R3\CIPTest\ws_objects\ciptest.pbl.src\wn_encode_test.srw.
24-02-06 14:19:03 INFO: Locked by Chris.
24-02-06 14:19:04 INFO: SVN Get Lock completed.

HTH

Regards ... Chris

Comment
There are no comments made yet.
Malek Taha
Malek Taha Accepted Answer Pending Moderation
  1. Tuesday, 6 February 2024 20:45 PM UTC
  2. PowerBuilder
  3. # 4

Hi Chris

    Thanks for the response. There is definately something about 2022 R3 that is causing authentication issues with SVN

The same SVN repository i can connect to with no issues using PB2021 I was able to when i was using pb2022R2 After the upgrade to R3 Authentication fails. 

There may be some sort of access issue

I am stuck'

Please advise

Thanks

Malek Taha

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 6 February 2024 22:04 PM UTC
Hi Malek ;

I would suggest creating a Support Ticket for this issue so that one of our SCC specialists can advise you further.

https://www.appeon.com/standardsupport/search

Regards .. Chris
  1. Helpful
There are no comments made yet.
Malek Taha
Malek Taha Accepted Answer Pending Moderation
  1. Thursday, 8 February 2024 20:38 PM UTC
  2. PowerBuilder
  3. # 5

Hi all

    First i want to thank Chris, Kitty and all at appeon that helped with this issue.

It has been resolved for Us Thanks again

 

1) i uninstall 2022 R3 and reboot then i install 2222 R2 and reboot Then it all worked as before

2) We updated the SVN server to 5.3.2

3) we updated the Tortoise client to 1.14.3

4) then we added TLS 1.3 to the server

2022R3 worked fine after the upgrades

5) installed 2022 R3 and all worked fine

 

Issue Resolved

i believe the issue was with the ssl update

 

Thanks

again everyone for your help

Thanks

Malek Taha

 

 

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 8 February 2024 20:57 PM UTC
Hi Malek;

Thank you for the feedback & the great news!

You are most welcome. ;-)

Regards .. Chris
  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.