E
Engelbert
When installing SPS 2003 to use the same SQL Server 2K server that was
already in use by (a newly installed) Project Server 2003 and its WSS, I
discovered that the account that had been specified for Logon for both SQL
Server and for SQL Server agent was a domain account that had a
non-permanent password.
Not a good idea in the long run, so I changed it in both cases to Local
System account and ran IISRESET
I also had discovered that both .NET Framework 2.0 and ASP.NET 2.0 had been
installed on that SQL Server 2K. Nobody responsible for this server knew why
so I removed those too (as SPS 2003 doesn't like ASP.NET 2.0 - typically on
its own server).
(I was having problems with the SPS 2003 installation and trying to remove
any contributing factors on the SQL Server machine where the problems lay.)
However now the customer can't login to PWA and hasn't be able to since mid
afternoon yesterday. (Thus knocking out the re-boot of the SQL Server server
a couple of hours *later* as a reason.)
(and the time this problem started is such that it's most likely to be the
time the Local System Account was specified but also might be when ASP.NET
2.0 and .NET Framework 2.0 were removed. I wasn't told of the problem at the
time - only this morning - so I can't allocate it to one of those two things
for sure.)
Does anyone have any idea from the above what the problem might be and how
to fix it ?
Engelbert
already in use by (a newly installed) Project Server 2003 and its WSS, I
discovered that the account that had been specified for Logon for both SQL
Server and for SQL Server agent was a domain account that had a
non-permanent password.
Not a good idea in the long run, so I changed it in both cases to Local
System account and ran IISRESET
I also had discovered that both .NET Framework 2.0 and ASP.NET 2.0 had been
installed on that SQL Server 2K. Nobody responsible for this server knew why
so I removed those too (as SPS 2003 doesn't like ASP.NET 2.0 - typically on
its own server).
(I was having problems with the SPS 2003 installation and trying to remove
any contributing factors on the SQL Server machine where the problems lay.)
However now the customer can't login to PWA and hasn't be able to since mid
afternoon yesterday. (Thus knocking out the re-boot of the SQL Server server
a couple of hours *later* as a reason.)
(and the time this problem started is such that it's most likely to be the
time the Local System Account was specified but also might be when ASP.NET
2.0 and .NET Framework 2.0 were removed. I wasn't told of the problem at the
time - only this morning - so I can't allocate it to one of those two things
for sure.)
Does anyone have any idea from the above what the problem might be and how
to fix it ?
Engelbert