# SMH error - modify Default Message Properties

**URL:** <https://techcommunity.softwareag.com/t/smh-error-modify-default-message-properties/59604>\
**Category:** Forum\
**Tags:** Former-Crossvision-Products, Service-Orchestrator\
**Created:** [March 11, 2006, 7:29am UTC](https://techcommunity.softwareag.com/t/smh-error-modify-default-message-properties/59604 "2006-03-11T07:29:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![arp](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@arp](https://techcommunity.softwareag.com/u/arp)\
**Post date:** [March 11, 2006, 7:29am UTC](https://techcommunity.softwareag.com/t/smh-error-modify-default-message-properties/59604/1 "2006-03-11T07:29:21Z")

</div>

Hi all;

I’m getting the following error when trying to modify the default message properties of a component factory via the System Management Hub interface:

“com.softwareag.xbridge.exceptions.XException : Version Mismatch : Agent Version : Mediator Runtime Version : 7.4.2.2”

I’ve received the same error before applying the latest patch - that is, with version 7.4.2.0

For now I have to modify the Default Message Properties directly in the hostconfig.xml - not really an optimal solution.

The server in question is Windows 2003 Standard, also running Tamino 4.4.1 and JDK is 1.4.2.10.

best regards,

- arp

---

<div class="post-metadata">

**Author:** ![arp](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@arp](https://techcommunity.softwareag.com/u/arp)\
**Post date:** [March 22, 2006, 10:21am UTC](https://techcommunity.softwareag.com/t/smh-error-modify-default-message-properties/59604/2 "2006-03-22T10:21:41Z")

</div>

Well… this one will have to be filed under T for ‘Twilight Zone’ …

Having renamed the machine running mediator, I changed the XBD settings referring to the host name (in the setMediatorEnvironment.bat, windows registry etc…) and got everything running without reinstalling.  
And magically I can now modify my default message properties via SMH…

I suppose the reason was a rogue setting somewhere, however can’t shed any more light on this.

- arp

---

<div class="post-metadata">

**Author:** ![arp](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@arp](https://techcommunity.softwareag.com/u/arp)\
**Post date:** [July 29, 2006, 1:54pm UTC](https://techcommunity.softwareag.com/t/smh-error-modify-default-message-properties/59604/3 "2006-07-29T13:54:00Z")

</div>

Still not sure what the issue was, but moving to Service Orchestrator 3.1 seems to solve the problem.

regards,

- arp

---

<div class="post-metadata">

**Author:** ![Jay2](https://avatars.discourse-cdn.com/v4/letter/j/a6a055/32.png) [@Jay2](https://techcommunity.softwareag.com/u/Jay2)\
**Post date:** [August 16, 2006, 6:05am UTC](https://techcommunity.softwareag.com/t/smh-error-modify-default-message-properties/59604/4 "2006-08-16T06:05:51Z")

</div>

Hey arp…

im also getting this error in our environment… but while using service orchestrator 3.1

can anyone else sched some light on this???

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 2:39pm UTC](https://techcommunity.softwareag.com/t/smh-error-modify-default-message-properties/59604/5 "2021-04-02T14:39:56Z")

</div>


