Error 'not registered to run'

[sue]

Hi,

 

I have a business operation wich gives the following error when we try to execute it.

 

ERROR <Ens>ErrBusinessDispatchNameNotRegistered: Business dispatch name 'CaMISGetUniversalNo' is not registered to run

 

Any one know what it means and how I can fix it?

 

The version in the test namespace works  fine.

 

Thanks

 

Sue

[Crístofer Mateos Vicente]

Hi,

I have just had the exact same problem. In my case, I had changed the name of the BS in the production and, since then, this error started to appear. I solved it by changing the name of the BS component with the exact same of the service class. For example, if the class is services.test.CaMISGetUniversalNo, you cannot use just CaMISGetUniversalNo as the name of the BS in your production, it must be services.test.CaMISGetUniversalNo.

I don't know the reason why this happens... It would be nice if anyone could explain it a little.

Regards,

[David Blake]

Hi Sue

 

This error occurs when the host name specified in a call does not exist. In your case, and this is quite common, the call would have been specifying the classname and not the host name.

 

So you will have a CallRequest method somewhere which now specifies the classname which is why changing the host name to the classname worked. If you would like to change the name of your host back, you will need to find the call and change the name to be that of the host.

 

Hope this helps

 

Dave

--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to Ensemble-in...@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healt...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en
---
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Ensemble-in-Healt...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Crístofer Mateos Vicente]

Another option that has worked for me is invoking the service using the inboundAdapter port, instead of the CSPGateway one.

Example:

http://localhost:1980/csp/namespace/services.test.CaMISGetUniversalNo.cls (works)

http://localhost:75552/csp/namespace/services.test.CaMISGetUniversalNo.cls (does not work)

[Dale du Preez]

As a further note on this, the reason this occurs is because a number of settings are defined at the production level, so Ensemble needs to know which settings to apply to your business service, and not only the class name.

In recent versions we support having multiple services that use the same class but different settings, in which case which business service you call can make a big difference to the way the request is handled and processed.

I hope that helps to shed some light on why there is this extra layer between the class and what Ensemble allows you to call.

Dale

[Crístofer Mateos Vicente]

By 75552 I meant 57772, just for the record :P

[David Blake]

Sue

 

Small correction. Now that I’ve re-read it, I see it was a service name that you have the issue with.

 

In that case, are you invoking it somewhere with CreateBusinessService()? It will perform the same check; I.e. that the dispatch name has an associated host.

 

On a technical level, it checks that ^Ens.Runtime(“DispatchName”,<dispatch name>) exists and uses the data from this node as the config name for the call.

 

Dave

 

From: Ensemble-in...@googlegroups.com [mailto:Ensemble-in...@googlegroups.com] On Behalf Of Crístofer Mateos Vicente
Sent: 01 April 2015 16:40
To: Ensemble-in...@googlegroups.com
Subject: [InterSystems-EnsHlth] Re: Error 'not registered to run'

 

Another option that has worked for me is invoking the service using the inboundAdapter port, instead of the CSPGateway one.

--

[sue]

Hi Everyone,

 

Thanks for the responses,

 

We found an typo in the BPL which called the BO and we hope that will fix it. Unfortunately the process has not had to call the BO since we made the change so I cannot say for certain that it is fixed yet. However it sounds a similar issue to the ones you have mentioned with the name.

 

Regards

Sue

To post to this group, send email to Ensemble-i...@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healthcare-unsub...@googlegroups.com

For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en
---
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare" group.

To unsubscribe from this group and stop receiving emails from it, send an email to Ensemble-in-Healthcare+unsub...@googlegroups.com.

[Conor B]

I have gotten that error many times when developing new code. Restarting the production does not fix the issue but for some reason restarting the individual component causes this error to disappear.

[Conor B]

I came across this error again today and it was because a target in a routing rule did not exist.

<send transform=".DTL.Outbound.ADT.A02" target="ToNoWhere"></send>

Seems like the error can occur it different ways ...