Page 1 of 1
Unable to load RID -
Posted: Mon Feb 09, 2009 3:33 am
by wjfitzgerald
Good Morning,
When i try and open any of my jobs this mornign, i am getting the following message:
"Unable to load RID - c2e76d84.43058877.6cf8a39.119137fb7f0.65d5ca16.3e3b4"
I have never seen this before and have no idea how to resolve it.
I have done a search on the site but have found no results.
If you have any suggestions i would be delighted to hear them, please?
Regards,
John Fitz
Posted: Mon Feb 09, 2009 5:02 am
by varaprasad
For me, it seems more like a repository related issue.
Please check your DB2 and see if there is any issue with the database.
Posted: Mon Feb 09, 2009 5:33 am
by wjfitzgerald
Thanks, will do.
The message just isn't the most informative, and i had no idea where to start.
Posted: Mon Feb 09, 2009 5:36 am
by wjfitzgerald
Thanks, will do.
The message just isn't the most informative, and i had no idea where to start.
Posted: Tue Aug 11, 2009 1:21 am
by telenet_bi
did you have any luck on finding this?
We just installed fixpack2 (on 8.0.1) and now have the same error. We are using Oracle as repository, so it won't be DB2 specific then.
Posted: Tue Aug 11, 2009 1:24 am
by ray.wurlod
RID = Repository ID
The other is a unique identifier of some record somewhere in the Repository database. I have no idea where.
It may be that your credentials to use the suite (and therefore its associated services) are lacking.
Posted: Tue Aug 11, 2009 2:25 am
by wjfitzgerald
Hi,
I am sorry to say that i found nothing definitive so i just went back through DB connections passwords, server connections and passwords etc.
Somewhere in there something must have been amiss, after a bit of pulling and dragging the jobs sorted themselves and have been running fine since.
I am sorry i have nothing more specific for you.
Regards
John FItz
Posted: Thu Aug 13, 2009 5:38 am
by telenet_bi
we've found our issue also. fixpack2 wasn't installed correctly on the client. It seems a client on 8.0.1fixpack1a cannot save jobs on a server which is 8.0.1fixpack2. (the other way around is also not possible)
This makes it rather difficult for us, since a dual install between these versions is also not possible. so we'll need a lot of extra PC's in the period between the first upgraded server and the last one.