What am I missing here… I had this setup before and now I can’t seem to get it to deploy again.
I’ll start with this is a Server 2008 R2 setup (yes I know old IIS) but I was able to get 10.2.700.12 to work after installing IIS 8.0 Express. I removed everything from the server and restarted back at 10.2.400 to see if I could get a side by side install going and replicate what I would like to do on my live server. I need an environment available to train users on the changes and have it be comprable performance to what they will see and I have no other servers available so side by side is the only option. Everything for 10.2.400 went back and was running fine with my live database, so I went to install 10.2.700 and I’m getting as far as the deploying of the appserver and it will crash saying it could not install WebSockets I need to enable that feature to work. I’ve tried removing IIS 8.0 express and re-installing it and still the appserver won’t deploy.
Josecgomez, if that was an option I wouldn’t be bothering to fight with this. I have no budget to upgrade anything, stuff has to die before they replace it.
Chaddb, I do not see that option anywhere in features, as well as I had this working last week… I only uninstalled it all to get 10.2.400 up and running and do a side by side upgrade. The server base config didn’t change from last week to this week which is why I’m so confused on how I was able to use it then but I can’t now.
I think the Web Socket feature was actually introduced in Server 2012. I take back enabling that feature. It may be supported in IIS 8.0 but I’m not sure how you enable it. Unless it’s enabled by default. But I would agree with @josecgomez that there is probably a dependency or something you’re missing. I’m guessing 10.2.700 requires something 10.2.400 doesn’t. Not sure why it worked and now doesn’t.
That only works for IIS 8, not the express version… I guess the best thing I can do is a full system restore on this box from last weeks backup. That’s the only way I’ll get that working environment back.
I wish it were that easy to convince… but the issue here is, that’s not the live environment. Technically I should be able to install this without a problem on my live server since that’s 2016.
What I was hoping to do this year was replace my two 2012 servers with new ones and then this wouldn’t even be a problem because I’d have those retired ones as test environments, but I was denied that.
Pay for a subscription service? Ha! I’m lucky I got them to move to Office 365. Hell they tried to axe that 2yrs ago after we did one year of it. Thankfully the entire office staff was on my side to keep it. We’d be back on office 2010 if it wasn’t for them speaking up.
I also only have 400/40 cable internet service… The last thing we’ll be doing is moving services to the cloud, I can barely support the one remote site and 2 remote users we have with that internet service.
**wow that added a bunch of junk when you reply via email…
I appreciate all of the other suggestions but unfortunately all of them are out of reach for me. I need to work with this server, or move on and try this on a different resource we already have. The latter is not desired because our other resources are already being used for other purposes.
Why not just setup dev app servers on your production server. We disable all MRP type processes in development and run all 4 of our appservers side by side without issue.
Jonathan - I think your a talented individual who is eager to learn based on your past posts… Would you say that your current employer stifles your capabilities? With their budget constraints, you will become the guy who lists Windows 2008 on his Resume 10yrs from now.
