Page 434 of 727« First...102030...432433434435436...440450460...Last »

How IIS authenticates browser clients

This article describes the different authentication methods that are available in IIS for both Microsoft Windows NT 4.0 and Microsoft Windows 2000. For a more complete description of the information discussed in this article, see the Windows NT 4.0 and Windows 2000 Resource Guides.

Authentication methods that are available for Windows NT 4.0

Anonymous – No logon is required and anyone is allowed to gain access to data that is protected with this method. The server uses a built in account (IUSR_machine name by default) to control the permissions on the files. The browser does not send any credentials or user info with this type of request.

  • Browsers Supported: Any
  • Limitations: None
  • User Rights Required: The anonymous user account defined on the server must have “Log On Locally” permissions.
  • Encryption Type: None

Basic (Clear Text) – The server requests the user to log on and a dialog box appears in the browser that allows the user to enter the credentials that are needed. These credentials must match the user credentials defined on the files that the user is attempting to access.

  • Browsers Supported: Any
  • Limitations: Not very secure. Passwords are easily deciphered.
  • User Rights Required: The user account must have “Log On Locally” permissions.
  • Encryption Type: Base 64 Encoding (not true encryption)

Windows NT Challenge/Response – The server requests the user to log on. If the browser supports Windows NT Challenge/Response, it automatically sends the user’s credentials if the user is logged on. If the domain that the user is on is different than the server’s domain, or if the user is not logged on, a dialog box appears requesting the credentials to send. Windows NT Challenge/Response uses an algorithm to generate a hash based on the user’s credentials and the computer that the user is using. It then sends this hash to the server. The browser does not send the user’s password across to the server.

  • Browsers Supported: Internet Explorer versions 3.01 and later
  • Limitations: Requires point-to-point connection. Usually, a circuit is closed after a “401 unauthorized ” error message; however, when negotiating a Windows NT Challenge/Response authentication sequence (which requires multiple round trips), the server keeps the circuit open for the duration of the sequence after the client has indicated that it will use Windows NT Challenge/Response. CERN proxies and certain other Internet devices prevent this from working. Also, Windows NT Challenge/Response does not support double-hop impersonations (in that once passed to the IIS server, the same credentials cannot be passed to a back-end server for authentication).
  • User Rights Required: The user account that is accessing the server must have “Access this computer from the network” permissions.
  • Encryption Type: NTLM Hash algorithm that is also uuencoded.

Orders of precedence:
When the browser makes a request, it always considers the first request to be Anonymous. Therefore, it does not send any credentials. If the server does not accept Anonymous OR if the Anonymous user account set on the server does not have permissions to the file being requested, the IIS server responds with an “Access Denied” error message and sends a list of the authentication types that are supported by using one of the following scenarios:

  • If Windows NT Challenge/Response is the only supported method (or if Anonymous fails), then the browser must support this method to communicate with the server. Otherwise, it cannot negotiate with the server and the user receives an “Access Denied” error message.
  • If Basic is the only supported method (or if Anonymous fails), then a dialog box appears in the browser to get the credentials, and then passes these credentials to the server. It attempts to send these credentials up to three times. If these all fail, the browser is not connected to the server.
  • If both Basic and Windows NT Challenge/Response are supported, the browser determines which method is used. If the browser supports Windows NT Challenge/Response, it uses this method and does not fall back to Basic. If Windows NT Challenge/Response is not supported, the browser uses Basic.

Notes:

  • When your browser establishes a connection with a Web site by using Basic or NTLM authentication, it does not fall back to Anonymous during the rest of that session with the server. If you try to connect to a Web page that is marked for Anonymous only after authenticating, you will be denied. (This may or may not hold true for Netscape).
  • When Internet Explorer has established a connection with the server by using Basic or NTLM authentication, it passes the credentials for every new request for the duration of the session.

Authentication methods that are available for Windows 2000 and above

Anonymous – No logon is required and anyone is allowed to gain access to data protected with this method. The server uses a built in account (IUSR_machine name by default) to control the permissions on the files. The browser does not send any credentials or user info with this type of request.

  • Browsers Supported: Any
  • Limitations: None
  • User Rights Required: The Anonymous user account defined on the server must have “Log On Locally” permissions.
  • Encryption Type: None

Basic (Clear Text) – The server requests the user to log on and a dialog box appears in the browser that allows the user to enter the credentials that are needed. These credentials must match the user credentials defined on the files that the user is attempting to access.

  • Browsers Supported: Any
  • Limitations: Not extremely secure. Passwords are easily deciphered.
  • User Rights Required: The user account must have “Log on Locally” rights
  • Encryption Type: Base 64 Encoding (not true encryption)

Digest – The server requests the user to log on and also sends a NONCE used to encrypt the password. The browser uses the NONCE to encrypt the password and sends this to the server. The server then encrypts its own copy of the user’s password and compares the two. If they match and the user has permissions, access is granted.

  • Browsers Supported: Internet Explorer 5 and later versions
  • Limitations: Not as secure as Integrated. Requires the server to have access to an Active Directory Server that is set up for Digest Authentication.
  • User Rights Required: Requires passwords to have “Save password as encrypted Clear Text”
  • Encryption Type: Based on NONCE sent by server.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

222028 

(http://support.microsoft.com/kb/222028/
)

Setting up Digest Authentication for use with Internet Information Services 5.0

Fortezza – To use Fortezza security with IIS 5.0, you need to have an appropriate Cryptographic API Service Provider (CSP) file from a Fortezza provider such as http://www.spyrus.com.

Windows Integrated (split into two sub categories)
Kerberos – The server requests a user to log on. If the browser supports Kerberos, The following takes place:

  • IIS requests authentication.
  • If the client has not logged on to a domain, a dialog box appears in Internet Explorer requesting credentials, and then contacts the KDC to request and receive a Ticket Granting Ticket. It then sends the Ticket Granting Ticket along with information about the IIS server to the KDC.
  • If the IE Client has already successfully logged into the domain and received a Ticket Granting Ticket, it sends this ticket along with info about the IIS server to the KDC
  • The KDC issues the client a Resource Ticket.
  • The Client passes this ticket to the IIS server.

