cancel
Showing results for 
Search instead for 
Did you mean: 

Is there a way to test connection in the window "configuration proxy repository"

Former Member
0 Kudos

Hi,

I'am new in testing PowerDesigner (PowerAmc in French version). And right now, I'am testing the diffrent type of connection.

The installation: PowerDesigner with SQLAnywhere to hold the repository DB.

I make a lot of research to find answer of my problem but not very lucky and I'am planning to reinstall the proxy and mention my own data source OBDC and see...

My problem:.

The installation of the proxy was done by someone else following the instruction that come with the sofware.

But testing for the first time the connection with the proxy I receive a error when I try to connect saying " impossible to establish a connection to the proxy, proxy instance was no able to connect to data base, 28000 SQLSTATE OBDC Driver, id or password is incorrect"

So it mean the the proxy is not able to connect to the data base of the repository with id and password of the dba user. If I use that id and password of the dba but in a direct connection, it work. By the way, the connection with the web portal work too.

So in the window "configuration proxy repository" the data source mention must have a error.

My Question:

But where I can find that data source mention (the one that was created by the installation guy) and test it like we do in the data source created (OBDC) in direct access (repository definition)?  In the window, "configuration proxy repository" the mention in the user and password look ok to me.

Do you have other suggestions ?

I join 2 images (it in french but by the "look" I think you will understand)

Thank !

Accepted Solutions (1)

Accepted Solutions (1)

former_member192453
Active Participant
0 Kudos

You can launch the ODBC Administrator to test you DSN.

For Windows 64-bit:

C:\Windows\System32\odbcad32.exe

For Windows 32-bit:

C:\Windows\SysWOW64\odbcad32.exe

If you installed 64-bit Proxy, then use the 64-bit ODBC Administrator and 32-bit ODBC for a 32-bit proxy. Also, make sure that the DSN was created as a system DSN.

Anthony

Former Member
0 Kudos

Hi Anthony,

Thank for your fast respond. I appreciate your cooperation.

I did check on those aspects on the server (C:\Windows\SysWOW64\odbcad32.exe)  and If I create a data source ODBC with the Id and password of the Dba account. it work (connect) with no problem. Note that the password that I use has the same number of digits that show on the window "Configuration proxy repository" that the guy who has done the installation use, so it a good indication that the guy use the same Id (dba) and password.

But on the server, I cannot see the data source ODBC that is use in the configuration window of the proxy server in the field Data Source "SQL Anywhere 12 CustDB", this was created by the guy who has done the installation.

I'am not a DBA specialist but it seem to me that must be related to the problem. But  I'am thinking that the only way to know is to reinstall the proxy server myself and create my own date source ODBC.   

What do you think ?

Thank

Bernard   

former_member192453
Active Participant
0 Kudos

Hi Bernard,

Based on your description, it appears that an 'User DSN' was created. In the Repository Proxy Configuration window, only System DSNs will be available in the Data source field.

You reference using the 32-bit ODBC administrator, therefore I would do the following:

1) create a 32-bit System DSN

2) right-click on the pdproxyconf16.exe file and select Run As Administrator

3) select your System DSN for the Data source for your Proxy Instance and click Update

4) launch the PowerDesigner client and create a Repository Definition. Select Proxy for the Connection type.

5) enter the Proxy server name and Port. Then select an Instance Name.

You can then Test the connection

NOTE: If a 64-bit instance of the Proxy Server was installed, you will need to create a 64-bit System DSN in step 1. You can then follow the remaining steps.

Regards,

Anthony

Former Member
0 Kudos

Hi Anthony,

You solve the problem. Sorry for the delay to answer you back.

I did re-check it again and find out there was a User DSN and System DSN. But he System DSN was not configure the right way. In the past, the person who did make those DSN must have make some test but did not have "completed" his work so I didn't have that information when I take over the situation, that why it was so confusing. Well,  it always better to double ckeck ourself. 

So the access with the proxy is working fine.

So thank again. I appreciate a lot.

Bernard

Answers (0)