roman(at)romanportal(dot)com>
Wed Jan 09 06:59:01 CST 2008
Hi Jordi,
Thank you for replying. I did install WSS3 x64 and also ASP.NET x64 yet the
problems persisted. I reinstalled ASP.NET 32bit to try and resolve the
problem. I could not resolve the issues I was having and there is little
information I could find to explain the x64 symptoms I was getting.
After several days of working on this problem, together with other unrelated
issues I've had with 64 bit applications, I am currently rebuilding the
server using 32 bit.
The network is small, 5 users, and I'm about quarter way through. I hope to
be up and running with WSS tomorrow but it will be a late night, again :)
Regards,
Roman
"Jordi Valldaura Riqué" wrote:
> Why dont you install 64 bit versions of WSS and .net framework? You are
> forcing your IIS to work oin 32 bits mode.
> "Roman" wrote:
>
> > Hi Mike,
> >
> > It seems 2K3 R2 x64 is feature rich.
> >
> > The Windows firewall is Off. I scrolled through the Services MSC and stopped
> > the Windows Firewall / ICS Service which was Started - no apparent system
> > change was noted. I don't believe I require ICS for normal client / server
> > operation?
> >
> > Now, several snippets from the Event Logs after the server reboot earlier
> > this morning. A string of these two events are in the log. I consequently ran
> > the ASP.NET 32 bit install (cscript
> > %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET
> > W3SVC/AppPools/Enable32bitAppOnWin64 1 and
> > %SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i) and
> > they stopped. I consequently now have ASP.NET v2.0.50727 (32 bit) Allowed in
> > the IIS Web Service Extensions.
> >
> > Event Type: Error
> > Event Source: W3SVC-WP
> > Event Category: None
> > Event ID: 2274
> > Date: 9/01/2008
> > Time: 1:24:20 AM
> > User: N/A
> > Computer: HOMENETSVR
> > Description:
> > ISAPI Filter
> > 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_filter.dll' could not
> > be loaded due to a configuration problem. The current configuration only
> > supports loading images built for a AMD64 processor architecture. The data
> > field contains the error number. To learn more about this issue, including
> > how to troubleshooting this kind of processor architecture mismatch error,
> > see
http://go.microsoft.com/fwlink/?LinkId=29349.
> >
> > For more information, see Help and Support Center at
> >
http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: c1 00 00 00 Ã?...
> >
> > Event Type: Error
> > Event Source: W3SVC-WP
> > Event Category: None
> > Event ID: 2268
> > Date: 9/01/2008
> > Time: 1:24:20 AM
> > User: N/A
> > Computer: HOMENETSVR
> > Description:
> > Could not load all ISAPI filters for site/service. Therefore startup aborted.
> >
> > For more information, see Help and Support Center at
> >
http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: c1 00 00 00 Ã?...
> >
> >
> > Event Type: Warning
> > Event Source: WinMgmt
> > Event Category: None
> > Event ID: 37
> > Date: 9/01/2008
> > Time: 2:13:12 AM
> > User: N/A
> > Computer: HOMENETSVR
> > Description:
> > WMI ADAP was unable to load the
> > c:\windows\Microsoft.NET\Framework\v2.0.50727\aspnet_perf.dll performance
> > library due to an unknown problem within the library: 0x0
> >
> > For more information, see Help and Support Center at
> >
http://go.microsoft.com/fwlink/events.asp.
> >
> >
> > I've issued several iisresets. Any suggestions warmly appreciated :)
> >
> > Roman
> >
> >
> > "Mike Walsh" wrote:
> >
> > > Check that the Windows Firewall Service is stopped and set to disable.
> > >
> > > This is something that I saw first with R2 and 2003 with SP2 until then
> > > this "feature" wasn't included.
> > >
> > > It continues to catch me out almost every time I install WSS 3.0 or MOSS
> > > 2007 on a VM.
> > >
> > > Mike Walsh
> > > WSS FAQ
http://www.wssfaq.com
> > > no private e-mail questions please
> > >
> >