Today the blog turns 5 years old.
Happy birthday old chap, good sport.
Today the blog turns 5 years old.
Happy birthday old chap, good sport.
Release 3 of the Create Time Dimension App is now live. This version brings Czech language support and ISO-8601 week numbers.
The update is made on the server so it is available for everyone right away, no update needed on the Excel/Client side.
Big thanks to Petr Havlik (Twitter: https://twitter.com/petrhavlik) for helping with the Czech translation.
Please note that the ISO-8601 week numbers are just one way of expressing week numbers and might not be what you want. The week numbers start on Mondays per definition and does not change when changing the week start day. If you would like to use another week numbering format you can still add a column using the =WEEKNUM(date, week number system) formula in Excel.
When installing a separate 32 bit web application in a SharePoint 2013 Farm the new application might fail to load and give a general 503 Service Unavailable error message. When looking in IIS manager, the Application Pool for the new app would be in the stopped state.
The following error messages might be visible in the Event log…
Event ID 5002 – Error <date and time> WAS 5002 None
Application pool ‘<App Pool Name>’ is being automatically disabled due to a series of failures in the process(es) serving that application pool.
And
Event ID 5139 – Warning <date and time> WAS 5139 None
A listener channel for protocol ‘http’ in worker process ‘<process number>’ serving application pool ‘<App Pool Name>’ reported a listener channel failure. The data field contains the error number.
Event ID 2282 – Error <date and time> IIS-W3SVC-WP 2282 None
The Module DLL ‘C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\isapi\spnativerequestmodule.dll’ could not be loaded due to a configuration problem. The current configuration only supports loading images built for a x86 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.
The Microsoft link for the issue will only redirect you to the www.iis.net web site.
The solution to this issue is to enable 32 bit applications to be loaded together with SharePoint and ask the SharePoint Module to only load in 64 bit mode. This can be done by running the following command, located in the %WINDIR%\System32\inetsrv\ folder:
appcmd.exe set config -section:system.webServer/globalModules /[name=’SPNativeRequestModule’].preCondition:integratedMode,bitness64
More information on configuring IIS can be found here: http://technet.microsoft.com/en-us/library/cc627313.aspx
Hat Tip to my colleague Markus Lind for pointing this out.
This is a follow up post on: Moving the blog to azure web sites: http://www.stefanjohansson.org/2013/05/moving-the-blog-to-azure-websites/
2013-07-09: Update 2 – As of Version 2.3.1 the Jetpack plugin and the WordPress cloud have been updated to support more SSL scenarios. Jetpack should now work without issues and configuration changes. The post below is still valid for other connected systems that doesn’t like mismatched SSL certificates.
One key feature missing from Azure Web Sites is the possibility to run your own SSL certificate for encrypted https traffic.
2013-06-03: Update 1 – https, SSL and certificates for custom domain names are now launched and available (for sites running in “reserved mode”) – read more here: http://www.windowsazure.com/en-us/develop/net/common-tasks/enable-ssl-web-site/ The information below still applies in case you don’t want to use a reserved mode site.
This pretty much disables it for any real business use whatsoever.
Every single professional I have spoken with regarding this have chosen alternate solutions for their projects and tests. As usual a key problem here is no official words on availability and firm delivery dates to relate to. Finding a blog post or discussion thread where someone says it might be available as a feature in the future just doesn’t enable project budgets to be spent on Azure Web Sites even for tests and explorations.
This weekend an issue with another website running in the same tenant as this blog made the whole system go down. This episode made me finally spend some time moving the blog to Azure Websites. It should be running fine and exactly as before, but if you find anything out of the ordinary or not working, please let me know.
The earlier host was LAMP-based so I had to do some changes to get everything working as before:
1, I had to upload a web.config file to support pretty links and remove the need for index.php in the url. More information here: http://stackoverflow.com/questions/9965124/how-to-rewrite-the-index-php-of-codeigniter-on-windows-azure
and here: http://codex.wordpress.org/Using_Permalinks#Permalinks_without_mod_rewrite
2, I had to trick Jetpack into working properly since there was an error message about a self signed certificate that made the whole thing go overboard: http://www.tpateman.co.uk/reboot/error-activating-jetpack-plugin/
Apart from that there was just the usual parts, update the dns configuration to support the new dns name in Azure (http://www.stefanjohansson.org/2012/12/how-to-configure-custom-dns-names-for-multiple-subdomain-based-azure-web-sites/), update the dns to point to the new host, migrate the content from the old host to the new and make sure everything was still configured as before.
While doing all of that I also managed to learn about the Core Control plugin (http://wordpress.org/extend/plugins/core-control/),
I also updated a few posts with manual Excerpts so that the posts displayed on the front page are truncated and a sticky post about migrating to Australia…
Update 2013-05-20: I have explored the JetPack issues some more and describe it here: http://www.stefanjohansson.org/2013/05/workarounds-for-problems-using-jetpack-and-https-on-azure-websites/