Unable to open this batch...

Options
Has anyone ever gotten this error "Unable to open this batch. This batch is exclusively opened by another user." when they know the batch is not open anywhere?  I have three users that are getting that message when they try to open or create a new batch.  They were all working fine up until yesterday afternoon and I cannot figure out where to look.  It seems like it's an issue with their workstations because when they log on to RE on another computer, it works fine, and when other users log on to theirs, they have the same issue.


BB recommends an uninstall/reinstall, which I'll try, just wondering if anyone has any other ideas or experience with this same issue that might be helpful.


Thanks,

Evan
Tagged:

Comments

  • First, just get everyone to log out so that zero users are logged in. I have often gotten errors indicating that some user (or an unknown user) has some record open (sometimes a gift, sometimes a query, some times a constituent . . . never a batch, but why not?) when clearly nobody has it open. The only solution is to clear everyone out and then log someone back in and test to see if it's accessible. 
  • Ryan Hyde:

    First, just get everyone to log out so that zero users are logged in. I have often gotten errors indicating that some user (or an unknown user) has some record open (sometimes a gift, sometimes a query, some times a constituent . . . never a batch, but why not?) when clearly nobody has it open. The only solution is to clear everyone out and then log someone back in and test to see if it's accessible. 

    Thanks Ryan.  Yeah, I've had the same thing happen with queries and constituents, but this is definitely a first for batches.  I'll wait until everyone clears out for the evening and see what I can come up with then.

  • Hi - I no longer work with RE on a daily basis, so I just looked it up in the documentation - there's a check box on the setup screen for batches that says "Other users may access this batch". If the batch was created by someone else, have them open it and see if that box is checked. I ran into this problem over and over with queries and reports and mail - I'd left the "others may make changes" (something like that) unchecked and so people couldn't save their changes before running and if they went back, they had to start over with dates or queries to include, etc. I tried to fix as many as possible before I left! The constituents you can't change - we spent a lot of time shouting, "could you close Smith, please?" across the office.


    Gracie Schild

    Bluebird Business Services

    Santa Fe NM
  • Ryan Hyde:

    First, just get everyone to log out so that zero users are logged in. I have often gotten errors indicating that some user (or an unknown user) has some record open (sometimes a gift, sometimes a query, some times a constituent . . . never a batch, but why not?) when clearly nobody has it open. The only solution is to clear everyone out and then log someone back in and test to see if it's accessible. 

    Similar experience here - neither I nor the data-entry clerk could get into the batch. So we went off and did something else, then tried again the next day and it opened OK. There were no check-box anomalies, as suggested by subsequent post. So if we have a reccurrence then we'll try the all-log-out method the same day. We're hosted.

  • Evan Post:

    Has anyone ever gotten this error "Unable to open this batch. This batch is exclusively opened by another user." when they know the batch is not open anywhere?  I have three users that are getting that message when they try to open or create a new batch.  They were all working fine up until yesterday afternoon and I cannot figure out where to look.  It seems like it's an issue with their workstations because when they log on to RE on another computer, it works fine, and when other users log on to theirs, they have the same issue.


    BB recommends an uninstall/reinstall, which I'll try, just wondering if anyone has any other ideas or experience with this same issue that might be helpful.


    Thanks,

    Evan

    Especially if you are self-hosted, also verify that your users are truly logging out of RE by using the Exit and Sign out menu option.  Any other method of closing down RE can leave the users potentially still logged in and help create these kinds of struggles.

Categories