Came across this error today:
HTTP Error 500.0 – Internal Server Error C:\PHP\php-cgi.exe – The FastCGI process exited unexpectedly
I was working on a Windows Server 2012 R2 with IIS installed.
After installing PHP 5.6 the error occured when trying to access any php files.
So apparently you need VC++ 11 runtime for PHP 5.5 or newer.
the solution was quick, download, install and iisreset (http://www.microsoft.com/en-us/download/details.aspx?id=30679)
Make sure you download and install the x86 version (vcredist_x86.exe), PHP on Windows isn’t 64 bit yet.
If you’re running PHP 5.4.x then you need to install the VC++9 runtime (http://www.microsoft.com/en-us/download/details.aspx?id=5582)
I know that there are some questions about, how to include msvcr120.dll/msvcp120.dll into your project.
If you want to drop that dependency. If you compile the program in release version, in Visual Studio 2013/2015 and do not depend on any VS-specific commands (
#pragma etc.) or precompiled headers etc.
If you want to compile it to one single release .exe and provide it to user WITHOUT demanding enduser to install VC++ Redistributes for VS
You can statically link the runtime to your project by setting the
/MT flag. You can find this option in Visual Studio 2013/2015 under Project > [ProjectName] Properties… > Configuration Properties > C/C++ > Code Generation > Runtime Library. Make sure to only set it for the Release configuration.
Getting tired of the John and Jane doe testing account names?
Here some funny and creative ones — let me know if you got some to add 🙂
Owa Tegyu Siam
Chuck U Farley
Solomon I. Lands
Loo King Good
Sum Dum Chum
So Soo Mee
Kisme U. Fool
Phil D Basket
There seems to be some doubt about Office 2016 when to install 64-bit version of office vs 32-bit
Limitations of the 64-bit version of Office
The 64-bit version of Office may perform better in some cases, but there are limitations:
- Solutions using ActiveX controls library, ComCtl controls won’t work.
- Third-party ActiveX controls and add-ins won’t work.
- Visual Basic for Applications (VBA) that contain Declare statements won’t work in the 64-bit version of Office without being updated.
- Compiled Access databases, like .MDE and .ACCDE files, won’t work unless they’re specifically written for the 64-bit version of Office.
- In SharePoint, the list view won’t be available.
If you have specific add-ins that you use in the 32-bit version of Office, they may not work in 64-bit Office, and vice versa. If you’re concerned, check your current version of Office before installing the new one. Considering testing the add-in with 64-bit Office, or finding out if a 64-bit version of the add-in is available from the developer.
The 64-bit version of Office has some limitations, but is the right choice when:
- You work with extremely large data sets, like enterprise-scale Excel workbooks with complex calculations, many PivotTables, connections to external databases, PowerPivot, PowerMap, or PowerView. The 64-bit version of Office may perform better for you.
- You work with extremely large pictures, videos, or animations in PowerPoint. The 64-bit version of Office may be better suited to handle these complex slide decks.
- You work with extremely large Word documents. The 64-bit version of Office may be better suited to handle Word documents with large tables, graphics, or other objects.
- You’re working with files over 2GB in Project, especially if the project has many subprojects.
- You want to keep the 64-bit version of Office that you’re already using. The 32-bit and 64-bit versions of Office programs aren’t compatible, so you can’t install both on the same computer.
- You’re developing in-house Office solutions, like add-ins or document-level customizations.
- Your organization requires Hardware Data Execution Prevention (DEP) be enforced for Office applications. DEP is a set of hardware and software technologies that some organizations use to enhance security.
Synology’s “secret” telnet password….
If you ever had to recover a Synology nas box in recovery-mode, pre DiskStation installation or after a failed DiskStation install….. Then you would need the “secret” telnet password for admin (or in some cases root)
In case you don’t want to contact Synology here is how it’s generated
- 1st character = month in hexadecimal, lower case (1=Jan, … , a=Oct, b=Nov, c=Dec)
- 2-3 = month in decimal, zero padded and starting in 1 (01, 02, 03, …, 11, 12)
- 4 = dash
- 5-6 = day of the month in hex (01, 02 .., 0A, .., 1F)
- 7-8 = greatest common divisor between month and day, zero padded. This is always a number between 01 and 12.
So, let’s say today is October 15, the password would be: a10-0f05 (a = month in hex, 10 = month in dec, 0f = day in hex, 05 = greatest divisor between 10 and 15).
In some cases the clock is also set to factory default… then try the password: 101-0101
Based on the original correct_password.c source,here is a short snippet to generate the daily password.
struct timeval tvTime;
struct tm tmOutput;
tmOutput.tm_mon += 1;
printf("password for today is: %x%02d-%02x%02d\n\n",
tmOutput.tm_mon, tmOutput.tm_mon, tmOutput.tm_mday,
int gcd(int a, int b)
I’ve been using Pidgin for ages…
In Pidgin I’m able to run the following protocols
- -XMPP (facebook)
- Office Communicator (for Lync and O365)
- Skype for Business
- ….. and lots more.. see the full list at Pidgin Thirdparty plugins
You should try it, if you like me prefer to keep your conversation history’s together and sorted.
One thing i’ve noticed, for some reason Office 365 (Lync or now Skype for Business) requires me to use a specific user agent(!) so….having problems getting it to work? Maybe you see:
Connection refused with error message
“You are currently not using the recommended version of the client”
“You have been rejected by the server: https://portal.microsoftonline.com/download/lync.aspx”
Cry no more!
Here is a list of user agents and versions you can emulate, and it works great! Just modify your connection profile, under advanced, type one of the following user agent values..
|Version / Product
||User Agent values (as seen in the wild)
|Lync 2013 and Office 365
UCCAPI/15.0.4481.1000 OC/15.0.4481.1000 (Microsoft Lync)
UCCAPI/15.0.4420.1017 OC/15.0.4420.1017 (Microsoft Lync)
|Lync 2010 and Office 365
UCCAPI/4.0.7577.314 OC/4.0.7577.314 (Microsoft Lync 2010)
UCCAPI/4.0.7577.256 OC/4.0.7577.280 (Microsoft Lync 2010)
|Office Communicator 2007 R2
UCCAPI/3.5.6907.206 OC/3.5.6907.206 (Microsoft Office Communicator 2007 R2)
UCCAPI/3.5.6907.0 OC/3.5.6907.0 (Microsoft Office Communicator 2007 R2)
|Office Communicator 2007
UCCP/2.0.6362.111 OC/2.0.6362.111 (Microsoft Office Communicator)
UCCP/2.0.6362.97 OC/2.0.6362.97 (Microsoft Office Communicator)
|Office Communicator 2005
LCC/1.3.5371 (Microsoft Office Communicator 2005 1.0.559.0)
LCC/1.3.5371 (Microsoft Office Communicator 2005 1.0.559.232)
MCT Program Requirements Update – effective September 2015:
Current MCT Program Renewal Requirements: (/learning page)
- Possess a current Microsoft Certification or qualification eligible for the MCT program.
- Meet the minimum instruction quantity of at least 1 class in the previous 365 days as validated by Metrics that Matter (MTM).
- All Microsoft training (not just MOC) will be recognized as credit toward program renewal as long as it can be measured in Metrics that Matter (MTM)* – NEW
- Meet the minimum instruction quality of an average instructor score of at least 7 as validated by MTM.*
- You can check your MTM records by following these steps.
- If you taught classes but didn’t use MTM you can add the course to MTM.
*The existing exception process will still apply for ITA, Academic, Microsoft Employee (FTEs) MCTs
Changes for MCT Program Entry/Renewal– New: The MCT Program is updating our order management system to be more efficient and to better serve your needs. In doing so, we are making the following changes:
- MCT Renewal Window Extended to 90 Days
- The renewal window for MCTs and MCT Alumni has been extended from 30 days to 90 days. MCTs and MCT Alumni can now start to renew their membership 90 days prior to their anniversary date. All MCTs and MCT Alumni will be receiving email renewal reminders 90, 60, 30, and 15 days prior to their anniversary date.
- Currencies and Payment Types – effective September 2015
- Currencies to be supported will be US Dollar (USD), British Pound (GBP), Australian Dollar (AUD), Euro (EUR),and Japanese Yen (JPY)
- Payment methods supported will be Credit Card and PayPal
For any questions, please refer here.
If you can’t wait for the IoT website to update, The Windows 10 IoT RTM images is already available
ARM IoT for Raspberry Pi II:
x86 IoT for Minnowboard Max:
The future of Windows is coming on July 29
To make your next Windows experience even better – We have just released the next version of Access Director. Using Access Director you will be able to secure your desktop, simple and easy!
– Run your desktop in a non-elevated user context
– Elevate only needed applications with a single click
– Elevate in your current user-context without affecting other unsecured applications like IE or Office
What’s in Access Director 3.0 ?
– Updates to support the next Windows experience (10)
– Support for integration modules
– Minor bug fixes
Get it from the Download Center
Direct Download Link
Installing UniFi controller in Debian
1. Edit /etc/apt/sources.list
# Ubiquiti UniFi updates
deb http://www.ubnt.com/downloads/unifi/distros/deb/debian debian ubiquiti
2. Add GPG keys
sudo apt-key adv –keyserver keyserver.ubuntu.com –recv C0A52C50
sudo apt-key adv –keyserver keyserver.ubuntu.com –recv 7F0CEB10
3. Run the following commands
sudo apt-get update
sudo apt-get install unifi
It should now start and be running at https://:8443/
You might have to modify the path in for java in /etc/init.d/unifi I had to change this from JAVA_HOME=/usr/lib/jvm/java-6-openjdk to JAVA_HOME=/usr/lib/jvm/java-6-openjdk-amd64
UniFi Controller default TCP ports:
unifi.shutdown.port=8081 (for management purpose)
unifi.http.port=8080 (device inform)
unifi.https.port=8443 (controller UI / API)
portal.http.port=8880 (portal redirect port for HTTP)
portal.https.port=8843 (portal redirect port for HTTPs)
unifi.db.port=27117 (local-bound port for DB server)
And UDP port 3478.