IISpeed 2.0.4 install issues- Win2012 x64

83 views
Skip to first unread message

Mark B

unread,
Jul 3, 2017, 8:12:41 PM7/3/17
to Support
Hello, I am troubleshooting IISpeed 2.0.4 install issues on a test Win2012 x64 server. I can't seem to render a website page with the footer information showing that the module has been installed correctly on this test site: http://agssandbox.com/ and I don't see anything populating to the cache folder. I've attached the config file I am using the. The only edit I have made is to the filecachepath.

I have followed the install instructions here: https://www.iiswebspeed.com/documentation/installation . I've created an iispeedcache directory D:\sem_sites\dev\iispeedcache and have given IIS_IUSR users full control of this directory. I've also given IIS_IUSR read and execute permissions to C:\Program Files\we-amp\iispeed\release and C:\Program Files (x86)\we-amp\iispeed\release

I've confirmed that the website has We-Amp IISpeed (C:\Program Files\we-amp\iispeed\release\iispeedmodule.dll) 64 bit module listed. The attached config file is in the root of  http://agssandbox.com/  and also C:\Program Files\we-amp\iispeed\release and C:\Program Files (x86)\we-amp\iispeed\release

I've checked event logs, tried turning on pagespeed diagnose and I'm not finding any information to pin point this issue. Is there something simple I am missing?

Any direction would be create- I am looking forward to getting this installed. Thanks- Mark


iispeed.config

Otto van der Schaaf

unread,
Jul 4, 2017, 3:39:55 AM7/4/17
to Mark B, Support
Are you testing from a local or public IP address?
When unregistered, the module only responds to requests private ip addresses
Maybe that's it?

Otto

Mark B

unread,
Jul 4, 2017, 10:57:33 AM7/4/17
to Support, bonne...@gmail.com
Hi Otto, thanks for the reply. I've copied the website files to the wwwroot default website dir on the server, and checked the site via http://localhost, restarted the server, confirmed the iispeed module is listed as a module on the website and the cache directory is still empty and the pages aren't rendering with the iispeed footer. I do have a license, but want to render the iispeed footer to verify the module is installed correctly. Is this a permissions issue, 32bit / 64bit issue or iispeed config file issue?

Also, I am seeing System-Error events in the event log with event id 7034 on the days I've been testing iispeed installs, etc. (this server is have not been used for anything else ever), I've attached an event log export. The system errors are mostly:

The IIS Admin Service service terminated unexpectedly.
The World Wide Web Publishing Service service terminated unexpectedly.

Could the iispeed module be part of the above errors?

Thanks- Mark
iispeed-system-errors2.evtx

Otto van der Schaaf

unread,
Jul 4, 2017, 11:32:09 AM7/4/17
to Mark B, Support
As of the latest release, the footer is no longer rendered.
But you could append ?PageSpeedFilters=+debug to the querystring to verify, as that appends a debug comment to the html?

As for the admin service terminating: I can't relate that, but the www could be possible (if the module is actually doing something).
There is a known issue in the pagespeed libararies with shutting down, which can cause a crasher when the app pool shuts down.
I wouldn't expect that to happen very frequently though..

Otto

Mark B

unread,
Jul 4, 2017, 1:04:54 PM7/4/17
to Support, bonne...@gmail.com
Thanks Otto, I decided to install on our production web server and I think it's working ok on this different server. I've also licensed it and see files populating to the cache directory + I see debug info in source.  On the test server, I could see the debug info in source, but no files were populating to the cache directory, so I'm not sure what is going on on the test server, but it seems to be working fine on production. Mark

Bruno Prebeg

unread,
Aug 10, 2017, 9:17:54 AM8/10/17
to Support, bonne...@gmail.com
Hello, 
I had the same problem as you had initially described and then I came across this thread.
I am using unregistered version for testing on the local machine. I was trying to get things going with the URL http://localhost/site, but this wouldn't work. 
Following previous comment from Otto I have changed it to http://127.0.0.1/site and now it is working as expected, maybe this is the issue on your test server if you are using unregistered version there?
Anyways, thanks Otto for your help:)!
Reply all
Reply to author
Forward
0 new messages