Charbel's blog

 So here I was, conducting a training for a customer, and I was showing the Excel Services features. I started creating an Excel sheet with dummy data, I created a chart from it and published it on SharePoint.

All goes well but when I opened the sheet from the document library, the Excel Services tried to render the graph in the web but than it failed saying that the Excel Calculation Services failed to show the chart. I was surprised a little bit, there is nothing fancy or complex in the graph, so why didn't it show?

After some thinking, I noticed that the color quality in my virtual machine dropped to 8 bit when I connected my machine to the projector. I disconnected it, modified the color quality to 24 bit and tried again: it worked

It seems that the Excel Calculation Services depends on the color quality on the server even though the graph was shown successfully in Excel client!!!
 

Are you having trouble configuring the SSO service on SharePoint 2007 and receiving the following message: "Failed to connect to the database server"?

If this is the case, you might want to look at the newly posted article in knowledge base:

http://support.microsoft.com/kb/944104

Last Wednesday I past my last SharePoint exam (70-542: Microsoft Office SharePoint Server 2007 – Application Development). With this done, I am now SharePoint certified. Boy the last exam was difficult.

I am happy now that the exams are old news now . Good luck for those out there who wish to be certified!!!

This is my first post after the big crash it's been a long time.

anyway, for anyone out there trying to become a leader or already a leader the below article is useful. This one is taken from the Hacknot site.

19 mistakes technical leaders fall into listed below:

1. Assuming the team serves you
2. Isolating yourself from the team
3. Employing hokey motivation techniques
4. Not providing technical direction and context
5. Fulfilling your own needs via the team
6. Focusing on your individual contribution
7. Trying to be technically omniscient
8. Failing to delegate effectively
9. Being ignorant of your own shortcomings
10. Failing to represent the best interests of your team
11. Failing to anticipate
12. Repeat mistakes others have already made
13. Using the project to pursue your own technical interests
14. Not maintaining technical involvement
15. Playing the game rather than focusing on the target
16. Avoiding conflict
17. Putting the project before the people
18. Expecting everyone to think and act like you
19. Failing to demonstrate compassion