The process that served the application pool** terminated unexpectedly. The process ID is **. The process exit code is 0x80

Event Type: Warning Event Source: W3SVC Event Category: None Event ID: 7034 Date: 2010-8-XX Event: XX:XX:XX User: XX Computer: XXXX Description: For application pool 'XXXXX' The process of providing the service terminated unexpectedly. The process ID is 'XXXX'. The process exit code is '0x80'. For more information, see the Help and Support Center at http://go.microsoft.com/fwlink/events.asp. CAUSE Together with each worker process that IIS creates under a separate identity, the system creates a new desktop object by allocating memory from the configured desktop heap. This issue occurs because, when the heap has been exhausted, IIS cannot create more worker processes Clients then receive the "service unavailable" error message in their Web browsers when they try to visit Web sites that those application pools host. The memory heap of the independent process is exhausted, and IIS cannot create more process workspaces to handle the resolution. Method: Warning: You need to modify the registry of the server. Please change the usage of the previous key. The registry key permits all worker processes to run in one shared desktop, regardless of their worker process Identities. To add the UseSharedWPDesktop registry key: 1. HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\W3SVC 2. Create a new DWORD entry under the Parameters key. :UseSharedWPDesktop value is 1 Restart IIS MS About this key value Description: UseSharedWPDesktop Registry path: HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\W3SVC\\Parameters Data Type: REG_DWORD Default Value: 0 Range: 0 - 1 If you are using a unique identity setting Application pool, then up to 60 application pool caps will be reached based on the application and memory resources on the server. Some system resources that are assigned a single new login session have certain restrictions. This means that there can be 60 processes running simultaneously on different accounts. IIS 6.0 supports running these processes on a single shared workstation and desktop at a cost that is a single package that shares a single user session between all parties. To scale to more than 60 application pools and share a single desktop, change UseSharedWPDesktop to a DWORD value of 1. After changing this registry key, you should be able to scale to hundreds of application pools and hundreds of concurrently running worker processes.

None of the above two methods have any effect... Think carefully for a long time. Think of yesterday's adjustment to the server's system32 directory... so add users to access (read, read and run, list folders and Directory). So.....the problem is solved... I have a go....windows permissions make me very painful