Failed Windows 3.4.3.0 upgrade

[Rod Widdowson]

> You have 3.4.1 stuck in the container and that's what it's running. The configuration is not part of the warfile so you have a
3.4.3
> system config running against a 3.4.1 IdP warfile and jars. You're comparing apples and apples but running an orange.

None of which usually happen but other applications can easily disturb the force

What you might want to do is stop the service, delete the temp files, redeploy the war and restart the service.

	sc stop shibd_idp
	rd /s/q "c:\Program Files (x86)\Shibboleth\IdP\jetty-base\tmp"
	cd "C:\Program Files (x86)\Shibboleth\IdP\bin"
	build
	sc start shibd_idp

A failure at any of these stages need investigated.