Kerberos uses tickets generated at a Ticket Granting Server (KDC) to authenticate. It sends this ticket to the IIS server. The browser does NOT send the user’s password across to the server.

  • Browsers Supported: Internet Explorer versions 5.0 and above
  • Limitations: the server must have access to an Active Directory server. Both the server and the client must have a trusted connection to a KDC.
  • User Rights Required: The Anonymous user account defined on the server must have “Log On Locally” permissions.
  • Encryption type: Encrypted ticket.

Windows NT Challenge/Response – The server requests the user to log on. If the browser supports Windows NT Challenge/Response, it automatically sends the user’s credentials if the user is logged on. If the domain that the user is on is different than the server’s domain, or if the user is not logged on, a dialog box appears in Internet Explorer requesting the credentials to send. Windows NT Challenge/Response uses an algorithm to generate a hash based on the user’s credentials and the computer that the user is using. It then sends this hash to the server. The browser does not send the user’s password across to the server.

  • Browsers Supported: Internet Explorer versions 3.01 and later.
  • Limitations: Requires point-to-point connection. Typically, a circuit is closed after a “401 unauthorized ” error message; however, when negotiating an Windows NT Challenge/Response authentication sequence (which requires multiple round trips), the server keeps the circuit open for the duration of the sequence after the client has indicated that it will use Windows NT Challenge/Response. CERN proxies and certain other Internet devices prevent this from working. Also, Windows NT Challenge/Response does not support double-hop impersonations (meaning that once passed to the IIS server, the same credentials cannot be passed to a back-end server for authentication, for example, when IIS uses Windows NT Challenge/Response, it cannot then authenticate the user against a SQL Server database on another computer by using SQL Integrated security).
  • User Rights Required: The user account accessing the server must have “Access this computer from the network ” permissions.
  • Encryption Type: NTLM Hash algorithm that is also uuencoded.

Orders of precedence:
When the browser makes a request, it always considers the first request to be Anonymous. Therefore, it does not send any credentials. If the server does not accept Anonymous or if the Anonymous user account set on the server does not have permissions to the file being requested, the IIS server responds with an “Access Denied” error message and sends a list of the authentication types that are supported by using one of the following scenarios:

  • If Windows Integrated is the only supported method (or if Anonymous fails), then the browser must support this method to communicate with the server. If this fails, the server does not try any of the other methods.
  • If Basic is the only supported method (or if Anonymous fails), then a dialog box appears in the to get the credentials, and then passes these to the server. It attempts to send the credentials up to three times. If these all fail, the browser does not connect to the server.
  • If both Basic and Windows Integrated are supported, the browser determines which method is used. If the browser supports Kerberos or Windows NT Challenge/Response, it uses this method. It does not fall back to Basic. If Windows NT Challenge/Response and Kerberos are not supported, the browser uses Basic, Digest, or Fortezza if it supports these. The order of precedence here is Basic, Digest, and then Fortezza.

Notes:

  • When your browser establishes a connection with a Web site by using Basic or Windows Integrated authentication, it does not fall back to Anonymous during the rest of that session with the server. If you try to connect to a Web page that is marked for Anonymous only after authenticating, you are denied. (This may or may not hold true for Netscape).
  • When Internet Explorer has established a connection with the server by using an authentication method other than Anonymous, it automatically passes the credentials for every new request during the duration of the session.

For more information about how to configure IIS Web site authentication in Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:

324274 

(http://support.microsoft.com/kb/324274/
)

How to configure IIS Web site authentication in Windows Server 2003

For more information about issues that may occur if a Web site application pool that is hosted on IIS 6.0 recycles during the authentication process, click the following article number to view the article in the Microsoft Knowledge Base:

902160 

(http://support.microsoft.com/kb/902160/
)

You receive “HTTP Error 401″ error messages, and you intermittently cannot connect to a Web site that is hosted on IIS 6.0

See original article:
How IIS authenticates browser clients

Excel for Mac error: "The application Microsoft Excel quit unexpectedly"

When you start Microsoft Excel for Mac or when you try to open a new Excel workbook, you experience one of the following conditions: 
  • The program closes unexpectedly.
  • You receive an error message: 

The application Microsoft Excel quit unexpectedly. Mac OS X and other applications are not affected. Click relaunch to launch the application again. Click report to see more details or send a report to Apple 

To resolve this problem, follow methods listed below for your version of Office.

Excel 2008 or later

Step 1: Quit all programs and close all windows

 1. On the Apple menu, click Force Quit.

 2. Select an application in the “Force Quit Applications” window.
Note You cannot quit Finder.

 3. Click Force Quit.

Collapse this imageExpand this image

 4. Repeat the previous steps until you quit all active applications.

