W
wwalkerbout
Greetings,
I am looking at setting up a process to help Network Operations
Support personnel proactively support a Project Server 2003
implementation. In order to do this, I would like to trap error
messages written to the IIS and SQL Server log files that specifically
relate to Project Server.
For trapping those error messages, I know there are a number of
options. However, does anyone know of how to obtain a list of the
Project Server 2003 specific error messages, or alternatively how one
might identify them so that they can be trapped?
Additionally, aside from the IIS and SQL server log files, are there
any other options for tracking error conditions for a Project Server
2003 implementation? The environment would initially consist of a two
server configuration (PS2003 and SQL Server), but is expected to
rapidly evolve after the initial Proof of Concept phase.
Any and all suggestions most appreciated.
Cheers,
Wayne
I am looking at setting up a process to help Network Operations
Support personnel proactively support a Project Server 2003
implementation. In order to do this, I would like to trap error
messages written to the IIS and SQL Server log files that specifically
relate to Project Server.
For trapping those error messages, I know there are a number of
options. However, does anyone know of how to obtain a list of the
Project Server 2003 specific error messages, or alternatively how one
might identify them so that they can be trapped?
Additionally, aside from the IIS and SQL server log files, are there
any other options for tracking error conditions for a Project Server
2003 implementation? The environment would initially consist of a two
server configuration (PS2003 and SQL Server), but is expected to
rapidly evolve after the initial Proof of Concept phase.
Any and all suggestions most appreciated.
Cheers,
Wayne