Two log windows for one job

Hi there,

I have just installed BODI 11.5.1.5 on a new server (part of a migration effort) but now when I start a job from the client it gives me two log windows! They both keep in sync, displaying exactly the same information. And when I look in the management console there is only one entry. The jobs seem to be running just fine, it’s just strange that I have these two windows.

Anyone have any idea why this happens, and what I might try to get rid of the second window?

Thanks,

Tako


BertB (BOB member since 2008-11-05)

some additional information I just noticed:

When I start a job from the designer, the job server drop down in the execution properties window holds the same job server twice (along with the old job server by the way, how can I remove that one?)

Going to the Server Manager, I don’t see anything out of the ordinary: just the one job server.

Any help would be appreciated.


BertB (BOB member since 2008-11-05)

Please edit the AL_MACHINE_INFO repository table, you seem to have two entries for one jobserver as it looks. Did I get your point correctly?


Werner Daehn :de: (BOB member since 2004-12-17)

Hi Werner,

Yes, you were totally right. Thanks!

I suppose it is not standard procedure to start deleting stuff from repository tables, so now I am wondering where this came from.

The double entry for the new machine might have come from me using the wrong login details first, then invalidating that user in the database, after which removing the entry from the server manager gave some unexpected messages, even though the result was that the repository was no longer attached to that job server, and I could add one with the correct login details. Maybe that caused the entry to remain in the table.

And the other entry: is that due to the fact that I migrated by copying a backup of the original server over to the new server?
And can I conclude then that that is not the recommended way to do this?
An alternative I could think of (using ATL) would work as well, but I would loase my history, right?

Tako


BertB (BOB member since 2008-11-05)

All correct.
Normally you would run server manager and remove the repo associations for a given jobserver. But if that jobserver does not exist anymore…we have to hack it.


Werner Daehn :de: (BOB member since 2004-12-17)