Today a colleague had an issue with the log service of SharePoint 2010.
Atleast that is what we thought 🙂
After checking all the services of SharePoint, services of the Windows Server and the event viewer, we still didn’t found out why SharePoint wouldn’t log.
So when we ran out of options, we checked how much free space was left on the disk. And this was the problem, only 200MB’s were free.
After freeing up some space, the logging ran again and everything was back to normal.
So lessons learned: Check the things first that you normally would take for granted. Keep in mind the KIS principle and happy hunting for bugs
Today is a first in four series to complete the SharePoint 2010 exams course.
I’ve achieved the first exam (Application Development), 3 more to go 🙂
I’ll keep you updated.
I hear and I forget.
I see and I remember.
I do and I understand.
I found that above text is something that describes a developer 😀
Text came from this link
It has something to do with a new community tool and CAML 🙂
more info will follow in due time.
The first drafts have been made and it’s looking very nice
I’m busy with Silverlight + SharePoint 2010 in Visual studio 2010.
All went well , but suddenly I’ve received an error with the mention of “ValidateXaml” task failed unexpectedly.
Ok reading the error furthur there was a mention of System.Windows not being found on the server.
That’s strange because the reference was right there.
The solution isn’t best case but it did the job for me.
Just go to c:program files(x86)references assembliesMicrosoftFrameworkSilverlightv3.0
Add System.dll, System.windows.dll and System.core.dll to the gac via gacutil.exe (gacutil /i “name of file of dll”).
My thanks to Gill Cleeren for finding this solution for me.
Lotz to blog about so soon to come 🙂
Coming soon to a blog near you 🙂