CreateInstance Error in PB 12.5.2 & Easerver 6.3.1 : 50 Distributed service error

[Former Member]

Hi,

I have migrated a PB 10.5 client server application to PB 12.5.2 and deployed all the server components to fresh Easerver 6.3.1installation successfully.

Now when I am trying to run the application I am getting the error as 50 Distributed service error when the Createinstance is being called. I can not get PowerBuilder 12.5.2 to create instances of easerver components.

The same code works perfectly in PB 10.5

As a solution suggested earlier in this forum I have also installed the PBVM 12.5 in easerver installation folder to deploy the easerver components and can see the PBVM115.DLL and PBVM125.DLL available to support the application to run in the latest PB, but didn't find any solution for it. Let me know if any one have come through such issue earlier and and found any resolution for it.

Here is the sample code that runs when the application tries to login into the application screen. The connections to the server are fine and when it tries to create the instance of the easerver component object(n_accesscontrol) the distributed server error pops.

Sample Code:

n_accesscontrol lnv_accesscontrol

ll_ret = g_connection.CreateInstance( lnv_accesscontrol,"accesscontrol/n_accesscontrol" )

    if ( ll_ret <> 0 ) then

        l_login.status = 0

        l_fe = create n_fatal_ex

        l_fe.setmessage( "CreateInstance (n_accesscontrol) error " + string( ll_ret ) )

        throw l_fe

    end if

Regards,

Kunal

[Former Member · Accepted solution]

Hi  Kunal ;

1) Is the IDL formed OK for the component?

   - check in the EAS Console

2) Did you rebuild the PB proxy objects from EAS 6.3 after deployment so that the v12.5 ones are generated (replacing the v10.5 ones).

3) Anything more in the EAS logs?

Regards ... Chris

[Former Member · Accepted solution]

Hi Chris,

1. Yes I could see the IDL for the component that have been deployed. I have rechecked it in the console under the IDL Module.

2) Did you rebuild the PB proxy objects from EAS 6.3 after deployment so that the v12.5 ones are generated (replacing the v10.5 ones).

Are there any way to rebuild the PB proxy objects from EAS 6.3 after deployment ?

I am not sure how the PB proxy objects can be rebuild from the EAS 6.3, although I have rebuild the proxy projects and objects of the client and easerver target components.

Are you talking about the STUB generation for the component ?

For ref. here is the log that I can see. The log text in bold points to the component for which I am getting the error as of now.

2013-07-18 13:56:44.034 INFO  Thread-85 [SystemException] com.sybase.djc.repository.PropertiesNotFoundException was thrown by method com.sybase.jaguar.server.JaguarServer.iiopHandler

2013-07-18 13:56:44.034 INFO  Thread-85     com.sybase.djc.repository.PropertiesNotFoundException: C:\Program Files (x86)\Sybase\EAServer6\Repository\Instance\com\sybase\djc\util\DjcClassLoader\ejb.components.accesscontrol.properties

2013-07-18 13:56:44.034 INFO  Thread-85         at com.sybase.djc.repository.Repository.getProperties(Repository.java:1057)

2013-07-18 13:56:44.034 INFO  Thread-85         at com.sybase.djc.repository.Repository.getProperties(Repository.java:437)

2013-07-18 13:56:44.034 INFO  Thread-85         at com.sybase.djc.repository.Repository.getProperties(Repository.java:422)

2013-07-18 13:56:44.034 INFO  Thread-85         at com.sybase.djc.util.DjcClassLoader.getInstance(DjcClassLoader.java:201)

2013-07-18 13:56:44.034 INFO  Thread-85         at com.sybase.djc.util.ThreadContext.activateClassLoaderFor(ThreadContext.java:132)

2013-07-18 13:56:44.034 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl.createRef(SessionImpl.java:157)

2013-07-18 13:56:44.034 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl.lookup(SessionImpl.java:85)

2013-07-18 13:56:44.034 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl_DJC.lookup(SessionImpl_DJC.java:273)

2013-07-18 13:56:44.034 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl_DJC.$invoke(SessionImpl_DJC.java:98)

2013-07-18 13:56:44.034 INFO  Thread-85         at com.sybase.jaguar.server.JaguarServer.iiopHandler(JaguarServer.java:293)

