Unable to launch Object Wizard from Agentry connector studio..

[Former Member]

Hi

I am trying a sampple exercise from Agentry Essentials. I am unable to launch the ObjectWizard from the Submenu ITem - AgentryConnectorStudio ->ObjectWizard option in the Data Source Explorer. I am connected to the sample NorthWind Database and am able to view the Orders Table on which I want to generate the Objects..

Any help from the Agentry experts is most welcome..

[Former Member]

What error are you seeing from the Data Source?

is the TCP\IP Port of the SQL Database set to Dynamic or set to 1433?

You can check this by going into "SQL Server Configuration manager" -> "SQL Server Network Configurations" -> "Protocols for XXXXXXX".  Here check to see if "TCP/IP" and "Named Pipes" is enabled.

Also, right click on "TCP/IP" and select "Properties" on the "IP Addresses" tab make sure all "TCP Dynamic Ports" are set to 0, and the "IPAll" section has "TCP Port" set to 1433

Stephen

[Former Member]

Steve

It wasnt a data connection issue more seemed to be a Agentry plugin pbm. Couldnt get the Object Wizard submenu item to be launched.. I manually created the steps wihtin the module so i guess its fine.. thanks for your suggestion.

[Former Member]

Hi Sriram,

I am facing the same issue and I am using work manager 5.3 application(which comes with Agentry sever 6.0).

i am using eclipse Indigo and editor plugin Agentry_6.0.22.0 ( downloaded from marketplace).

What can be the possible cause of this error?

Thanks,

Arihant

[Former Member]

Hi Arihant,

Is this still an issue ? If yes, I had similar issue. As Sriram wrote, I created a module first within the agentry perspective, then open the database development perspective. At this point, the object wizard would work.

HTH

Welly

[agentry_src]

Hi Sriram,

Please mark this Discussion with a Correct Answer and Helpful Answer where appropriate.  See http://scn.sap.com/community/support/blog/2013/04/03/how-to-close-a-discussion-and-why   Even if you discovered the solution without any outside contributions, it helps others to understand what the solution turned out to be.

Regards, Mike

SAP Customer Experience Group - CEG