Tuesday, December 25, 2007
Friday, December 7, 2007
MOSS Errors
Now, I do have an answer to the following error messages:
Error 1:
While trying to backup the whole farm, I saw the error message:
Object Shared Search Index failed in event OnPrepareBackup. For more information, see the error log located in the backup directory. UnauthorizedAccessException: Retrieving the COM class factory for component with CLSID {3D42CCB1-4665-4620-92A3-478F47389230} failed due to the following error: 80070005.
Event Viewer Error messages
Error 2:
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Timer
Event ID: 6398
Date: 12/7/2007
Time: 1:47:40 PM
User: N/A
Computer: ****ServerName******WIKI
Description:The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID 1f3483b5-34a2-421a-9f3f-92a9c5251363) threw an exception. More information is included below.
Retrieving the COM class factory for component with CLSID {3D42CCB1-4665-4620-92A3-478F47389230} failed due to the following error: 80070005.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Error 3:
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6481
Date: 12/7/2007
Time: 1:47:33 PM
User: N/A
Computer: ****ServerName******WIKI
Description:Application Server job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (1a9460af-60a2-4fc5-8fb2-c53f9a48063a).
Reason: Retrieving the COM class factory for component with CLSID {3D42CCB1-4665-4620-92A3-478F47389230} failed due to the following error: 80070005.
Techinal Support Details:System.UnauthorizedAccessException: Retrieving the COM class factory for component with CLSID {3D42CCB1-4665-4620-92A3-478F47389230} failed due to the following error: 80070005. at System.Runtime.Remoting.RemotingServices.AllocateUninitializedObject(RuntimeType objectType) at System.Runtime.Remoting.RemotingServices.AllocateUninitializedObject(Type objectType) at System.Runtime.Remoting.Activation.ActivationServices.CreateInstance(Type serverType) at System.Runtime.Remoting.Activation.ActivationServices.IsCurrentContextOK(Type serverType, Object[] props, Boolean bNewObj) at Microsoft.Office.Server.Search.Administration.Gatherer.get_AdminObject() at Microsoft.Office.Server.Search.Administration.Gatherer.ProvisionGlobalProperties() at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize() at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Solution:
The application pool account needs to be given launch & activate permission to the DCOM 'osearch' service. In my case it was the network service which was getting accessed denied. I had to give it the permissions and there were no errors in the eventviewer.
- Start -> Run -> DCOMCNFG
- Component Services ->Computers->My Computer->DCOM Config
- Look for osearch and right click it to give lauch, activate permissions to the desired account
- Sometimes you need to give the IISWAM REG ADMIN service.
Hope this helps someone.
Posted by
Prashanth Palakollu
at
3:28 PM
3
comments
Labels: MOSS 2007
Thursday, December 6, 2007
I am back !
Posted by
Prashanth Palakollu
at
9:52 PM
0
comments
Labels: General
Tuesday, October 9, 2007
REMIX 2007 at Boston
Posted by
Prashanth Palakollu
at
10:54 PM
0
comments
Labels: General
Thursday, October 4, 2007
How to become a DBA from a Developer
Brad gave some real good tips for becoming a better DBA.
Here are a few tips from the show:
- Love the DBA work. If you are not going to love something, you will never be able to understand it.
- Take responsibility. This is the only way you will be able to learn something new.
- Understand your organization's data. This will help you a lot in better structuring your databases.
- You have to be a good Problem Solver.
- Read Books...this is one of the easiest ways to learn something quickly. I still prefer books to electronic media.
- Take Classes/Training.
- Participate in forums.
- Be active in your community and attend events (like PASS).
- Always keep looking for the Dirtiest, hardest jobs. This will help you by giving you new harder challenges everyday.....keeps your brain sharp.
- Be proactive (prepare for next failure).
Thanks for the great show guys and keep on coming up with such shows....
Posted by
Prashanth Palakollu
at
11:41 PM
0
comments
Labels: SQL Server 2008
Wednesday, October 3, 2007
Moving SSIS packages from Development to Production
First Error:
a)Failed to decrypt protected XML node "PackagePassword" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.
b)Failed to decrypt protected XML node "DTS:Property" with error 0x80070002 "The system cannot find the file specified.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.
This happens because of the package protection level which is by default set to "EncryptWithSensitiveKey". Setting the package protection level to "DontSaveSensitive" helped me to remove these errors. This can be done by right clicking the package in the designer and changing the properties
Also, I setup the proxy sever agent so that the package runs under my account(the one which created the package)
Second Error:
After the first error was resolved, now was the time to run the packages. When I ran the package, it threw an error which was something like this:
SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "*****" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed
The error was happening in an access datasource. I went back into the package configuration file and removed the initial catalog parameter value(which was empty by the way) and voila, it worked.
This post helped me to get through :
https://forums.microsoft.com/msdn/showpost.aspx?postid=73863&siteid=1
Posted by
Prashanth Palakollu
at
4:36 PM
5
comments
Labels: SQL Server 2008
Thursday, September 20, 2007
Code Camp
Posted by
Prashanth Palakollu
at
7:34 PM
0
comments
Labels: General