2013-07-18 13:56:44.034 INFO  Thread-85         at com.sybase.jaguar.server.RequestHandler.processRequest(RequestHandler.java:9)

2013-07-18 13:56:44.034 INFO  Thread-85         at com.sybase.djc.rmi.iiop.server.MessageHandler.processRequest(MessageHandler.java:651)

2013-07-18 13:56:44.034 INFO  Thread-85         at com.sybase.djc.rmi.iiop.server.MessageHandler.run(MessageHandler.java:352)

2013-07-18 13:56:44.034 INFO  Thread-85         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)

2013-07-18 13:56:44.034 INFO  Thread-85         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)

2013-07-18 13:56:44.034 INFO  Thread-85         at java.lang.Thread.run(Thread.java:595)

2013-07-18 13:56:48.454 INFO  Thread-85 [SystemException] com.sybase.djc.repository.PropertiesNotFoundException was thrown by method com.sybase.jaguar.server.JaguarServer.iiopHandler

2013-07-18 13:56:48.454 INFO  Thread-85     com.sybase.djc.repository.PropertiesNotFoundException: C:\Program Files (x86)\Sybase\EAServer6\Repository\Instance\com\sybase\djc\util\DjcClassLoader\ejb.components.accesscontrol.properties

2013-07-18 13:56:48.454 INFO  Thread-85         at com.sybase.djc.repository.Repository.getProperties(Repository.java:1057)

2013-07-18 13:56:48.454 INFO  Thread-85         at com.sybase.djc.repository.Repository.getProperties(Repository.java:437)

2013-07-18 13:56:48.454 INFO  Thread-85         at com.sybase.djc.repository.Repository.getProperties(Repository.java:422)

2013-07-18 13:56:48.454 INFO  Thread-85         at com.sybase.djc.util.DjcClassLoader.getInstance(DjcClassLoader.java:201)

2013-07-18 13:56:48.454 INFO  Thread-85         at com.sybase.djc.util.ThreadContext.activateClassLoaderFor(ThreadContext.java:132)

2013-07-18 13:56:48.454 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl.createRef(SessionImpl.java:157)

2013-07-18 13:56:48.454 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl.lookup(SessionImpl.java:85)

2013-07-18 13:56:48.454 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl_DJC.lookup(SessionImpl_DJC.java:273)

2013-07-18 13:56:48.454 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl_DJC.$invoke(SessionImpl_DJC.java:98)

2013-07-18 13:56:48.454 INFO  Thread-85         at com.sybase.jaguar.server.JaguarServer.iiopHandler(JaguarServer.java:293)

2013-07-18 13:56:48.454 INFO  Thread-85         at com.sybase.jaguar.server.RequestHandler.processRequest(RequestHandler.java:9)

2013-07-18 13:56:48.454 INFO  Thread-85         at com.sybase.djc.rmi.iiop.server.MessageHandler.processRequest(MessageHandler.java:651)

2013-07-18 13:56:48.454 INFO  Thread-85         at com.sybase.djc.rmi.iiop.server.MessageHandler.run(MessageHandler.java:352)

2013-07-18 13:56:48.454 INFO  Thread-85         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)

2013-07-18 13:56:48.454 INFO  Thread-85         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)

2013-07-18 13:56:48.454 INFO  Thread-85         at java.lang.Thread.run(Thread.java:595)

Regards,

Kunal.

[Former Member · Accepted solution]

It looks like a problem with the EAS set-up. Can you create a simple object with a "hello world" function (just returns a known string) and test that first. If that dies not work then you need to look at your EAS installation.

[Former Member · Accepted solution]

For #2 ...

   You would build a new Project in your PB application using the EJB Client Proxy option ....

  After you deploy your PB NVUO's to EAS 6.x - you would then run this project to re-create the client side proxies from the EAS's IDL. This will populate proxy objects into a PBL of your choosing when this project executes.

Regards ... Chris

[Former Member · Accepted solution]

Hi Chris,

I tried the way you have suggested above, Infact initialy I deployed the PB NVUO'S through the server proxy projects created earlier(migrated) and then run the client side proxy project to create the client side proxy from EAS's IDL.

Just to recheck I created the new NVUO and created a new proxy server project and deployed this component and then created the client proxy and changed the code to read the instance of this new object but it gave the same error.

