November 2009 Entries
FreeSSHd is a free SSH Server available for personal or commercial use. The server software can be used as an SFTP server.
Installing FreeSSHd is pretty simple and straightforward if you keep a couple of things in mind:
- On Windows 2008, you must install the software as an Administrator. Although the installation can be performed simply by clicking on the install EXE, be sure to right click and “Run as Administrator”.
- The other thing to keep in mind is that you will need to restart the windows service in order for user changes to take effect. If you do not restart...
One of our MOSS servers installed on Windows 2008 had the following periodic Application Log entry:
Tracing Service failed to create the trace log file directory 'D:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\'. Error 3: The system cannot find the path specified.
Interestingly enough there were files in the LOGS directory so at one point or another this was working.
This post suggests it is a lack of permission on the LOGS directory for the WSS_ADMIN_WPG group, but this was not the case for this server:
http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/thread/3cd056cd-73a1-43aa-99d5-3d9849b5000a
Although, the issue was a permission error on the LOGS directory, the account lacking permissions was the...
We moved things around a bit on our site and as a result we were no longer able to post blog entries with images to our blog. This was working prior to our changes using Windows Live Writer against the SubText blog engine. After a bit investigation it turned out to be a permission issue on the images directory. Adding the appropriate permissions to the images directory for the web application pool identity account on our blog corrected the problem. No more image upload is not supported would you like to set up FTP from Windows Live Writer!
Recently, while working on integrating an email notification tool with a client’s Exchange 2007 IMAP services we encountered several errors. The errors included: - “Connection is closed. 14 “ when attempting to telnet to the secure IMAP port. After walking through the Exchange configuration with our client it became apparent that the issue was likely related to an expired Exchange SSL certificate. I proceeded to reissue a new certificate and found this article helpful: Creating a Certificate or Certificate Request for TLS http://technet.microsoft.com/en-us/library/aa998840.aspx Especially...