Background information: We have an e-learning portal with hundreds of
courses and thousands of users which tracks user activities and course
scores, the user logs into the website, enters lms application and
launches a course. The course launch URL takes him to the content
providers website and also requests some AICC parameters from our LMS
Server.


Occurence: The courses were not launching since yesterday morning and
we noticed in the evening that the tranaction log was growing to
significant size and we executed the " dump tran databasename with
no_log " to dump the transaction log and hence the huge log file was
dumped and now the Tranaction log is <3GB size. And we were able to
launch the courses last night.


Environment: Win 2000 Server, SQL Server 2000, VC++

Errors: captured in Event Log as error messages, DebugViewer is used
to check code execution path and code related errors and trace any
known errors.

Issue: The course is launched from content providers website and the
LMS server on our end sends AICC parameters before launching the
course on the content providers website.

Now, the LMS server is not responding consistently when the complete
URL(which connects to both the content providers website and our LMS
Server) is launched..Though the error says Status 500: An error
occured in the content providers launch program, we used the
DebugViewer to note that it is the LMS that is not responding
consistently. (Even though the error makes us believe that the problem
is with the content providers program, the Technical support at the
content provider has certified that the problem is not with their
launch program, but with the LMS response)

Since morning, when we try to launch a course, we get an error message
as above however, if we refresh the screen 1 or 2 times then the
course gets launched, i.e, the launch is successful on multiple tries.

BackGround of the error: Months ago the courses and the call to AICC
parameters from the LMS used to be called from our LMS server and even
the course content was launched from our webservers, and at that time
the error was much more frequent.

Important piece of information:
SQL Server 2000: The transaction log size grew to significant size, so
we had to dump the transaction log(see on top), which was of 40GB
size, after dumping the log and backing up the database, the server
transaction log size is now much smaller (<3GB).

Thanks much

pankaj (AT) pankajrai (DOT) com (PR) wrote in message news:<5a4c014d.0407081127.76b1d6df (AT) posting (DOT) google.com>...
lots of details deleted]
Was there a question somewhere in all of that? Or were you just
warning us about what can happen when using Microsoft products?

Sitting here puzzled,
Ed Prochak