I have figured out the missing components (which all I have deployed) in the EJB MODULE in management console but they are available under the CORBA  Packages.

Does all the components should be also available under the EJB Module ?

In my last server configuration I migrated a web service PB application where the deployed components were available under both headings( CORBA Packages & EJB Module) in management console and that application works fine on latest server 6.3.1.

Also I deployed the same components(few) in the already configured and running server on 6.3.1 and found that this component reflects on CORBA Packages and EJB Module after deployment which is not the case with the recent configured server. I am not sure if all the deployed components should be available at both the headers, but the earlier configured server works fine and my web application runs smoothly on it. So it can be possible that there may be configuration issue that I have done recently ? Any suggestion

Regards,

Kunal

[Former Member · Accepted solution]

Hi Kunal;

   Yes, it sounds like you might have a bad EAS installation. You might want to uninstall the non-working EAS, reboot and try another install. If you do - make sure that you select a full installation during the set-up.

Regards ... Chris

[Former Member · Accepted solution]

Hi Chris,

Thanks, I will reinstall the Easerver and test the same again.

To confirm again, I created a small test application in PB 12.5.2 and 10.5(earlier version which runs for easerver 5.5 for my existing appl.) which returns a string for successful connection and deployed the components to 6.3.1 installation but both test application in different version failed to create the instance. At the same time I again deployed the component from PB 12.5.2 & PB 10.5  in easerver 5.5 and I could get the successfull conection return from EAServer 5.5. This pretty clears that there is some issue with the 6.3.1 easerver installer.

Let me know if you have any suggestion for installation apart from full installation of server w.r.t the instance creation.

Regards,

Kunal

[Former Member · Accepted solution]

Hi David,

As you suggested earlier, I created a small test application in PB 12.5.2 and 10.5(earlier version which runs for easerver 5.5 for my existing appl.) which returns a string for successful connection and deployed the components to 6.3.1 installation but both test application in different version failed to create the instance. At the same time I again deployed the component from PB 12.5.2 & PB 10.5  in easerver 5.5 and I could get the successful connection return from EAServer 5.5. This pretty clears that there is some issue with the 6.3.1 easerver installer.

Let me know if you have any suggestion for me as a part of installation that would fix the issue of creating the instance of the components in easerver 6.3.1.

Regards,

Kunal

[Former Member · Accepted solution]

If you cannot get a "Hello World" function to work then un-install, delete registry entries and re-install.

It probably does not matter, but we always change the directory to one with no spaces in the name. Old habits die hard.

Hopefully that will fix your issue.

[Former Member · Accepted solution]

Hi Chris\David,

Re-installation of EAServer solved the problem for me and I am not getting any instance error now.

Appreciate your valuable time and suggestions that helped me to dig the issue and resolve it.

Thanks & regards,

Kunal Kumar

[Former Member]

Error 50 is a generic error, there should be more information in error logs. can you supply any other information?

When you installed the PB12.5 VM did you run the installer?

Cheers

David

[Former Member]

Hi David,

Are you talking about the PBVM installer ? if yes then I have run the installer to install the PBVM which installed the run time files in EAServe6\powerbuilder repository and also in the Sybase\Shared folder.

Here is the log that I can see created when I hit the application and the code tries to create instance for the component accesscontrol\n_accesscontrol. The log indicates about the same component(in bold) that my code is trying to create the instance.

2013-07-18 13:21:09.331 INFO  Thread-85 [SystemException] com.sybase.djc.repository.PropertiesNotFoundException was thrown by method com.sybase.jaguar.server.JaguarServer.iiopHandler

2013-07-18 13:21:09.331 INFO  Thread-85     com.sybase.djc.repository.PropertiesNotFoundException: C:\Program Files (x86)\Sybase\EAServer6\Repository\Instance\com\sybase\djc\util\DjcClassLoader\ejb.components.accesscontrol.properties

2013-07-18 13:21:09.331 INFO  Thread-85         at com.sybase.djc.repository.Repository.getProperties(Repository.java:1057)

2013-07-18 13:21:09.331 INFO  Thread-85         at com.sybase.djc.repository.Repository.getProperties(Repository.java:437)

2013-07-18 13:21:09.331 INFO  Thread-85         at com.sybase.djc.repository.Repository.getProperties(Repository.java:422)

