Many install issues and Test SMTP settings crashes W3WP.exe on Windows 2008 Server
So I installed gemini 3.1 after several hours of playing around and now I can not get it to send a test email, so I have no clue if the email settings are working. When I click on the "Test" button in Gemini, IIS crashes completely and all websites go down and this is what is logged in event viewer:
Faulting application w3wp.exe, version 7.0.6001.18000, time stamp 0x47919413, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a7a6, exception code 0xc0000374, fault offset 0x000b015d, process id 0x16f0, application start time 0x01c96544230f280d.
Any ideas on how to fix this? Having trouble evaluating this product for our organization when the email notifications won't even work and it crashes the server...
FYI, There were several issues with the install on Windows 2008.
Issues I encountered during the install:
1. It is not documented for Windows 2008 that it requires classic mode instead of integrated pipeline mode in IIS for the website to function.
2. There were local activation DTC issues on the IIS WAMREG admin service, so I had to enable that in component services. Not sure as to the cause of these issues, but SharePoint, and Reporting services are working fine on this box, so I am not sure what is so special about Gemini that requires these permissions.
3. The website would constantly fail to load during the initial setup with the following error:
Exception information: Exception type: HttpException Exception message: Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (C:\Program Files\CounterSoft\Gemini Project Issue Tracking\Gemini Web Application\web.config line 46)
I have .NET Framework 3.5 with SP1 installed at the time. So I downloaded the ASP .NET AJAX toolkit and the WSE 3.0 extensions (even though they are already integrated into .NET 3.5) and ran them on the box and that seemed to fix this error.
MattO
· 1 |
|
Tuesday, December 23, 2008, 9:47:40 PM |