Networking - is it really important?

Networking is a word thrown around like bad appetizers. It sounds ok, but is it really good for you?
YES. You may think you have all the skills you need to do your job, and you may, for now. But tomorrow is never guaranteed, and you may be building plans for a new house instead of coding a site to control inventory, it helps to know people. You never know what you might need, but never doubt, you will need to have a resource besides your brain to ping.
Shy or not, go to the recruiters in your town to see what they know. You will have user groups, names of community leaders, and popular sites that can help you in any industry with a quick meet an greet. I may never call the guy in Texas, but if he needs to call me for help and I am later planning a vacation in his town, you bet that I'm calling to see if the resort is really 'on the beach' or washed up.
You don't have to make friends or marry the peeps you network with, you just need to remember their names and occasionally remember that what they don't know now could help you later. Technology moves at the speed of light and no one can know everything, but getting involved, volunteering with agencies on your downtime will go along way if you want to find other options for your career or life as it goes on. I know what you are thinking; I have no downtime, I have 3 kids, I don't sleep, how the f*ck can I fit in putting on my happy face to pretend to like people that I may never talk to?
Hear me out. Once a month, once a year, just go and try to attend something and shake hands, get a few email addresses, and then communicate. At 3am when you are beating your head against the wall quietly as the family sleeps and your server is down, broadcast an SOS to those email addresses. Anyone in IT knows, it's not what you know, it's who you know, and at 3 am, if you know someone that sleeps with a smartphone by their bed and is on-call themselves, they will understand where you're coming from. I am always amazed to get responses back from people around the world who I've never met, or only worked with once or twice, so be appreciative, even if you get a reply that doesn't help.
Networking can mean skipping that second, third and sometimes group interview, so be full proof. Check your Linked In, Dig, blogs, fb, and twitter accounts for random pics that may offend others before you pile on the communication. Networking is a different version of your resume, make sure it shines and impresses, you will go much further without posting the beer pong pics, I promise. If your name is Weiner, see a judge, get it changed, you will have a stigma anywhere you go, otherwise, be prepared to strategize conversation topics about your life as seen on the web.
Networking today also means relationships tomorrow, so if you are happy coding away in a corner; wake up and realize you want a family or someone to watch your dog, there is a better chance to look around from the contacts who know you than trying to pick up milk and a date. Great minds think alike, and if you are willing to put in the effort to be known among your local community for technology, civic duties, volunteering, or even a run club, you will find more people to brainstorm and pontificate about all the life haps.

The compiler failed with error code -1073741819

Ok, if you copy and paste a file into production and then check your site to find this error:

The compiler failed with error code -1073741819, or an error with a very similar number sequence and more info only pointing to where .net framework is running syswow64 or under the 2.0 folder/temp files.... do not be alarmed. Try these steps.

A) Recycle the app pool for site.

B) Restart site.

C) if you see the compilation error begin to appear on other sites on the same server, restart IIS, while IIS is stopped, go to C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files and delete the files in that folder.

D) Reboot.

I read around and found that the compiler errors could later cause a hard drive failure to rear its ugly head and some folks rebuilt the server because they kept seeing the errors return, however, these steps will help in the meantime before you have to jump through holy hoops.

MIVA empresa install 5.06 on test server

Recently, I tried to set up a test site of our old MIVA driven site. Not an easy task since MIVA will not run on IIS 7 and our server has the luck of being one that was originally a W2K box that got upgraded to 2003 and has subsequently received several MVIA updates/upgrades over the years also. I called MIVA and was told to just 'copy the files over to a new server and set up a new subdomain.' This=bad instruction. I copied all the files, the data files and in IIS on a correct install you will find a tab on the properties of the sites running MIVA that have a MIVA tab with input boxes for pointing to the correct path of data files and certs. If you don't have the tab, you have to run an install. My trouble, I had Miva v5.06 running. First, there is no download of 5.06, so forget that, it won't be found. Install the zip file 5.12 that you can download from the MIVA support site. Now, just to the meat. If you know IIS 6, you can set up the site, assign permission, or look up another site for help. Put the correct information in the MIVA tab input boxes, bounce the site, app pool, maybe even IIS to get it all to jive. Now, you still have to make some modifications if you have done what I did - copy the MySql db from prod down to this new box. You will need to edit the domains table entries that have your production URL embedded and replace it with the test URL for it to be an accessible admin area. The only issue I have had after making this setup was getting uploads for new modules to work.
However, there is a workaround for that too. If you copy the module files to your server in the 'modules' folder, then go to the Global settings in the store - hit add module, and instead of hitting upload, put the 'modules/nameoffile.mvc' in the input box and click Add, you will have success.