2013-07-18 13:21:09.331 INFO  Thread-85         at com.sybase.djc.util.DjcClassLoader.getInstance(DjcClassLoader.java:201)

2013-07-18 13:21:09.331 INFO  Thread-85         at com.sybase.djc.util.ThreadContext.activateClassLoaderFor(ThreadContext.java:132)

2013-07-18 13:21:09.331 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl.createRef(SessionImpl.java:157)

2013-07-18 13:21:09.331 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl.lookup(SessionImpl.java:85)

2013-07-18 13:21:09.331 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl_DJC.lookup(SessionImpl_DJC.java:273)

2013-07-18 13:21:09.331 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl_DJC.$invoke(SessionImpl_DJC.java:98)

2013-07-18 13:21:09.331 INFO  Thread-85         at com.sybase.jaguar.server.JaguarServer.iiopHandler(JaguarServer.java:293)

2013-07-18 13:21:09.331 INFO  Thread-85         at com.sybase.jaguar.server.RequestHandler.processRequest(RequestHandler.java:9)

2013-07-18 13:21:09.331 INFO  Thread-85         at com.sybase.djc.rmi.iiop.server.MessageHandler.processRequest(MessageHandler.java:651)

2013-07-18 13:21:09.331 INFO  Thread-85         at com.sybase.djc.rmi.iiop.server.MessageHandler.run(MessageHandler.java:352)

2013-07-18 13:21:09.331 INFO  Thread-85         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)

2013-07-18 13:21:09.331 INFO  Thread-85         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)

2013-07-18 13:21:09.331 INFO  Thread-85         at java.lang.Thread.run(Thread.java:595)

2013-07-18 13:21:14.903 INFO  Thread-85 [SystemException] com.sybase.djc.repository.PropertiesNotFoundException was thrown by method com.sybase.jaguar.server.JaguarServer.iiopHandler

2013-07-18 13:21:14.903 INFO  Thread-85     com.sybase.djc.repository.PropertiesNotFoundException: C:\Program Files (x86)\Sybase\EAServer6\Repository\Instance\com\sybase\djc\util\DjcClassLoader\ejb.components.accesscontrol.properties

2013-07-18 13:21:14.903 INFO  Thread-85         at com.sybase.djc.repository.Repository.getProperties(Repository.java:1057)

2013-07-18 13:21:14.903 INFO  Thread-85         at com.sybase.djc.repository.Repository.getProperties(Repository.java:437)

2013-07-18 13:21:14.903 INFO  Thread-85         at com.sybase.djc.repository.Repository.getProperties(Repository.java:422)

2013-07-18 13:21:14.903 INFO  Thread-85         at com.sybase.djc.util.DjcClassLoader.getInstance(DjcClassLoader.java:201)

2013-07-18 13:21:14.903 INFO  Thread-85         at com.sybase.djc.util.ThreadContext.activateClassLoaderFor(ThreadContext.java:132)

2013-07-18 13:21:14.903 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl.createRef(SessionImpl.java:157)

2013-07-18 13:21:14.903 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl.lookup(SessionImpl.java:85)

2013-07-18 13:21:14.903 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl_DJC.lookup(SessionImpl_DJC.java:273)

2013-07-18 13:21:14.903 INFO  Thread-85         at com.sybase.jaguar.server.SessionImpl_DJC.$invoke(SessionImpl_DJC.java:98)

2013-07-18 13:21:14.903 INFO  Thread-85         at com.sybase.jaguar.server.JaguarServer.iiopHandler(JaguarServer.java:293)

2013-07-18 13:21:14.903 INFO  Thread-85         at com.sybase.jaguar.server.RequestHandler.processRequest(RequestHandler.java:9)

2013-07-18 13:21:14.903 INFO  Thread-85         at com.sybase.djc.rmi.iiop.server.MessageHandler.processRequest(MessageHandler.java:651)

2013-07-18 13:21:14.903 INFO  Thread-85         at com.sybase.djc.rmi.iiop.server.MessageHandler.run(MessageHandler.java:352)

2013-07-18 13:21:14.903 INFO  Thread-85         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)

2013-07-18 13:21:14.903 INFO  Thread-85         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)

2013-07-18 13:21:14.903 INFO  Thread-85         at java.lang.Thread.run(Thread.java:595)

Regards,

Kunal