Internal Server error 5015

[Reinaldo Cardenas]

Gentleman

In the Project Server 2003 sometimes, when i intented logon with windows
authetication or local Project Server account, i do not logon and display
this message : An internal server error has occurred and Project cannot log
you on at this time. Please try again later. (5015), is necessary restart the
server and is possible do log on.

Any idea what resolve this issue, please ?

thanks and regards

 

[Amir]

how are you logging into project server? PDS method or PWA?

 

[Marc S.]

Reinaldo,

Usually when we get that error it means that the hard disk of the server
running SQL is full. This is probably caused by the log file that is created
with your Project Server database. It grows with every transaction in the
database and can easily reach a size of up to 30 - 50 GBs. To make sure this
is really the cause of the problem open Explorer in Windows and navigate to
the location of the log files. If you don't know where they're stored simply
search for *.ldf on your hard drives and you should find the files. Check the
size of the log files and let us know whether this could be the cause of the
problem.

Hope this helps...

Marc

 

[Marc S.]

Reinaldo,

Although you haven't provided us any update on whether the error is really
caused by the full hard drive of your server, here's the SQL script I usually
run to shrink the database log file.

backup log ProjectServer with truncate_only
dbcc shrinkfile(ProjectServer_Log, 1)
dbcc shrinkdatabase(ProjectServer, 0, TRUNCATEONLY)

Please note that 'ProjectServer' stands for the name of the database,
'ProjectServer_Log' is the name of the respective log file.

I would not consider myself a SQL expert so this script may not be perfect -
maybe Gary Chefetz or somebody else with SQL knowledge can post a brief
feedback on it? However, it always gets the job done for me.

Hope this helps...

Marc

 

[Reinaldo Cardenas]

the login is PWA

how are you logging into project server? PDS method or PWA?

 

[Reinaldo Cardenas]

Hello Marc,
excellent, the error was caused by the full logs SQL file.

Thank you very much

 

[Reinaldo Cardenas]

Hello Marcs,

Yes, this is the cause of the problem.
because, suddenly ? :-(

Thanks for help me

 

[Marc S.]

You're welcome!

I would recommend you to create a scheduled job in SQL Enterprise Manager
that runs the script I've posted every week. This will make sure the same
problem won't happen again without you having to check the size of the log
file manually every day...

Regards,

Marc