I recently was trying to create a SharePoint site and was surprised to see a “File Not Found.” error when I submitted the action. After scratching my head for a short amount of time, I remembered that I had created a managed path that was the same name as the site I was trying to create.
After removing the managed path, I was able to create my site and go merrily along my way.
I have recently been having some Address Book sync problems with Office Communicator 2007 R2. A couple things I wanted to share with anyone who cares to listen:
-When you turn on logging within Communicator, the logs are placed in your profile directory. So, at the root of your profile (i.e. for Windows XP, it would be: c:\documents and settings\%username%), open the Tracing folder. This is where the logs are created.
-When you start Communicator, it tries to download and make a local copy of the Address Book. The location of the address book copy is again located in the profile directory. So, for Windows XP, it would be: c:\documents and settings\%username%\local settings\application data\microsoft\communicator .
I have been trying to install Office Communications Server (OCS) 2007 R2 Standard Edition for a few days now without success.
During the server install process (after the schema has been extended), a warning shows up in the activation logs of every role (Standard Edition Server, Web Components Server, Web Conferencing Server, Audio/Video Conferencing Server, Application Sharing Server, and Application Host).
The warning on the main Deployment Log states:
[0x03EC796D] Wizard was successful, but one or more warnings occurred during execution of the wizard. Please check the log file for more information.
The warning within each activation log states:
[0x03EC78E4] More than one DNS records are found for the pool FQDN. Please validate the pool’s DNS registration.
A note about the DNS Record Count: 3 is also in the log.
After trying for many hours to get this to work, the solution is simple, but it isn’t ‘nice’.
Office Communications Server 2007 does not support network interface controller (NIC) teaming. Sounds crazy, right? Good luck finding this little tidbit documented anywhere.
[UPDATE] I have been told (by a Microsoft rep) that Microsoft does support NIC teaming, but I haven’t found any documentation that points to the correct answer.