Hi Shirley,

Much obliged. Sometimes it's hard to see what's poking you in the eye J.
It's working for me too now! Yeehaa!

Cheers, Wilson

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Shirley
Sent: Monday, 11 August 2008 11:03
To: [email protected]
Subject: RE: [OzMOSS] BDC Search crawling error: content access account
cannot be decrypted ...

 

Hi,

 

I had the same issue last Friday...I performed the following steps and
it solved the issue...

1.      Open SharePoint Central Administration, and on the left below
Shared Services Administration click on the Shared Service Provider with
the search configuration you want to change (e.g. SharedServices1). 
2.      Under Search, click Search settings. Click Default content
access account. 
3.      Enter the credentials, confirm the password and click OK. 

Hope this helps...

 

Regards,

Shirley.

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Wampers, Wilson [Talent International]
Sent: Monday, August 11, 2008 12:08 PM
To: [email protected]
Subject: [OzMOSS] BDC Search crawling error: content access account
cannot be decrypted ...

 

Hi All,

 

As a test run I've configured a BDC application definition against a
simple SQL Server 2005 Express DB using Pass Through Windows
Authentication for SqlServer.

The SSP BDC Application shows crawlable = yes.

In the site collection BDC web parts using this data object work fine.
And immediately return changes to the database content when changes are
made.

 

I've created a domain account and assigned domain admin rights to it (to
circumvent any potential issues).

This account has also policy permissions log on batch locally and as a
service ...

The SSP app pool is configured with that domain account called
'domain\svc_search'.

This account has sql db_securityadmin rights for the database to be
crawled.

The Office Search Service runs with this log on account as well.

The Windows SharePoint Services Search log on account is this account as
well.

DCOM Config components OSearch and SPSearch Security have Launch &
Activation Permissions: Local Launch and Local Activation rights for the
account.

When I specify a crawl rule
bdc://49128c53-6bd3-46e7-8651-5d27a7e78afa/*, I have the impressions
this part works.

 

 

 

But I still get the following error:

 

 

 

*         bdc2://49128c53-6bd3-46e7-8651-5d27a7e78afa/1152

The password for the content access account cannot be decrypted because
it was stored with different credentials. Re-type the password for the
account used to crawl this content.

 

I've tried several ways re-typing the password for the ad account logged
on as this or that or the other etc...

Deleted the BDC app several times and re-created using different logon
accounts etc...

Configured search in a similar fashion etc...

 

If anyone can make out what's going wrong and how to fix this, it would
be greatly appreciated.

 

Cheers, Wilson Wampers

 

-------------------------------------------------------------------
OzMOSS.com - to unsubscribe from this list, send a message back to the
list with 'unsubscribe' as the subject.
Powered by mailenable.com 

No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.138 / Virus Database: 270.6.0/1601 - Release Date: 8/8/2008
9:02 AM

-------------------------------------------------------------------
OzMOSS.com - to unsubscribe from this list, send a message back to the
list with 'unsubscribe' as the subject.
Powered by mailenable.com 




------------------------------------------------------------------- OzMOSS.com 
- to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject.

Powered by mailenable.com

<<image001.png>>

<<image002.png>>

Reply via email to