Were you able to login to your Business Space console to view dashboards that were created on Business Monitor, and now you get a Page Cannot Be Displayed and in your url bar it direct you to a security check (see image below), even though you did not make any changes? If so, read on.
Apparently there is a bug that allows duplicate entries to be created in a table in Business Monitor that stores your account information. If this is happening, you will see the following error in your SystemOut.log for your Business Space server:
12/13/12 10:51:23:182 EST] 00000038 E com.ibm.mm.server. persistence.rdbms.dao.ibatis.BaseDao getAccountByExternalId [12/13/12 10:51:23:323 EST] 00000038 W com.ibm.mm.server.model. persist.NLFModelPersistenceHandlerImpl loadSharedRoot IGNORING EXCEPTION (error reading account with external id 05ebab275936e94ca69d576c67bc8f8d), RETURNING NULL com.ibm.mm.framework.persistence. exceptions.DataBackendException: error reading account with external id 05ebab275936e94ca69d576c67bc8f8d at com.ibm.mm.server.persistence.rdbms.dao.ibatis.AccountDaoSqlMap. getAccountByExternalId(AccountDaoSqlMap.java:55) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
You should open a PMR with IBM so that they can provide you with the fix that will prevent duplicate entries from being created in this table, and thus, preventing some users from logging in. Only users that have a duplicate row in the table will not be able to login. So, some users may still be able to login to Business Space.
There is a table called ACCOUNT, most likely in your Monitor database, unless you created a separate database for your Business Space. Retrieve all the rows in this table and sort by EXTERNAL_ID ascending order.
Simply look for the ID that is mentioned in the error in you SystemOut.log for Business Space (as seen in red above). You will see two rows there in your table. Delete one of the rows and Commit your changes.
After you restart your Business Space server, you will be able to log in to Business Space again.