For a few days ago, the company changed the new server, used the Win2003Server system, just felt good after installed. The server is placed in the Telecommunications Bureau and the speed is also very fast. It was running normally two days ago. On the third day, I suddenly couldn't access the server. At that time, I didn't care. After restarting the server, I run normal. I thought that things have been resolved, because it is weekend, I didn't care. When I arrived in the company, I killed twice during the day. Look at memory, normal, consume 20%, CPU is only 2%. Check the event log, the application log, there is no unusual place. This is a bad time, and I will not stop online. A friend who started 9CBS recommended me that it might be the problem of the application pool. However, no matter the application pool separately, or cancel the recycling process operation, IIS death is issued. Finally, someone said that Access is running in 2003. Think carefully, it is indeed, the server has a statistical analysis system on the server, which is an Access database that cannot be accessed normally, while another site without a statistics can be accessed. Then I immediately change the Access database to the SQL Server database. I have no problems now. Now think about it, it should be an Access database problem. It seems that this problem is a bug of Win2003. The patch is yes, but it requires the ID of the genuine system when it comes to request. Online also said that the next SP of Win2003 may contain this patch. I hope this article will help friends with the same problem. With such a problem, I suggest that the database is replaced into SQL Server.
