Archive: Posts Tagged ‘SharePoint 2007’

Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

No comments July 8th, 2010

This error seems to pop up quite often, and it’s a little frustrating when your first encounter it. When I experienced it, I was attempting to schedule a crawl from the SharePoint 2007 Search Administration. I was able to manually run full and incremental crawls but not schedule them.

The issue was actually pretty simple to resolve. Since these scheduled events are scheduled much like any other windows task, using the windows scheduled tasks, we just need to insure SharePoint has access to add new jobs in there. We’ll do this by adding WSS_WPG with read/write permissions to C:\%windir%\tasks. Follow these steps:

  1. Open CMD, and RUN attrib –s %windir%\tasks (Changes the view of the folder so you can edit the ACL permissions)
  2. In Windows Explorer, browse to C:\%windir%, right-click the Tasks folder, and then click Properties.
  3. Add the WSS_WPG group
  4. Assign Read/Write Permissions
  5. Click OK
  6. attrib +s %windir%\tasks (This resets the Tasks Property back to the default view)

Once the above has been completed you should be able to schedule a full or incremental crawl.

Using a Script Configuration to SharePoint -vs- Using the Configuration Wizard.

No comments April 16th, 2010

I’ve been deploying SharePoint for years, I’ve always used the Microsoft Office SharePoint Configuration Wizard to configure the farm.  Recently I had a customer ask me how they could customize the name of the AdminContent database that the wizard randomly names it something like:

SharePoint_AdminContent_d9843542-d33d-43f7-a820-d8803f8f3fc5

I’ve never minded this much; however,  if you happen to be using the same SQL server instance for multiple SharePoint deployments, it could get confusing as to which AdminContent goes with which farm, or maybe you want ALL your your SharePoint databases to follow a certain naming convention.

Whatever the reason might be,  I put together this small script that will allow you to customize the AdminContent database name as well as being able to offer the ability to hand your customer or whoever a sure way of configuring SharePoint the same every time:

cd\
cd C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN
PSConfig.exe -cmd configdb -create -server SQLServerName\Instance -database NameOfConfigDB -user DOMAIN\FarmAdminAccount -password FarmAdminPassword -admincontentdatabase NameOfAdminContentDB
psconfig.exe -cmd helpcollections installall
psconfig.exe -cmd secureresources
psconfig.exe -cmd services -install
stsadm -o spsearch -action start -farmserviceaccount DOMAIN\WSSSearchAccount -farmservicepassword WSSSearchPassword
stsadm -o osearch -action start -role IndexQuery -farmserviceaccount DOMAIN/OfficeSearchAccount -farmservicepassword OfficeSearchPassword -farmcontactemail name@domain.com
psconfig.exe -cmd services -provision
psconfig.exe -cmd installfeatures
psconfig.exe -cmd adminvs -provision -port PortNumberForCentralAdmin –windowsauthprovider onlyusentlm
psconfig.exe -cmd applicationcontent -installcode

For a complete reference of commands and switches, please visit:

http://technet.microsoft.com/en-us/library/cc288944.aspx

Authentication failed because the remote party has closed the transport stream.

2 comments September 14th, 2009

If you receiver the error “Authentication failed because the remote party has closed the transport stream” when accessing “Search Settings” in the SSP, the following steps will resolve the issue. The issue is a result of an incorrect self-serving-certificate.

1. Install the IIS 6.0 Resource Kit on the index server (http://www.microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&DisplayLang=en)

2. Assign a new SSL certificate to the Office SharePoint Server Web Services site on the index server using the SELFSSL tool from the resource kit.

SELFSSL.EXE /S:951338967 /K:1024 /V:1825 /P:56738

The /S and /P parameters specify the web site ID and port number, respectively, of the Office SharePoint Server Web Services site in IIS. They should be set to the appropriate values for your environment.