Follow up on previous post about msmq problems.
After a bit of investigating I found that my profile was damaged in some way so that the net.pipe, net.tcp and net.msmq bindings shoved up as being asociated to (unknown). After deleting local profile and logging in again everything was peachy!
Monday, 13 May 2013
Friday, 3 May 2013
Windows Server 2012 and uninstalling .net v4.5
Yes, sometimes we do those little things that's really really not a good idea.
We had a bit of trouble with a MSMQ-queue in a project and since I am in no means a server person i thought it odd that HTTP Activation was not installed for .Net Framework 3.0 when it was so for 4.5, so I installed that feature. Big mistake it turns out. After this the net.msmq, net.pipe and net.tcp bindings stopped working. Ok, I think we might have fixed this if we had just re-installed the 4.5 version of the http-handler but instead I accidently uninstalled .net Framework 4.5. This is a big no-no on a Windows Server 2012 apparently so when server had restarted we were in core mode (no gui) without powershell! I should point out that of course this was no production server, I have enough self preservation to not go near those ;)
Internet to the rescue!
This technet forum-post and this blog-entry really helped out.
Basically they offer help to first activate to Powershell feature and then how to install two features from installation media. Back to square one!
We had a bit of trouble with a MSMQ-queue in a project and since I am in no means a server person i thought it odd that HTTP Activation was not installed for .Net Framework 3.0 when it was so for 4.5, so I installed that feature. Big mistake it turns out. After this the net.msmq, net.pipe and net.tcp bindings stopped working. Ok, I think we might have fixed this if we had just re-installed the 4.5 version of the http-handler but instead I accidently uninstalled .net Framework 4.5. This is a big no-no on a Windows Server 2012 apparently so when server had restarted we were in core mode (no gui) without powershell! I should point out that of course this was no production server, I have enough self preservation to not go near those ;)
Internet to the rescue!
This technet forum-post and this blog-entry really helped out.
Basically they offer help to first activate to Powershell feature and then how to install two features from installation media. Back to square one!
Subscribe to:
Posts (Atom)