In my current job I work very closely with our graphic designer. She comes up with amazing mock-ups. Colour codes are normally given to me in RGB codes. I found this great website which converts a specified RBG code into a hexadecimal string.
Here is the URL: http://www.javascripter.net/faq/rgbtohex.htm
Tuesday, May 26, 2009
Monday, May 25, 2009
Does Microsoft really test their code? (Attention: Important Information on Service Pack 2)
I was so looking forward for SharePoint 2007 Service Pack 2. I was in the middle of planning the rollout into our environments (Dev, Test and Production).
And then we received this email from Microsoft which can be also found at the SharePoint team blog. http://blogs.msdn.com/sharepoint/archive/2009/05/21/attention-important-information-on-service-pack-2.aspx
What’s going on Microsoft, do you really test your code. I love Microsoft products and have been promoting them at every opportunity. I had to put up with lot of crap today because of this.
I know there is a workaround but please please get your act together. We are so fed up of Microsoft workarounds.
And then we received this email from Microsoft which can be also found at the SharePoint team blog. http://blogs.msdn.com/sharepoint/archive/2009/05/21/attention-important-information-on-service-pack-2.aspx
What’s going on Microsoft, do you really test your code. I love Microsoft products and have been promoting them at every opportunity. I had to put up with lot of crap today because of this.
I know there is a workaround but please please get your act together. We are so fed up of Microsoft workarounds.
Wednesday, May 20, 2009
ActiveX controls used by Microsoft Office SharePoint Server (MOSS) 2007
Our infrastructure team is creating a new Microsoft XP image for the SOE (Standard Operating Environment). They wanted to know a list of ActiveX controls required by MOSS 2007 which could be pre-installed.
85% of our intranet is on SharePoint 2003, 15% in MOSS 2007 (We are currently migrating from SharePoint 2003 to 2007) and client machines have Office 2003 installed.
I found this really useful blog from Jose Barreto and thought of sharing it. The link is http://blogs.technet.com/josebda/archive/2007/03/26/searching-the-visible-moss-2007-code-for-activex-references.aspx.
I’ll share our experience when the testing is completed.
85% of our intranet is on SharePoint 2003, 15% in MOSS 2007 (We are currently migrating from SharePoint 2003 to 2007) and client machines have Office 2003 installed.
I found this really useful blog from Jose Barreto and thought of sharing it. The link is http://blogs.technet.com/josebda/archive/2007/03/26/searching-the-visible-moss-2007-code-for-activex-references.aspx.
I’ll share our experience when the testing is completed.
Monday, May 18, 2009
How to fix corrupted TRIM indexes?
Recently we started receiving following types of emails from the TRIM Event Processor.
TRIM Event Processor running on server reported the following message:
Error : Database: - User An error occurred updating Content Index for Record(xxxxxxx). The primary content index in folder C:\.. has a pending transaction file (C:\TRIMIndexFolder\TRIMpending.bin). This indicates that a previous call to update the index using these transactions has failed. All content indexing will cease for this database until the problem has been rectified.
This E-mail Message has been automatically generated by TRIM Context (server).
This became a very big issue because it was filling up our TRIM notification inbox. It wasn’t effecting day to day TRIM operations except for document content searches.
This is how we fixed it.
Solution 1 – Failed
These were the steps involved based on HP documentation:
1. Stop the TRIM Event Server service on your Event Server.
2. Locate the TRIMPending.bin file. This should be located in the Document Content Index folder, the location being administered by each site.
3. Rename the file ‘TRIMPending.bin’ to ‘TRIMtrans.bin’.
4. Start the Event Server service.
Solution 2 - Successful
We tried the above few times and every attempt failed. We were running out of time and finally we decided to delete the current index and recreate it. Worked like a magic. No more issues and no more automated email notifications.
These were the steps involved:
1. Stop all TRIM services (Low priority to high priority).
2. Go to Event Server and stop Document Content Indexing (DCI).
3. Remove the content index from the dataset.
4. Go to the DCI folder and delete the folder which is represented by the 2 character database identifier.
5. Go back to TRIM enterprise Manage and create the new index.
6. Reindex the newly created Content Index.
7. Check for the logs and fix any issues.
8. Go to properties of the Workgroup Server and update the Content Search Settings path.
9. Turn on Document Content Indexing(DCI) on the Event Server (Check the path).
10. Create a new DCI chain and mark the existing chain as read-only.
11. Start all TRIM Services (High priority to low priority).
12. Using Monitor Activity ensure Event Queue is back to normal.
TRIM Event Processor running on server reported the following message:
Error : Database: - User An error occurred updating Content Index for Record(xxxxxxx). The primary content index in folder C:\.. has a pending transaction file (C:\TRIMIndexFolder\TRIMpending.bin). This indicates that a previous call to update the index using these transactions has failed. All content indexing will cease for this database until the problem has been rectified.
This E-mail Message has been automatically generated by TRIM Context (server).
This became a very big issue because it was filling up our TRIM notification inbox. It wasn’t effecting day to day TRIM operations except for document content searches.
This is how we fixed it.
Solution 1 – Failed
These were the steps involved based on HP documentation:
1. Stop the TRIM Event Server service on your Event Server.
2. Locate the TRIMPending.bin file. This should be located in the Document Content Index folder, the location being administered by each site.
3. Rename the file ‘TRIMPending.bin’ to ‘TRIMtrans.bin’.
4. Start the Event Server service.
Solution 2 - Successful
We tried the above few times and every attempt failed. We were running out of time and finally we decided to delete the current index and recreate it. Worked like a magic. No more issues and no more automated email notifications.
These were the steps involved:
1. Stop all TRIM services (Low priority to high priority).
2. Go to Event Server and stop Document Content Indexing (DCI).
3. Remove the content index from the dataset.
4. Go to the DCI folder and delete the folder which is represented by the 2 character database identifier.
5. Go back to TRIM enterprise Manage and create the new index.
6. Reindex the newly created Content Index.
7. Check for the logs and fix any issues.
8. Go to properties of the Workgroup Server and update the Content Search Settings path.
9. Turn on Document Content Indexing(DCI) on the Event Server (Check the path).
10. Create a new DCI chain and mark the existing chain as read-only.
11. Start all TRIM Services (High priority to low priority).
12. Using Monitor Activity ensure Event Queue is back to normal.
Labels:
TRIM,
TRIM Event Processor,
TRIM Index (DCI)
Wednesday, May 13, 2009
How to change DotNetNuke favicon?
DNN supports favicon per portal.
- Generate a favicon.ico using a free 3rd party website. I use http://www.chami.com/html-kit/services/favicon/.
- Upload favicon.ico file to the root of the portal folder. (Example: \Portals\0, \Portals\1, \Portals\3, etc)
Thursday, May 7, 2009
My first blog.
This is my first blog entry. After 6 years of putting off, finally I’ve decided to start blogging. Main objective of my blog will be to share my knowledge and thoughts with the other. Please stay tuned…
Subscribe to:
Posts (Atom)