Step 2: Remove Excel Preferences

  1. Quit all Microsoft Office for Mac programs. 
  2. On the Go menu, click Home
  3. Open Library.
    Note The Library folder is hidden in MAC OS X Lion. To display this folder, hold down the OPTION key while you click the Go menu. 
  4. Open the Preferences folder. Click View , click Arrange by then Name. 
  5. Look for a file that is named com.microsoft.Excel.plist. 
  6. If you locate the file, click and then drag and drop the file to the Desktop. If you do not locate the file, the program is using the default preferences.  
  7. If you locate the file and move it to the desktop, start Excel, and check whether the problem still occurs. If the problem still occurs, quit Microsoft Excel, and restore the file to its original location. Then, go to the next step. If the problem seems to be resolved, you can move the com.microsoft.Excel.plist file to the trash. 
  8. Quit all Microsoft Office for Mac programs. 
  9. On the Go menu, click Home
  10. Open Library.
    Note The Library folder is hidden in MAC OS X Lion. To display this folder, hold down the OPTION key while you click the Go menu. 
  11. Open the Preferences folder. 
  12. Open the Microsoft Folder. 
  13. Look for a file that is named com.microsoft.Excel.prefs.plist.
  14. If you locate the file, move it to the Desktop. If you do not locate the file, the program is using the default preferences. 
  15. If you locate the file and move it to the desktop, start Excel, and check whether the problem still occurs. If the problem still occurs, quit Microsoft Excel, and restore the file to its original location. Then, go to the next step. If the problem seems to be resolved, you can move the com.microsoft.Excel.prefs.plist file to the trash. 
  16. Close all Microsoft Office applications. 
  17. On the Go menu, click Home
  18. Open Library.
    Note The Library folder is hidden in MAC OS X Lion. To display this folder, hold down the OPTION key while you click the Go menu. 
  19. Open the Preferences folder. 
  20. Open the Microsoft Folder. 
  21. Open the Office 2008 or Office 2011 folder. 
  22. Look for a file that is named Excel Toolbars (12) or Microsoft Excel Toolbars
  23. If you locate the file, move it to the desktop. If you do not locate the file, the program is using the default preferences. 
  24. If you locate the file and move it to the desktop, start Microsoft Excel, and check whether the problem still occurs. If the problem still occurs, quit Microsoft Excel, and restore the file to its original location. Then, go to the next step. If the problem seems to be resolved, you can move the toolbars file to the trash. 


If the problem continues to occur, proceed to the next step.

Step 3: Peform clean boot 

For information how to clean start your Operating system (OS), see Microsoft Knowledge Base article:

