Something has gone wild in the ILO Flash memory.
Fix
Answers to Software Questions the Experts Would Not Answer. Microsoft.NET, Java, Spring, Hibernate, JavaScript, C#, SQL Server as well as Mac, Solaris, Linux, CISCO IOS and related now include some Automotive IT! You could be having the same problem for hours like me!
rake db:create
You tried to re-build an old Visual Studio 6.0 C or C++ project in Visual Studio 2005 or 2008 and you get the following error:
Fatal error LNK1104: cannot open file 'LIBC.lib'
Root Cause:
LIBC.LIB is no longer supported in the later version of Microsoft Visual Studio product.
Possible Fix:
Use the Multi-Thread-Safe version LIBCMT.LIB instead of LIBC.LIB that may fix.
Event Source: crypt32
Event Category: None
Event ID: 8
Description:
Failed auto update retrieval of third-party root list sequence number from:
Possible Fix:
Appears that it is lacking the Intermediate CA Certification.
Add a cert manually from: http://www.verisign.com/support/verisign-intermediate-ca/secure-site-pro-intermediate/index.html
We have numerous situations at work where we need to debug issues at customer sites remotely. It is a huge hassle to install a development environment and source code and even source code control system at customer sites each time there is some hard-to-track crash or bug that we need to attend to.
Fortunately modern Visual Studio environment supports remote debugging. With the ubiquitous availability of VPNs this has became easier but there are still some challenges exist. I am sure that you have also been puzzled by why your system won't connect with the remote to begin a debug session, or get all sorts of different messages which all boil down to some connectivity and authentication issues.
I just got this to work (finally) with one of our customers using Visual Studio 2005 debugging environment. Both my system and the customer system was in different domains, so before I forget what hoops I had to jump through to get this going, I am going to document that here so that at least I can refer to this article myself.
I am sure that this is similar with 2008. We are using Windows XPs between the two.
The Most Important Gotcha Concept
The most important requirement for the remote debugging connection to work is the understanding of the following facts.
The Cookie Cutter Method
If remote debugging isn't working, at least some basic stuff going by creating some simple Hello World type app and use the following to see if you can connect and debug at all.
Time Took To Research and Fix This
About year and half.
You have set up an IIS server on the Internet on Microsoft Windows 2003 R2 server. Everything appears to be going normally. You can FTP to "yourself" from within the same server, so you know FTP is working. Now you find out that people cannot see the directory when they connect to the FTP server. They can log in and connect but connection breaks as soon as the user tries to get a directory listing or try to send a file.
The Cause:
Your IIS Server, by default, does not support Passive FTP, and whoever trying to access your FTP server is opening the FTP server behind their own firewall and Network Address Translation (NAT). That's 99% of the case from Cable Modem and DSL users.
The Fix:
You will need to do two things.
Using wscript, you need to configure the IIS Metabase so that IIS allows the use of ports for Passive FTP, then restart the IIS.
Using anther batch script, you will need to add EACH port number in the Windows firewall exceptions list.
This site seems to give you the complete information on the whole issue and how to fix it step by step.
http://velikan.net/iis-passive-ftp/