It has been while since I posted anything. Mainly not because I was not learning anything new, but it is because I am not getting enough time nowadays (or in other words, I just got a life now ). But then I realized that time and time, I like to read my old post to fix some really odd issue and if I don’t keep record of troubles I had in past, I might forget them again. So I decided to find time to write often… it’s my new mid year resolution … lets see if I stick to this or not.
Recently I was playing with Windows 2016 Server in our test environment as part of testing it’s viability for our application suite. And so if you have ever worked with .NET Framework project you know that sometimes it can be royal pain to work if there is a version difference between Framework you have installed and Framework project is expecting.
Something like that happened with me in this case too. I need to have Framework 4.0 and Win 2016 has 4.6 installed by default. So against my better judgment, I decided to uninstalled .Net Framework 4.6 from system. It did let me uninstall it just fine but when I rebooted system, it failed to start Server Manager because guess what !! It was depending on .NET Framework 4. So I thought OK, I can download installed from Web and install it using that. But nooooo, since it’s part of OS now you can’t run installer and install framework from there. So I had catch 22 case. I can’t install .NET Framework from installer because it’s part of OS (and you have to use server manager) And you can’t start server manager for installation because you need .NET Framework 4 !!
So… after trying Windows 10, I ran into first annoying issue which seem to have no solution at this point.
Main reason I wanted to upgrade to Win 10 (not sure if I had choice since MSFT is literally forcing everyone to upgrade to Win 10) was to try Hyper-V. I am running at any given time @ 3 VMs together and my laptop has 8GB of ram so it has no issue running all of them together.
But today I was getting odd error when I tried to start VMs for something. Exact error was like below,
Finally I gave up and upgraded my Windows 7 Pro to Windows 10 Pro. I resisted upgrade to 8 and 8.1 mostly because when I tried them in my new laptop I was not impressed at all. Worse, I lost my faith in MSFT. It was mostly because user experience for me was just terrible. I am more in favor of OS with less clutter and less GUI heavy… and Windows 8 was opposite of it.
What I like: After playing with Windows 10 preview, I was genuinely impressed. I liked that MSFT has replaced metro desktop with good ol’ start menu, even if it is not same as old one but to me it is still more functionally useful than metro. More control over update and more option for privacy settings. Most good feature for me was inclusion of Hyper-V server in Professional edition. This relives me from using 3rd part hypervisors (read Virtual Box Smile). And another useful feature for me was PS 5 with WMF 5.
So it has been ages since MSFT has ceased support for once great operating system Windows XP. But some lucky few still have no choice to use it because of some legacy app they just can’t get rid of Or people like me who are still using Windows 7 and use XP in …err… XP Mode. In my case, I use it purely for support purpose. Being software engineering sometimes we get to work in level 2 – 3 support requests and I really hate to install 3rd party vpn or remoting applications in my workstation. In this situation, this XP Mode is life saver …
Recently I had to connect to some customer over vpn and one of the requirement for that network is that client needs to have antivirus installed in it. This being my VM for support, I never thought that I would want to install AV in it. So I was Googleing for AV software that can be installed on XP and natually I thought that I would want to use MSFT Security Essentials because it’s very light weight (how good it is at protecting things is totally different story). But to my surprise, I found that XP is not supported by MSFT, instead it suggested that I upgrade to newer OS !!
I like to spend time with Oracle DB just as much time I spend with SQL Server, but we exclusively use SQL Server at our work so I am not getting enough time with Oracle anymore. And another reason is it with Oracle there are way too many variable to consider when you are troubleshooting something. So when couple of days back when I boot up my VM of Oracle, I ran into this strange error and I was genuinely surprised to find how minute the cause could be.
So, this how the story goes …. after booting my VM, I started SQL PLUS utility (it is kind of SQLCMD equivalent of SQL Server, it is CLI to access Oracle DB to be exact). When I was asked to provide login credentials, when I provided ‘em I was greeted with following error message,
ORA-12560: TNS: protocol adapter error
Visual Studio 2008 full installation had always included Business Intelligence Development Studio (BIDS) with it. But for whatever reasons MSFT decided to skip that part in VS 2010(may be because there was no major release SQL Server during that time) and it was missing for very long time till release of next major SQL Server release aka.. SQL Server 2012. Even at that point there was no BIDS or similar tool set available in VS 2010/12 till MSFT released SQL Server Data Tools BI Studio for VS 2012.
So after I got VS 2013 edition installed on my system I was trying to install SSDT BI for VS 2013 so I can play with it on my new VS. But to my surprise, when I started installation it failed on a step where it check for pre-requisites with error about having different architecture which is understandable since I am using x64 bit system. So I looked for 64bit installation for SSDT BI and found that there is no such installation !!
I rely on great windows utility called Snipping tool both at work and at home to take screenshots of different things to write and keep things in records. And in past I have tried other screenshot replacement tools like Green Shot and Snag It but they are too much for my simple needs to take screenshot. So today when this tool stopped working in my home system, it was my top priority to fix it …
There were bunch of solutions explained over different forums including repairing office, killing another running snipping exe, reinstalling tablet pc component etc but none of them worked. One of the suggestion was to do system restore but that will not work for me either (because I have always felt lazy to keep by system backedup to the date ).