Troubleshooting Dynamics AX 2009 Enterprise Portal Unable to generate a temporary class

Recently, I bumped on this error while troubleshooting a webpart in AX 2009

Error

Server was unable to process request. ---> Unable to generate a temporary class (result=1).
error CS2001: Source file 'C:\WINDOWS\TEMP\vmeyu2da.0.cs' could not be found
error CS2008: No inputs specified

Solution:

Give the app pool iis account read/write permissions to c:\windows\temp folder

How to uninstall Windows Internal database for Windows Sharepoint Services 3.0

Greetings All!

It's been a while since I was last here. I was away for a while to meet some personal commitments and also my work life kept me busy.

I would like to share a recent experience where I had to troubleshoot a WSS 3.0 installation where it was using Windows Internal database instead of SQL

I found this technet article helpful to uninstall Windows Internal database

 https://technet.microsoft.com/en-us/library/cc708610(v=ws.10).aspx

Hope it might help somebody out there!

Troubleshooting Sharepoint Search Errors - Part 2

A while ago, I had to put my Sharepoint hat to troubleshoot the below issues. If you have worked on Sharepoint as an Admin, you will agree with me that Sharepoint errors are more complex to troubleshoot compared to other tools in MS Stack. The error messages sometimes don't convey the right meaning. 

Ok, let's jump into the various errors which was logged in Event Viewer and the solution for them

Error #2

Event Type:        Error

Event Source:    Office Server Search

Event Category:  Search service

Event ID:              10038

Description:

Query machine <xyz> has been taken out of rotation due to this error: The object is not initialzed.   0x8004180b. It will be retried in 15 seconds. Component: 3a87986b-8ffe-41db-ae22-5e3fd1b9f4d9

Error #3

Event Type:        Warning

Event Source:    Office Server Search

Event Category:  Search service

Event ID:              10039

Description:

Retry of query machine <xyz> has failed with error: The object is not initialzed.   0x8004180b.  It will be retried again in 60 seconds. Component: 3a87986b-8ffe-41db-ae22-5e3fd1b9f4d9

Error #4

Event Type:        Error

Event Source:    Office Server Search

Event Category:  Content index server

Event ID:              4127

Description:

Content index on Portal_Content could not be initialized. Error The system cannot find the file specified.   0x80070002.Component: 3a87986b-8ffe-41db-ae22-5e3fd1b9f4d9

Error# 5 (While Searching from Portal, you get the below errors)

“Your search cannot be completed because of a service error”

"The search request was unable to connect to the Search Service"

Error #6

Event Type:       Error

Event Source:    Office SharePoint Server

Event Category: Office Server Shared Services

Event ID:          6482

Description:

Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (8fd1e03c-96df-4b7a-bd33-8da3fa924f03).

Reason: Object 3a87986b-8ffe-41db-ae22-5e3fd1b9f4d9 not found.

Techinal Support Details:

System.Collections.Generic.KeyNotFoundException: Object 3a87986b-8ffe-41db-ae22-5e3fd1b9f4d9 not found.

   at Microsoft.Office.Server.Search.Administration.SearchApi.get_App()

   at Microsoft.Office.Server.Search.Administration.SearchApi.SetUsersPermittedToQuery(String[] userNames, Boolean force)

   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()

   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

Solution for Errors 2, 3, 4, 5 and 6

Sometime back, I moved our Sharepoint Databases to a different DB Server and since then the Search was broken; maybe the index file got corrupted during the move.

I had to do the following inorder to bring back the search:

1.       Go to CA > Operations > Services on Server > Click on Office Sharepoint Server Search > Configure Sharepoint Server Search Service and checked Use this server for serving search queries

          Then go to CA > Application Management > Manage this Farms Shared Services > New Shared Services Provider to fix the indexer as <<prod-servername>> and change the index location here toD:\SharepointIndex\Config as C:\ was getting full.

3.       Go to CA > Application Management > Create or configure this farm’s shared services.

4.       Go to Manage this Farms Shared Services page, click the SSP

5.       On the Shared Services Administration Home page, click Search settings in the Search section.

6.       On the Configure Search Settings page, click Reset all crawled content in the Crawl Settings section.

7.       By default, the Deactivate search alerts during reset check box is selected on the Reset Crawled Content page. This option prevents users who have search alerts configured from being sent unnecessary e-mail messages when the crawled content is reset. Click to clear this check box if you do not want to disable alerts during the reset operation.

8.       Click Reset Now.

9.       In the message box, click OK to confirm that you want to reset the search content index.

1 

Go back to the Shared Services Administration Home page, click Search settings in the Search section.

11.   Click Content sources and crawl schedules.

12.   Drop the menu down for the Source you want to crawl, click Start Full Crawl.

Below is a list of references/links which i found useful during my troubleshooting exercise: (Maybe someone might find useful out there)

http://www.informationworker.co.za/blogs/mirror/Lists/Posts/Post.aspx?ID=1292

http://technet.microsoft.com/en-us/library/cc850697(office.12).aspx

http://sharepointdiva.wordpress.com/2008/05/29/office-sharepoint-server-search-service-stuck/

http://technet.microsoft.com/en-us/library/cc263244(office.12).aspx

http://blogs.msdn.com/b/miketag/archive/2007/07/05/estimate-moss-search-disk-space-requirements.aspx

http://www.chandima.net/Blog/archive/2008/04/10/moving-sharepoint-search-index-location.aspx

http://nikspatel.wordpress.com/2009/03/05/moving-index-file-locations-on-the-moss-index-and-query-servers/

http://dsen-25.blogspot.com/2010/09/moss-search-error-content-index-is.html?showComment=1327622531349#c3141394064941424823

http://blog.jussipalo.com/2008/01/moss-system-cannot-find-file-specified.html

http://bytelab.blogspot.com/2008_09_01_archive.html

Troubleshooting Sharepoint Error - The search application for SSP1 on the server is not provisioned

It's been a while since I did some posting on my blog. Was bit busy these days. A few weeks ago, I had put my Sharepoint admin hat to troubleshoot some search errors in our farm. Thought to share on how I went with troubleshooting one of them..

Error# 1

The search application for 'SSP1' on server <xyz> is not provisioned. Confirm that the Windows SharePoint Services Timer service and Windows SharePoint Services Administration service are running on the server.

Solution

1. Central Administration > Operations > Global Configuration > Timer job definitions > Application Server Administration Service Timer Job > Disable

2. Then open windows administrative services (services.msc), stop Windows SharePoint Services Timer

3. Navigate to C:\Documents and Settings\all users\application data\microsoft\sharepoint\Config\ , Open the Recent GUID Folder and delete only the XML files from the directory, then open the

cache.ini and change the number in it to 1.

4. Start Windows SharePoint Services Timer and give it a few seconds so that the new XML files from the location you deleted then are re-populated.

5. Central Administration > Operations > Global Configuration > Timer job definitions > Application Server Administration Service Timer Job > Enable.

How to move Sharepoint Databases from one Server to another

Dear Friends,

A while ago, I was involved in upgrading our Sharepoint SQL Server databases and had them move from one server to another. Initially, I was under the impression that moving Sharepoint databases would be as simple as detaching databases from one server and attaching it to the destination server. But it's not easy as said, with sharepoint the databases are tightly coupled with the web applications, so I had to go through a series of steps to complete the move.

Note - In case if you are trying out these steps, I would highly recommend to perform these steps first on your TEST Environment.

In case, you are not able to view the embedded document below, please go to this link https://docs.google.com/document/pub?id=1VtAlH8I0v5yz50Yt7PmvGai_tbcHgRaed0cSC56EROk