Web & E-Learning Services

Known Blackboard Issues:

Description of Problem Reported
Status
Workaround
Error on login:
" No authentication credentials were provided with the request" ?
Most reports have been cleared up by enabling active scripting in Internet Explorer. I'd suggest just adding it to your list of trusted sites, which would allow active scripting for BB, but not leave you open to the world.
 
Testing Locking up Reported to Blackboard Only appears to happen when test is set at view one question at a time with no backtracking.

A user has to log in twice if they access the login page directly, without going through the gateway page. User receives the message: "Challenge Token null".

When a user bypasses the Gateway page, a session is not created to the database and it results in the issue that users are seeing where they have to login twice. To keep from having to click login twice always access Blackboard from http://blackboard.odessa.edu/
Course Copy does not work properly with courses with a course cartridge Reported to Blackboard Use Export Course and then import with Import Package, only works if cartridge is not copyright protected. Recommend getting another cartridge, rather than exporting.
E-mail only works if all addresses are correct Reported to Blackboard  Make sure all addresses are correct
Instructor is not sent e-mail when coping course Fixed  
Assignment or Quiz modification automatically checks "display from" Blackboard is aware of problem and it should be fixed with Application Pack 2 in late August or September. If you change the “until date”, this problem does not occur.
Database Error encountered when pasting HTML saved from Word into Item text box. This is caused by a 32,000 character limit for that particular text field. Saving Word as HTML creates bloated HTML which fills this limit quickly. Save the HTML as a separate file, attach to Item instead of pasting into text box.
User logged out for no apparent reason. A user that logs in and uses Blackboard extensively in one sitting may reach a point where he or she is logged out for no apparent reason. This issue is cause by a limitation in browsers on the number of cookies associated with a single server. When the user logs in, a session cookie is created. Several other areas, such as Assessments, individual portal modules, and building blocks will also create session cookies. When the number of cookies associated with a server reaches 20, browsers will often begin dropping some of the older cookies. In this case, the oldest cookie is the login cookie.