Repository Migration and ZABO

system · June 2, 2003, 6:48pm

We’ve just created a new repository (our old one got corrupted). It’s an instance on the same server as the old one. I’ve exported/imported users, imported/exported Universes and uploaded documents. We are just changing the name from BO to BOREPO. Connection strings are also the same, but, obviously there is a new BOMain.key file.

This will be transparent to Webi users but how is this going to affect the ZABO users? Will they have to download ZABO again to get the new BOMain.Key?

I did a search and someone did ask the same question here but the thread talks about everyting to be considered but ZABO.

BO_User (BOB member since 2002-10-02)

system · June 2, 2003, 6:58pm

ZABO users don’t download the BOMain.key. They use the one on the Webi server. So as long as that one is up to date, you should be fine.

MichaelWelter (BOB member since 2002-08-08)

system · June 2, 2003, 7:55pm

Doesn’t the LocData contain servername.key? So I am guessing that gets updated everytime a ZABO users logs in?

BO_User (BOB member since 2002-10-02)

system · June 2, 2003, 7:59pm

Yes, it does, but in this case, the server isn’t being changed, so there shouldn’t be anything to do at the desktop level.

MichaelWelter (BOB member since 2002-08-08)

system · June 3, 2003, 6:20pm

I get it now. Thanks

BO_User (BOB member since 2002-10-02)

system · June 4, 2003, 1:56pm

Any ideas on how does this affect Stored Procedures Reports? Some of my reports are using SPs. ther refresh fails saying that “A connection required to refresh this document is unavaliable”. When I try to edit the data provider, it tells me that “You are not authourized to use this stored Procedure”. I checked in the DB and the Userid has execute permissions on the SPs.

Anyone know why this is happening?

BO_User (BOB member since 2002-10-02)