2398596
(http://support.microsoft.com/kb/2398596/)
 Perform a clean startup (Safe mode) to determine whether background programs are interfering with Office for Mac

If the problem continues to occur, proceed to the next step.

Step 4: Remove and then reinstall Office 

For information how to remove and then reinstall Office, see Microsoft Knowledge Base article:

2500821
(http://support.microsoft.com/kb/2500821)
Manually remove Office 2008 for Mac completely from your computer

2398768
(http://support.microsoft.com/kb/2398768/)
How to completely remove Office for Mac 2011

If the issue continues to occur in Safe mode, proceed to Step 3. 

Step 5: Use the “Repair Disk Permissions” option 

You can use the Repair Disk Permissions option to troubleshoot permissions problems in Mac OS X 10.2 or later versions.  To use the Repair Disk Permissions option, follow these steps:

  1. On the Go menu, click Utilities
  2. Start the Disk Utility program. 
  3. Click the primary hard disk drive for your computer. 
  4. Click the First Aid tab. 
  5. Click Repair Disk Permissions.

Note The Disk Utility program only repairs software that is installed by Apple. This utility also repairs folders, such as the Applications folder. However, this utility does not repair software that is in your home folder. For more information about the Repair Disk Permissions option, see the following AppleCare article: http://docs.info.apple.com/article.html?artnum=10671
(http://docs.info.apple.com/article.html?artnum=106712)

Microsoft Excel 2004 for Mac

  1. Quit all Microsoft Office for Mac programs.
  2. On the Go menu, click Home.
  3. Open Library.
    Note The Library folder is hidden in MAC OS X Lion. To display this folder, hold down the OPTION key while you click the Go menu.
  4. Open the Preferences folder.
  5. Look for a file that is named com.microsoft.Excel.plist.
  6. If you locate the file, move it to the desktop. If you do not locate the file, the program is using the default preferences.
  7. If you locate the file and move it to the desktop, start Excel, and check whether the problem still occurs. If the problem still occurs, quit Excel, and restore the file to its original location. Then, go to the next step. If the problem seems to be resolved, you can move the com.microsoft.Excel.plist file to the trash.
  8. Quit all Microsoft Office for Mac programs.
  9. On the Go menu, click Home.
  10. Open Library.
    Note The Library folder is hidden in MAC OS X Lion. To display this folder, hold down the OPTION key while you click the Go menu.
  11. Open the Preferences folder.
  12. Open the Microsoft Folder.
  13. Look for a file that is named com.microsoft.Excel.prefs.plist.
  14. If you locate the file, move it to the desktop. If you do not locate the file, the program is using the default preferences.
  15. If you locate the file and move it to the desktop, start Excel, and check whether the problem still occurs. If the problem still occurs, quit Excel, and restore the file to its original location. Then, go to the next step. If the problem seems to be resolved, you can move the com.microsoft.Excel.prefs.plist file to the trash.
  16. Close all Microsoft Office applications.
  17. On the Go menu, click Home.
  18. Open Library.
    Note The Library folder is hidden in MAC OS X Lion. To display this folder, hold down the OPTION key while you click the Go menu.
  19. Open the Preferences folder.
  20. Open the Microsoft Folder.
  21. Look for a file that is named Excel Toolbars (11).
  22. If you locate the file, move it to the desktop. If you do not locate the file, the program is using the default preferences.
  23. If you locate the file and move it to the desktop, start Excel, and check whether the problem still occurs. If the problem still occurs, quit Excel, and restore the file to its original location. Then, go to the next step. If the problem seems to be resolved, you can move the Excel Toolbars (11) file to the trash.
  24. Start Excel, and check whether the problem still occurs.

If the problem still occurs, the problem is not related to these files.

If the problem no longer occurs, one of these files was causing the problem. If this is the case, you have to restore the files to their original location one at a time. Test the program after you restore each file. Continue to do this until the program occurs again. When the problem, the problem is related to the last file that you restored. Delete that file by dragging it to the trash.

More:
Excel for Mac error: "The application Microsoft Excel quit unexpectedly"

FAST Patch: esp.5.3.SP4.alerting.patch06.Win32/Linux

ID    : esp.5.3.SP4.alerting.patch06.Win32/Linux
Product   : ESP 5.3.SP4 on Win32/Linux
Category   : Recommended fix
Date released : 12-Dec-11

Overall Description
*******************
Build version: 5.3.4.54

Pre-requisites
**************
This patch requires ESP 5.3.SP4 on a corresponding platform

Known impacts of applying this fix
**********************************
o No known side-effects.

Install procedure
*****************
Note: Do always deploy patches on your staging/test environment first and
run your smoke- and stability-check there first as your system may have
custom non-mainstream adaptations that may not match with official new patches.
Note that FAST Enterprise Search Platform will be unavailable during the installation
process.  In a multi-node installation, these instructions must be executed on each node.
1.  Shut down FAST ESP. This can be done by executing the following
    command:
    nctrl stop
2.  Extract the files from the patch.
3.  Launch the ESP Update Installer
 (I.e. run setup.exe on Windows or setup_Linux.bin. Use the -console option to run in shell.)
 You will be given three choices:
 - Install patch
 - Rollback patch
 - Patch History
4. To install, select Install patch.
 You need to provide the path to your ESP installation and the complete path to the patch you wish to install.
5. The Update Installer will now try to install the patch.
 If successfull, a confirmation will be given. If not, then the cause of why the patch could not be installed will be displayed.
 In case of an error, your ESP state will be the same as it was before you started the Update Installer, regardless of when the
 Update Installer aborted the install.
6.  Restart FAST ESP. This can be done by executing the following
    command:
    nctrl start

This is a fix for issues
************************
 o 854670 : When there is a near operator within another near operator, that trigger matches irrespective of the word distance.

See the original article here:
FAST Patch: esp.5.3.SP4.alerting.patch06.Win32/Linux

Error message when you try to use Communicator 2007: "Communicator cannot synchronize with the corporate address book"

Although this article may apply to a many different implementations of Communicator, it is especially applicable in a dedicated deployment of the Microsoft Business Productivity Online Suite.

When you try to use Microsoft Office Communicator 2007, you may receive the following error message: 

“Communicator cannot synchronize with the corporate address book. Please contact your system administrator.”

Additionally, when you try to locate a contact by searching in Communicator, the contact cannot be located. However, you can see the same contact in the Outlook global address list (GAL).

Additionally, you may see incorrect contact data in Communicator. For example, after a display name is changed, Communicator may not be updated.

This issue may occur if the following conditions are true:

  • The ABS files are old and must be refreshed.
  • The computer is not connected to the OCS server in such a way that the ABS files can be downloaded.
 

The Communicator ABS files (Galcontacts.db and Galcontactsdelta.db) are downloaded by the client from a location that is provided to the client through in-band provisioning. The client receives both an internal and an external
location for download to accommodate remote-access users. You can view these URLs by opening the client’s logs and then searching for ABS. You will soon find the internal and external ABS URLs.

Originally posted here:
Error message when you try to use Communicator 2007: "Communicator cannot synchronize with the corporate address book"

Hitting "F5" key on Appointment opens new record in CRM 2011 Post UR5

After installing Dynamics CRM Update Rollup 5, You open a new “Appointment” record. After entering information and clicking “Save”, you press “F5″ on your keyboard to refresh the record. However, instead of refreshing, it opens a New record page. The original appointment you created is still saved, but the F5 button does not refresh it.

Pre-UR5, all records did this. Post U5, the “Appointment” entity is the only one still affected.

This was due to a design change in Update Rollup 5.
Workaround:
After saving the initial record, close out of the record and re-open it. If you press F5 again, the page will refresh.
Additionally, you will not see this issue if you create a new appointment that has a time conflict with another appointment for that user. You will be prompted that the user is already scheduled during that time. If you ignore and save, you will be able to press “F5″ and refresh after that prompt.
Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.

Visit site:
Hitting "F5" key on Appointment opens new record in CRM 2011 Post UR5

FRx 6.7 and 64-bit Support

This article describes the compatibility of Microsoft FRx 6.7 with a 64-bit version of Windows.
 

Microsoft FRx 6.7 is not supported on a 64-bit version of Windows.

Some parts of FRx 6.7 may work on 64-bit Windows because of the 32-bit compatibility layer (WoW64).  However, this environment is not tested or   supported.

FRx 6.7 service pack 11 or later versions is compatible with Windows 7 and Windows Server 2008, but only with the 32-bit versions.

Our recommendation is to install FRx 6.7 on a 32-bit version of Windows (client and server). 

FRx 6.7 can connect to the general ledger database that resides on a 64-bit SQL Server.

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.

Follow this link:
FRx 6.7 and 64-bit Support

FAST Patch: sharepointconnector.1.0.SP2.complete.patch03.Win32

ID    : sharepointconnector.1.0.SP2.complete.patch03.Win32
Product   : SharePointConnector 1.0.SP2 on Win32
Category   : Recommended fix
Date released : 22-Oct-10
 

Overall Description
*******************
This patch basically addresses the issues reported by various connector customers.
 
  o Robustness improvements – The connector will log various SharePoint content errors and exceptions, and continue to crawl with available content. 
  o Retrying of failed contents – The connector will save failed sites, list and documents (download failures) in the state database and will later retry this failed content. Instead of performing the retry inside the same connector run, it will instead be retried in later runs of the connector.
  o If a document has been intentionally dropped from the pipeline, the connector will no longer report this as a failed callback. 
  o Callbacks have been changed to report the document URL instead of document ID to make the log easier to understand and react upon. 
  o Various improvements to error log messages so the users can understand what exactly went wrong.

Configuring the new retry mechanism
========================
At the end of each connector run, the connector will retry failed content once.
If there are still failures, the connector will retry these failures in the next run.
By default the connector will retry this failed content up to 5 connector runs.
After the connector has reached this limit it will not retry failed content.
 
However if you still want the connector to retry failed content, you can increase the number of retry runs.
Please add a new configuration option NumberOfRetryCycles to the General section of your connector configuration file and set this to desired number of retry runs (e.g. 10).
 
A note about how to read the connector logs
============================
When the connector has completed a successful initial or incremental crawl, it will perform one sweep across all the previously failed documents (whether they failed in the current run or in a previous run) and retry them before it terminates. As a result of this, the summary at the end of the logs will be the summary of the retry sweep and not the initial or incremental crawl. To find the summary from the initial or incremental crawl, you need to look further up in the log.

   Build version: 1.0.44.0

Pre-requisites
**************
SharePoint Connector 1.0 SP2, with or without any patches

Why would you apply this fix
**************************** 
  o The connector fails a crawl and terminates prematurely. This version will catch more errors and log them and then move on. 
  o The connector spends a lot of time retrying download of content which is temporarily unavailable, or unavailable because of wrongly configured security. 
  o You drop documents intentionally in the ESP pipeline and the connector log is spammed with error messages about this.
  o In case of failures, the connector is not providing sufficient/user friendly log messages to understand the exact problem.
  o Some data is never made searchable due to the connector not being able to download the content and after having retried a certain number of times, the connector gives up and never retries to download that data.

Known impacts of applying this fix
**********************************
There is one known issue in this version of the connector, that also exists in all earlier versions of the connector, that has not been fixed:
 
When the connector fails to fetch all changes from SharePoint during the initial phase of an incremental run, it will not proceed and process any changes.
 
This is due to a known issue in SharePoint:
 
If some data in SharePoint has badly configured permissions, the call to the Web Service method GetChanges() will fail with “Unauthorized”.
 
The consequence of this is that the connector will fail to run a successful incremental crawl until the “bad” change ID has expired. Unfortunately, this also causes the saved change token (from the full crawl or from the last successful incremental crawl) will also have expired. Hence the only resolution will be to go back to a full craw.
 
NOTE: This issue occurs very seldom and should not occur when SharePoint is administered in a “normal” way.
 
This error can be recognized by the following error in the connector log:
 
2010-10-12 1:22:49 PM FATAL    : SharePointConnector : Error running connector SharePointConnector. Will terminate. Error: SharePoint connector failed to retrieve content though SharePoint Web Services
2010-10-12 1:22:49 PM DEBUG    : SharePointConnector :    at Microsoft.SharePoint.Search.Extended.Content.MOSSConnector.MOSSConnectorExceptionHelper.ThrowSiteDataException(Exception exception, SiteDataParameters param)
   at Microsoft.SharePoint.Search.Extended.Content.MOSSConnector.MOSSCrawler.GetChangesResponse(ObjectType objectType, String contentDBId, String& lastChangeId, String& currentChangeId, Int32 timeOut, Boolean& moreChanges)
   at Microsoft.SharePoint.Search.Extended.Content.MOSSConnector.MOSSCrawler.GetChanges(ObjectType objectType, String contentDBId, String& lastChangeId, String& currentChangeId, Int32 timeout, Boolean& moreChanges)
   at Microsoft.SharePoint.Search.Extended.Content.MOSSConnector.MOSSSubSiteCrawler.ProcessChanges(String& lastChangeToken, String& currentChangeToken, Boolean& hasMoreChanges, String objectId, ObjectType objType, Boolean isFirstIteration)
   at Microsoft.SharePoint.Search.Extended.Content.MOSSConnector.MOSSSubSiteCrawler.FindSitesAndListsFromGetChanges()
   at Microsoft.SharePoint.Search.Extended.Content.MOSSConnector.MOSSTaskSplitter.GetStartSitesAndLists(IFastConfig configuration, Boolean addIncludeUrltoTheTaskList, Boolean isSubTask)
   at Microsoft.SharePoint.Search.Extended.Content.MOSSConnector.MOSSTaskSplitter.Split(IFastConfig configuration, Boolean addIncludeUrltoTheTaskList, Boolean isSubTask)
   at Microsoft.SharePoint.Search.Extended.Content.MOSSConnector.MOSSTaskSplitter.Split(IFastConfig configuration)
   at com.fastsearch.esp.cctk.framework.ANPConnectorManager.Start()
   at Microsoft.SharePoint.Search.Extended.Content.MOSSConnector.ANPMOSSConnectorManager.Start()
   at com.fastsearch.esp.cctk.framework.ConnectorManager.RunCommandLineWithReturnValue(String[] argv)

 
The only workaround for this error is to manually fix the “bad” permissions in SharePoint. To be able to locate where in SharePoint the “bad” permissions exist, you will need help from FAST services.
 
NOTE that the permissions will need to be fixed within the time it takes for the SharePoint changelog to recycle. This is by default 15 days in SharePoint 2007 and 90 days in SharePoint 2010.

Install procedure
*****************
1) make a backup of your current installation by making a copy of the installation folder (typically C:Program Files (x86)FASTFAST SharePoint Connector).
 
2) Unzip the archive called sharepointconnector.1.0.SP2.complete.patch03.Win32.zip on top of the installation folder (typically C:Program Files (x86)FASTFAST SharePoint Connector). This will replace all your binaries in the bin folder and a few other files. When prompted for whether you want to overwrite files, select “Yes”. Your configuration files will not be replaced and can be reused with the new version.
 
This release does not require a full re-crawl to be operational but it’s highly recommended. Errors in the previous version may have caused document loss and these missing documents will only be included again by doing a full crawl.
 
To trigger a full crawl with this release using your existing configuration, you need to either delete and re-create your state database or, if you’re not worried about space in your state database, set the configuration parameter Database/TableNamePrefix to a new unique value. This will cause a whole new set of tables to be created.
 
If you want to not perform a full crawl but instead go directly to incremental, you will need to migrate your state database. This version makes use of a few new tables and it also expects some of the URLs in the state database to contain trailing slashes.
 
To migrate your state database, Follow the instructions in the file Migration-ReadMe.txt which resides in the etc directory.

This is a fix for issues
************************ 
 o 850934 : Fail to crawl resources in Incremental / Restart mode due to null exception
 o 850976 : SharepointConnector 1.0 does not retry content aggregation if it fails while downloading content.
 o 850989 : Errors in callbacks is impossible to relate to the relevant content
 o 850990 : SharePoint connector should not sleep / retry on “401 Unauthorized”
 o 851005 : FAST SharePoint .NET connector failures in incremental crawls
 o 851105 : callbackhandler should not treat intentionally dropped documents as failed
 o 851204 : Documents are getting missed in the Restart mode
 o 851237 : List items with attachments failed to index with a “object reference not set to an instance of an obeject”

Issue Reproduction
******************
Some data is never made searchable due to the connector not being able to download the content 
 
EXPECTED RESULTS
The connector should keep the information on failed contents and try to index them later 
 
ACTUAL RESULTS
The connector retries to get the content then and there, but never again later. 
 
HOW TO REPRODUCE 
Explicitly deny access to the crawler user to some content and run the connector to crawl that content. You should see ERRORs in the connector log that it fails to download the content and that it retries (for a certain amount of time). After that time has elapsed, the connector moves on and never tries to get that content again 
 
Then connector log is spammed with ERROR messages about documents that are intentionally dropped in the ESP pipeline 
 
EXPECTED RESULTS 
The connector should not consider the intentionally dropped documents as failed documents. It should treat them as successfully submitted documents.
 
ACTUAL RESULTS 
The connector reports the intentionally dropped documents as failed documents. 
 
HOW TO REPRODUCE
Add a document processor stage to the ESP pipeline that returns ProcessorStatus.Completed from the Process() method. This results in the document being dropped from the pipeline (it will not be indexed and searchable). Observe that the conenctor log contains ERROR entries about this. 
 
When there are errors in the ESP pipeline for a document, the ERROR entry in the connector log contains a GUID based document ID instead of the URL of the document 
 
EXPECTED RESULTS
The callback handler should provide a document URL making the log easier to understand and to act upon. E.g. by going to the relevant content and fix it or to exclude it from crawling. 
 
ACTUAL RESULTS
The callback handler provides document IDs which are practically impossible to relate to the failed document in SharePoint.. 
 
HOW TO REPRODUCE
Add a file to a document library that is of an unsupported file type (e.g. .exe) and remove this file type from the configuration parameter Filters/ExcludeExtensions so that the connector will not drop it. You should see an ERROR entry in the connector log that says “Unsupported mime-type format: application/octet-stream”. Observe that the ID of the failed document is a GUID based identifier. It is hard to correlate this to the relevant document ni SharePoint.

See the original article here:
FAST Patch: sharepointconnector.1.0.SP2.complete.patch03.Win32

SDP 248CF6C75-2D60-4E1A-BEB0-307C0427C7C8 Microsoft Dynamics CRM Baseline Information Collector for Windows Server 2003

The Microsoft Dynamics CRM Baseline Information Collector for Windows Server 2003 collects information that is used to troubleshoot Microsoft Dynamics CRM common issues.

This article describes the information that may be collected from a computer when the Microsoft Dynamics CRM Baseline Information Collector for Windows Server 2003 is run.


Information that is collected

Operating system information

Collapse this tableExpand this table

Description

File Name

Operating system version information

date run_crmserverinformation.txt

Microsoft Dynamics CRM registry key values

Collapse this tableExpand this table

Description

File Name

List of registry keys and values that are stored under the following registry hive:

HKEY_LocalMachineSoftwareMicrosoftMSCRM

date run_crmserverinformation.txt

Installed Microsoft Dynamics CRM hotfixes

Collapse this tableExpand this table

Description

File Name

List of all applied Microsoft Dynamics CRM hotfixes

date run_crmserverinformation.txt

Microsoft Dynamics CRM file list

Collapse this tableExpand this table

Description

File Name

Complete list of files from the CRM_Server_InstallDir registry key value, including dates and file versions

date run_crmserverinformation.txt

Microsoft CRM files that are installed in the assembly cache

Collapse this tableExpand this table

Description

File Name

List of all Microsoft Dynamics CRM files that are installed in the global assembly cache on the CRM Server

date run_crmserverinformation.txt

Windows Services list

Collapse this tableExpand this table

Description

File Name

Detailed list of all active Windows Services on the Microsoft Dynamics CRM Server

date run_crmserverinformation.txt

Running processes

Collapse this tableExpand this table

Description

File Name

Detailed list of all running processes on the Microsoft Dynamics CRM Server

date run_crmserverinformation.txt

Application event logs

Collapse this tableExpand this table

Description

File Name

Event log – Application – All Microsoft Dynamics CRM events in the last seven days

Event log – Application – All ASP.NET events in the last seven days

date run_crmserverinformation.txt

IIS application pool settings

Collapse this tableExpand this table

Description

File Name

Detailed list of all application pools that are present on the server that is running IIS and that hosts Microsoft Dynamics CRM

date run_crmserverinformation.txt

Microsoft CRM website settings

Collapse this tableExpand this table

Description

File Name

Information about the location of the website under the following LM/W3SVC registry key:

HKEY_LocalMachineSOFTWAREMicrosoftMSCRM

date run_crmserverinformation.txt

Boot.ini file

Collapse this tableExpand this table

Description

File Name

Contents of the server’s boot.ini file

date run_crmserverinformation.txt

TCP/IP configuration

Collapse this tableExpand this table

Description

File Name

List of TCP/IP registry keys and their values.

date run_crmserverinformation.txt

Microsoft SQL Server general information

Collapse this tableExpand this table

Description

File Name

List of the SQL Server configuration settings for the Microsoft Dynamics CRM deployment

date run_crmserverinformation.txt

Microsoft Dynamics CRM 4.0 configuration database settings

Collapse this tableExpand this table

Description

File Name

Provides a list of the Organization, Server, ConfigSettings, and DeploymentProperties tables for servers that have a deployment of Microsoft Dynamics CRM 4.0

date run_crmserverinformation.txt

Organizational statistics

Collapse this tableExpand this table

Description

File Name

Summary report that details the ten largest tables, the number of custom entities, and the number of custom attributes per entity for each organization in the deployment

date run_crmserverinformation.txt

Business logic extensions

Collapse this tableExpand this table

Description

File Name

Summary report that details any deployed plugins, workflow activities, or callout assemblies for each organization in the deployment

date run_crmserverinformation.txt

Taken from:
SDP 248CF6C75-2D60-4E1A-BEB0-307C0427C7C8 Microsoft Dynamics CRM Baseline Information Collector for Windows Server 2003

SDP 35a6af7ba-e0c0-4a92-853c-e5f3c6bcdba3 Microsoft Dynamics CRM Baseline Collector for Windows Server 2008 R2

The Microsoft Dynamics CRM Baseline Information Collector for Windows Server 2008 R2 collects information that is used to troubleshoot Microsoft Dynamics CRM common issues.
This article describes the information that may be collected from a computer when the Microsoft CRM Baseline Collector is run. 

Information that is collected

Operating system information

Collapse this tableExpand this table

Description File Name
Operating system version information date run_crmserverinformation.txt

Microsoft Dynamics CRM registry key values

Collapse this tableExpand this table

Description File Name
List of registry keys and values that are stored under the following registry hive:

HKEY_LocalMachineSoftwareMicrosoftMSCRM

date run_crmserverinformation.txt

Installed Microsoft Dynamics CRM hotfixes

Collapse this tableExpand this table

Description File Name
Lit of all applied Microsoft Dynamics CRM hotfixes date run_crmserverinformation.txt

Microsoft Dynamics CRM file listing

Collapse this tableExpand this table

Description File Name
Complete list of files from the CRM_Server_InstallDir registry key value, including dates and file versions date run_crmserverinformation.txt

Microsoft CRM files that are installed in the assembly cache

Collapse this tableExpand this table

Description File Name
List of all Microsoft Dynamics CRM files that are installed in the global assembly cache on the CRM Server date run_crmserverinformation.txt

Windows Services list

Collapse this tableExpand this table

Description File Name
Detailed list of all active Windows Services on the Microsoft Dynamics CRM Server  date run_crmserverinformation.txt

Running processes

Collapse this tableExpand this table

Description File Name
Detailed list of all running processes on the Microsoft Dynamics CRM server date run_crmserverinformation.txt

Application event logs

Collapse this tableExpand this table

Description File Name
Event log – Application – All Microsoft Dynamics CRM events in the last seven days
Event log – Application – All ASP.NET events in the last seven days
date run_crmserverinformation.txt

IIS application pool settings

Collapse this tableExpand this table

Description File Name
Detailed list of all application pools that are present on the server that is running IIS and that hosts Microsoft Dynamics CRM date run_crmserverinformation.txt

Microsoft CRM website settings

Collapse this tableExpand this table

Description File Name
Information about the location of the website under the following LM/W3SVC registry key:

HKEY_LocalMachineSOFTWAREMicrosoftMSCRM

date run_crmserverinformation.txt

Boot.ini file

Collapse this tableExpand this table

Description File Name
Contents of the server’s boot.ini file date run_crmserverinformation.txt

TCP/IP configuration

Collapse this tableExpand this table

Description File Name
List of TCP/IP registry keys and their values date run_crmserverinformation.txt

Microsoft SQL Server general information

Collapse this tableExpand this table

Description File Name
List of the SQL Server configuration settings for the CRM Deployment date run_crmserverinformation.txt

Microsoft Dynamics CRM 4.0 configuration database settings

Collapse this tableExpand this table

Description File Name
ist of the Organization, Server, ConfigSettings, and DeploymentProperties tablesfor servers that have a deployment of Microsoft Dynamics CRM 4.0 date run_crmserverinformation.txt

Organizational statistics

Collapse this tableExpand this table

Description File Name
Summary report that details the ten largest tables, the number of custom entities, and the number of custom attributes per entity for each organization in the deployment date run_crmserverinformation.txt

Business logic extensions

Collapse this tableExpand this table

Description File Name
Summary report that details any deployed plugins, workflow activities, or callout assemblies for each organization in the deployment date run_crmserverinformation.txt

Read this article:
SDP 35a6af7ba-e0c0-4a92-853c-e5f3c6bcdba3 Microsoft Dynamics CRM Baseline Collector for Windows Server 2008 R2

FAST Patch: sharepointconnector.1.0.SP2.complete.patch04.Win32

ID    : sharepointconnector.1.0.SP2.complete.patch04.Win32
Product   : SharePointConnector 1.0.SP2 on Win32
Category   : Recommended fix
Date released : 21-Feb-11 

Overall Description
*******************
This release addresses no of bugs reported by various customers on connector SP2 and above. 
 
Please note the following if current patch level is not patch3. 
 
Configuring the new retry mechanism
At the end of each connector run, the connector will retry failed content once. If there are still failures, the connector will retry these failures in the next run. By default the connector will retry this failed content up to 5 connector runs. After the connector has reached this limit it will not retry failed content. 
 
However if you still want the connector to retry failed content, you can increase the number of retry runs. Please add a new configuration option NumberOfRetryCycles to the General section of your connector configuration file and set this to desired number of retry runs (e.g. 10). 
 
A note about how to read the connector logs
When the connector has completed a successful initial or incremental crawl, it will perform one sweep across all the previously failed documents (whether they failed in the current run or in a previous run) and retry them before it terminates. As a result of this, the summary at the end of the logs will be the summary of the retry sweep and not the initial or incremental crawl. To find the summary from the initial or incremental crawl, you need to look further up in the log. 
 
   Build version: connectors.15

Pre-requisites
**************
SharePoint connector SP2 or above

Known impacts of applying this fix
**********************************
The following known issue has been observed in patch3 and patch4. 
 
In incremental mode if a new sub site was added to a previously indexed site, the connector won’t maintain the parent child relationship in the state database for the site and sub site. This will cause the connector to not propagate changes in the parent site to the sub site. 
 
For example, if the newly added sub site is set to inherit security from the parent site, and there is a permission change that tightens the security of the parent site, the sub-site will NOT be re-crawled. Hence, it will remain visible (in search) for people who shouldn’t have access to it.
 
However the connector will index content of sub site as expected and will also handle changes to the sub site itself.

Install procedure
***************** 
  o make a backup of your current installation by making a copy of the installation folder (typically C:Program Files (x86)FASTFAST SharePoint Connector).
  o Unzip the archive called sharepointconnector.1.0.SP2.complete.patch04.Win32.zip on top of the installation folder (typically C:Program Files (x86)FASTFAST SharePoint Connector). This will replace all your binaries in the bin folder and a few other files. When prompted for whether you want to overwrite files, select “Yes”. Your configuration files will not be replaced and can be reused with the new version.  
 
This release does not require a full re-crawl to be operational but it’s highly recommended. Errors in the previous version may have caused document loss and these missing documents will only be included again by doing a full crawl. 
 
To trigger a full crawl with this release using your existing configuration, you need to either delete and re-create your state database or, if you’re not worried about space in your state database, set the configuration parameter Database/TableNamePrefix to a new unique value. This will cause a whole new set of tables to be created. 
 
Following is only applicable if the current connector installation is not on patch3. 
 
If you want to not perform a full crawl but instead go directly to incremental, you will need to migrate your state database. This version makes use of a few new tables and it also expects some of the URLs in the state database to contain trailing slashes. 
 
To migrate your state database, follow the below instructions.
 
  o Connect to the current existing state tracker database by using SQL Server Management Studio.
  o Open the script “sql_db_migration.sql”
  o If the connector is configured to use a table name prefix (Database/TableNamePrefix)
   replace the literal in the migration script with the table name prefix else replace this literal with empty string. 
  o Execute the script. The status line in SQL Server Manager should read “Query executed successfully”.
  o Open the script “update_changetoken_urls.sql”
  o If the connector is configured to use a table name prefix (Database/TableNamePrefix)
   replace the literal in the script with the table name prefix else replace this literal with empty string. 
  o Replace the with Filters/IncludeWebUrls value and execute the script.
   Please note that if the connector is configured to use multiple IncludeWebUrls this script needs to be executed for each URL separately.
An alternative to steps 5, 6 and 7 is to right-click the table “ChangeTokens” and select “Edit top 200 Rows” and then for each row add a trailing slash to the URL in the “Url” column. Make sure you don’t modify the URL except for adding the trailing slash.
 
 
NOTE: Migration scripts have not been provided for Oracle.

This is a fix for issues
************************ 
 o 851313 : Connector doesn’t gets out of retry mode when setting the Sleep Interval in configuration file.
 o 851324 : When IndexItemView Set to false, List Item is not indexed when attachment exceeds the limit.
 o 851394 : Sharepoint Web Policies Not Handled by the SharePoint Connector (1.0sp2patch02)
 o 851494 : Connector fails to process site content in incremental mode in SP2010
 o 851619 : Connector terminates in incremental mode
 o 851685 : The connector doesn’t honor items filters in the incremental mode
 o 851716 : MS-SP-Connector – ProcessSiteCollectionUpdates – Object reference not set to an instance of an object
 o 851729 : SharePoint Connector 1.0 SP2Pach03KAO: Incremental crawl doesn’t re-feed document in renamed folder.
 o 851769 : SharePoint Connector 1.0 SP2 Patch03: It doesn’t work on JPN environment.
 o 851827 : SPConnector1.0SP2Patch03KAO:IncludeListUrls does not work fine in incremental crawl

Issue Reproduction
******************
The connector doesn’t handle SharePoint web polices. 
 
Define web policies for the web application the connector is configured to crawl and run the connector. 
 
EXPECTED RESULTS 
The connector should detect these web policies in these policies should be reflected in the indexed content. 
 
ACTUAL RESULT 
The connector doesn’t honor web policies. Note that The connector won’t be able to handle updates to web policies. 
 
The connector is unable to process content updates with SharePoint 2010. 
 
After the initial run make some changes to SharePoint content and run the connector. 
 
EXPECTED RESULTS
The connector should detect these changes and update the index accordingly. 
 
ACTUAL RESULT
The connector is not able to process these changes hence the index doesn’t get updated with these changes. 
 
The connector doesn’t honor items filters in the incremental mode.
 
  o Create a list with two items itemA and itemB
  o Define exclude (or include) filters in such a way that the connector will ignore itemA when crawling SP. You can use max file size, extensions etc… filters for this.
  o Run the connector and make sure itemA has not been indexed.
  o Now make some updates to the itemA and itemB
EXPECTED RESULTS
The connector should update the itemB accordingly.
 
ACTUAL RESULTS
The connector not updates the itemB and fail with a null reference exception.
 
The connector is not able to handle folder renames.
 
After the initial crawl rename a folder and run the connector.
 
EXPECTED RESULTS
The connector should detect the rename operation and update the indexed folder and it’s items correctly. 
 
ACTUAL RESULTS
The connector doesn’t handle the folder rename operation.

Read More:
FAST Patch: sharepointconnector.1.0.SP2.complete.patch04.Win32

Page 434 of 727« First...102030...432433434435436...440450460...Last »

Recent Comments

    Archives

    Categories