Page 323 of 982« First...102030...321322323324325...330340350...Last »

Outlook 2010 keyboard shortcuts fail to respond after switching to the next or previous message when the Microsoft Dynamics CRM 2011 add-in is configured

After using the Outlook 2010 keyboard shortcuts to navigate to the next or previous e-mail message, additional keyboard shortcuts will fail to respond. This issue only occurs when the Microsoft Dynamics CRM 2011 add-in has been enabled and configured.
Microsoft has confirmed that this is a known issue.
This issue will be addressed in the next major release of Microsoft Dynamics CRM.
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.

Article ID: 2909813 – Last Review: November 11, 2013 – Revision: 1.0


Applies to
  • Microsoft Dynamics CRM 2011
kbmbsmigrate kbsurveynew KB2909813

Taken from:
Outlook 2010 keyboard shortcuts fail to respond after switching to the next or previous message when the Microsoft Dynamics CRM 2011 add-in is configured

FIX: "Query stopped because an error occurred while it was running" when you run a non-live query in Forefront Threat Management Gateway 2010 SP2

You have Rollup 1

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

, Rollup 2

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

, or Rollup 3

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

 installed in Microsoft Forefront Threat Management Gateway 2010 Service Pack 2 (SP2). However, when you run any non-live query (a historical query such as Last Hour, Last Week, and so on) against a logging database, the query doesn’t run successfully. Additionally, you receive the following error message:

The query stopped because an error occurred while it was running.

This problem occurs when the following conditions are true:
  • Logging uses either SQL Server Express or remote SQL Server.
  • Form-based authentication is used in Web Publishing rules.
  • There are too many concurrent incoming web requests hitting these rules.

A code change was introduced in Forefront Threat Management Gateway 2010 SP2 that causes Thread Local Storage (TLS) index exhaustion. This prevents the required loading of the libraries that are used for querying SQL Server logging databases.

To resolve this problem, install Rollup 4

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

for Forefront Threat Management Gateway (TMG) 2010 Service Pack 2.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
Learn about the terminology

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

Microsoft uses to describe software updates.

Article ID: 2863383 – Last Review: November 8, 2013 – Revision: 2.0


Applies to
  • Microsoft Forefront Threat Management Gateway 2010 Service Pack 2, when used with:
    • Microsoft Forefront Threat Management Gateway 2010 Enterprise
    • Microsoft Forefront Threat Management Gateway 2010 Standard
kbqfe kbfix kbexpertiseinter kbbug kbsurveynew KB2863383

Read more here:
FIX: "Query stopped because an error occurred while it was running" when you run a non-live query in Forefront Threat Management Gateway 2010 SP2

FIX: Firewall service (Wspsrv.exe) crashes when a web publishing request is handled in Forefront Threat Management Gateway 2010

The Firewall service (Wspsrv.exe) may crash intermittently while a web publishing request is handled in Microsoft Forefront Threat Management Gateway 2010.
This problem may occur when the Web Publishing listener has the Require SSL Client Certificate option enabled.
To resolve this problem, install Rollup 4

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

for Forefront Threat Management Gateway (TMG) 2010 Service Pack 2.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
Learn about the terminology

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

Microsoft uses to describe software updates.

Article ID: 2899716 – Last Review: November 8, 2013 – Revision: 1.0


Applies to
  • Microsoft Forefront Threat Management Gateway 2010 Enterprise
  • Microsoft Forefront Threat Management Gateway 2010 Standard
kbqfe kbfix kbexpertiseinter kbbug kbsurveynew KB2899716

See the original post:
FIX: Firewall service (Wspsrv.exe) crashes when a web publishing request is handled in Forefront Threat Management Gateway 2010

FIX: "URL" and "Destination Host Name" values are unreadable in the web proxy log of Forefront Threat Management Gateway 2010 are unreadable

The URL and Destination Host Name columns in the web proxy log of Microsoft Forefront Threat Management Gateway 2010 may be displayed as unreadable values. This problem occurs when users access websites by using an internationalized domain name (IDN) and the log entries are retrieved from disk.

Note IDNs are domain names that may contain Unicode characters and are accessed by using Punycode transcription. Threat Management Gateway converts the Punycode name into the Unicode representation when the log entries are viewed in the logging view in the Forefront TMG Management snap-in of the Microsoft Management Console (MMC). However, when the log entries are retrieved from disk, any non-ASCII characters in the Unicode string are replaced with a question mark (?), as we explain in the “Cause” section.

This problem occurs because the logging columns in Threat Management Gateway are saved in ASCII format, and when the log records are written to disk, the values in the URL and Destination Host Name columns are converted from Unicode to ASCII. This causes any non-ASCII value in the value to be replaced with a question mark (?).
To resolve this problem, install Rollup 4

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

 for Forefront Threat Management Gateway 2010 Service Pack 2, and then run the script in the “More Information” section.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
Copy and paste the following script in Notepad.exe, and then save the file as ”SetPersistLogAsPunycode.vbs.”
'Define the constants needed.
Const strVpsGUID = "143F5698-103B-12D4-FF34-1F34767DEABC"
Const strVpsPropertyName = "PersistLogAsPunycode"
Const Error_FileNotFound = &H80070002
Set objArgs = wscript.Arguments
fInvalidParameterValue = False
if objArgs.Count > 0 then
    if objArgs(0) = "0" then
        fPersistLogAsPunycode = False
    elseif objArgs(0) = "1" then
        fPersistLogAsPunycode = True
    else
        fInvalidParameterValue = True
    end if
end if
if objArgs.Count <> 1 or fInvalidParameterValue then
    wscript.echo "Usage: SetPersistLogAsPunycode.vbs <0|1>"
    wscript.echo
    wscript.echo "Control how log fields that may contain punycode-encoded parts are"
    wscript.echo "stored in the persistent log."
    wscript.echo
    wscript.echo "    0 - Persist the applicable log fields as ASCII (the default behavior)"
    wscript.echo "    1 - Persist the applicable log fields as Punycode"
    wscript.Quit 2
end if
set objLogging = CreateObject("FPC.Root").GetContainingArray().Logging
Set objVPSet = OpenVPSet(objLogging, strVpsGUID)
objVPSet.Value(strVpsPropertyName) = fPersistLogAsPunycode
objLogging.Save
function OpenVPSet(objParent, strVpsGUID)
    Set objVPSets = objParent.VendorParametersSets
    On Error Resume Next
    Set OpenVPSet = objVPSets.Item(strVpsGUID)
    ' Save the Err properties in case it needs to be re-raised
    errNumber      = Err.Number
    errSource      = Err.Source
    errDescription = Err.Description
    errHelpFile    = Err.HelpFile
    errHelpContext = Err.HelpContext

    On Error GoTo 0

    if errNumber = Error_FileNotFound Then
        Set OpenVPSet = objVPSets.Add(strVpsGUID)
    Elseif errNumber < 0 Then
        ' An error other than "file not found" occured -- re-raise the error,
        ' this time not under "On Error Resume Next"
        Err.Raise errNumber, errSource, errDescription, errHelpFile, errHelpContext
    End If
end function

To enable Threat Management Gateway to persist the log entries as Punycode values, run the following command:

cscript.exe SetPersistLogAsPunycode.vbs 1

To revert Threat Management Gateway to its default behavior of logging fields as ASCII characters, run the following command:

cscript.exe SetPersistLogAsPunycode.vbs 0

See the terminology

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

Microsoft uses to describe software updates.

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.

Article ID: 2890563 - Last Review: November 8, 2013 - Revision: 1.0


Applies to
  • Microsoft Forefront Threat Management Gateway 2010 Enterprise
  • Microsoft Forefront Threat Management Gateway 2010 Standard
kbqfe kbfix kbexpertiseinter kbbug kbsurveynew KB2890563

Read More:
FIX: "URL" and "Destination Host Name" values are unreadable in the web proxy log of Forefront Threat Management Gateway 2010 are unreadable

FIX: Accounts are locked out beyond the AccountLockoutResetTime period in Forefront Threat Management Gateway 2010 SP2

After you configure the account lockout feature

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

 in Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 2, the accounts may remain locked beyond the configured AccountLockoutResetTime period.

This problem occurs if there is an ongoing authentication attempt while the account is locked out. In this situation, the account lockout period may be extended incorrectly by the AccountLockoutResetTime feature. This problem may occur whether the correct credentials are used or not.
To resolve this problem, install Rollup 4

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

 for Forefront Threat Management Gateway (TMG) 2010 Service Pack 2.

To temporarily workaround this problem, restart the TMG Firewall Service. This resets the account lockout database.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
Learn about the terminology

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

Microsoft uses to describe software updates.

Article ID: 2889345 – Last Review: November 8, 2013 – Revision: 3.0


Applies to
  • Microsoft Forefront Threat Management Gateway 2010 Service Pack 2, when used with:
    • Microsoft Forefront Threat Management Gateway 2010 Enterprise
    • Microsoft Forefront Threat Management Gateway 2010 Standard
kbqfe kbfix kbexpertiseinter kbbug kbsurveynew KB2889345

More:
FIX: Accounts are locked out beyond the AccountLockoutResetTime period in Forefront Threat Management Gateway 2010 SP2

FIX: Firewall Service leaks memory if Malware Inspection is enabled in Forefront Threat Management Gateway 2010

The Microsoft Forefront Threat Management Gateway 2010 Firewall Service process may leak memory over time if the Malware Inspection feature is enabled.

Note You may be able to verify this problem by monitoring the Performance Monitor counters for the WSPSRV.EXE process. In this way, you can determine whether the Private Bytes, Virtual Bytes and Working Set processes continually increase without ever decreasing.

To resolve this problem, install Rollup 4

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

for Forefront Threat Management Gateway (TMG) 2010 Service Pack 2.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
Learn about the terminology

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

Microsoft uses to describe software updates.

Article ID: 2891026 – Last Review: November 8, 2013 – Revision: 1.0


Applies to
  • Microsoft Forefront Threat Management Gateway 2010 Enterprise
  • Microsoft Forefront Threat Management Gateway 2010 Standard
kbqfe kbfix kbexpertiseinter kbbug kbsurveynew KB2891026

Read the original:
FIX: Firewall Service leaks memory if Malware Inspection is enabled in Forefront Threat Management Gateway 2010

FIX: A password change is unsuccessful if a user’s DN attribute contains a forward slash and an Active Directory LDAP-defined special character in Forefront Threat Management Gateway 2010

Consider the following scenario:
  • An administrator has forms-based authentication (FBA) set up in Microsoft Forefront Threat Management Gateway (TMG) 2010.
  • The distinguished name (DN) attribute for a user contains a forward slash (/) and an Active Directory Lightweight Directory Access Protocol (LDAP)-defined special character.
  • The user tries to change his or her password.

In this scenario, the password change is unsuccessful, and the user receives the following generic error message:

Either the user name or old password is not valid, or the new password does not meet the minimum complexity requirements. Please try again.

Additionally, tracing in TMG 2010 may indicate that ADsOpenObject failed with 0×80005000 (E_ADS_BAD_PATHNAME) or 0×80072032 (ERROR_DS_INVALID_DN_SYNTAX) because the special character in the LDAP request escaped.

This problem occurs for any Active Directory user account for which the DN attribute contains an Active Directory special character and a forward slash character. 
To resolve this problem, install Rollup 4

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

 for Forefront Threat Management Gateway 2010 Service Pack 2.

After you apply this update, you can configure Threat Management Gateway to use the objectGUID attribute instead of the DistinguishedName attribute in Active Directory LDAP path to resolve the issue that is described in this article. To enable this functionality, follow these steps:

  1. Copy and paste the following script into Notepad, and then save it by using the “EnableKB2888619.vbs” file name:
    set curArray = CreateObject("FPC.Root").GetContainingArray()
    Const SE_VPS_GUID = "143F5698-103B-12D4-FF34-1F34767DEABC"
    Const SE_VPS_NAME = "UseObjectGUIDInLDAPADsPath"
    Const SE_VPS_VALUE = 1
    
    Sub SetValue()
    
    ' Create the root obect.
    Dim root ' The FPCLib.FPC root object
    Set root = CreateObject("FPC.Root")
    
    'Declare the other objects needed.
    Dim array ' An FPCArray object
    Dim VendorSets ' An FPCVendorParametersSets collection
    Dim VendorSet ' An FPCVendorParametersSet object
    
    ' Obtain references to the array object
    ' and the network rules collection.
    Set array = curArray
    Set VendorSets = array.VendorParametersSets
    
    On Error Resume Next
    Set VendorSet = VendorSets.Item( SE_VPS_GUID )
    
    If Err.Number <> 0 Then
    Err.Clear
    
    ' Add the item
    Set VendorSet = VendorSets.Add( SE_VPS_GUID )
    CheckError
    WScript.Echo "New VendorSet added... " & VendorSet.Name
    
    Else
    WScript.Echo "Existing VendorSet found... value- " & VendorSet.Value(SE_VPS_NAME)
    End If
    
    If VendorSet.Value(SE_VPS_NAME) <> SE_VPS_VALUE Then
    
    Err.Clear
    VendorSet.Value(SE_VPS_NAME) = SE_VPS_VALUE
    
    If Err.Number <> 0 Then
    CheckError
    Else
    VendorSets.Save false, true
    CheckError
    
    If Err.Number = 0 Then
    WScript.Echo "Done with " & SE_VPS_NAME & ", saved!"
    End If
    End If
    Else
    WScript.Echo "Done with " & SE_VPS_NAME & ", no change!"
    End If
    
    End Sub
    
    Sub CheckError()
    
    If Err.Number <> 0 Then
    WScript.Echo "An error occurred: 0x" & Hex(Err.Number) & " " & Err.Description
    Err.Clear
    End If
    
    End Sub
    
    SetValue

  2. Run the script on one of the Threat Management Gateway array members. The script change will take effect when the Threat Management Gateway configuration synchronizes. No Firewall service restart is necessary for the change to take effect.
  3. To revert the change and return to the original behavior, locate the following line in the script:

    Const SE_VPS_VALUE = 1

  4. Change that line as follows:

    Const SE_VPS_VALUE = 0

  5. Save the script, and then run the script on one of the array members.

To work around this problem, remove the forward slash or the Active Directory special character from the DN attribute of the user.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
Escaped special characters in Active Directory attributes are as follows:
  • Comma (,)
  • Backslash ()
  • Number sign (#)
  • Plus sign (+)
  • Less than sign (<)
  • Greater than sign ( )
  • Semicolon (;)
  • Quotation mark (“)
  • Equal sign (=)
  • Leading or trailing spaces

Example of user account attributes:

sAMAccountName: JeffSmith
displayName: Smith, Jeff / TMG
distinguishedName: CN=Smith, Jeff / TMG,OU=Support,DC=Fabrikam,DC=com

Notes

  • The backslash escape character () is automatically added to the DN.
  • The distinguishedName attribute for this user account contains both the Active Directory special character comma (,) and the forward slash (/).

For more information, see the following:
See the terminology

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

Microsoft uses to describe software updates.

Article ID: 2888619 – Last Review: November 8, 2013 – Revision: 1.0


Applies to
  • Microsoft Forefront Threat Management Gateway 2010 Enterprise
  • Microsoft Forefront Threat Management Gateway 2010 Standard
kbqfe kbfix kbexpertiseinter kbbug kbsurveynew KB2888619

Continue reading here:
FIX: A password change is unsuccessful if a user’s DN attribute contains a forward slash and an Active Directory LDAP-defined special character in Forefront Threat Management Gateway 2010

FIX: Threat Management Gateway 2010 incorrectly sends "Keep-Alive" headers when it replies to Windows Media Player WPAD file requests

When Windows Media Player makes a Web Proxy Automatic Discovery (WPAD) request for the WPAD.dat file, it first appends a query string to the request, such as the following:
This enables a server to send differentiated auto-discovery content to a Media client.

Microsoft Forefront Threat Management Gateway 2010 responds to such requests with a “400 Bad Request” response. Media Player then requests the WPAD.dat file again but without the query string.

When the “400 Bad Request” response is sent, Threat Management Gateway 2010 incorrectly sends Connection: Keep Alive and Proxy-Connection: Keep-Alive headers before it sends a TCP FIN packet to close the TCP connection.

If Media Player then tries to reuse the initial TCP connection for the second request of WPAD.dat because of the presence of the “Keep-Alive” headers, this can cause performance issues because Threat Management Gateway 2010 considers the connection to be closed.

To resolve this problem, install Rollup 4

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

 for Forefront Threat Management Gateway 2010 Service Pack 2.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
See the terminology

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

Microsoft uses to describe software updates.

Article ID: 2899720 – Last Review: November 8, 2013 – Revision: 1.0


Applies to
  • Microsoft Forefront Threat Management Gateway 2010 Enterprise
  • Microsoft Forefront Threat Management Gateway 2010 Standard
kbqfe kbfix kbexpertiseinter kbbug kbsurveynew KB2899720

See more here:
FIX: Threat Management Gateway 2010 incorrectly sends "Keep-Alive" headers when it replies to Windows Media Player WPAD file requests

FIX: Access to certain SSL websites may be unavailable when HTTPS Inspection is enabled in Forefront Threat Management Gateway 2010

When HTTPS Inspection is enabled in Microsoft Forefront Threat Management Gateway 2010, access to certain secure sockets layer (SSL) websites may be unavailable. Additionally, you receive the following error message in Internet Explorer:

Internet Explorer cannot display the webpage

When you view the Threat Management Gateway web proxy logs, a result code of either 0×80090332 or -2146893022 is logged for the request.

If you run a Network Monitor trace of the traffic, you find that Threat Management Gateway returns the following error to the client:

HTTP/1.1 502 Proxy Error (The target principal name is incorrect.)

This problem occurs because HTTPS Inspection expects an SSL certificate to have a Common Name attribute specified in the Subject field. This is checked by HTTPS Inspection as part of certificate validation.

Some certification authorities have started to issue SSL certificates that have the subject name specified only in the Subject Alternate Name attribute. This is a valid certificate format. However, HTTPS Inspection in Threat Management Gateway 2010 does not handle this kind of certificate, and the outgoing connection fails.

Usually, a certificate that uses the Subject Alternate Name attribute would also specify a Common Name attribute in the Subject field.

To resolve this problem, install Rollup 4

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

for Forefront Threat Management Gateway (TMG) 2010 Service Pack 2.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
See the terminology

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

Microsoft uses to describe software updates.

Article ID: 2899713 – Last Review: November 8, 2013 – Revision: 1.0


Applies to
  • Microsoft Forefront Threat Management Gateway 2010 Enterprise
  • Microsoft Forefront Threat Management Gateway 2010 Standard
kbqfe kbfix kbexpertiseinter kbbug kbsurveynew KB2899713

Read the original post:
FIX: Access to certain SSL websites may be unavailable when HTTPS Inspection is enabled in Forefront Threat Management Gateway 2010

FIX: Incorrect Performance Monitor values when queried from a .NET Framework app in Forefront Threat Management Gateway 2010

Consider the following scenario:
  • You use a Microsoft .NET Framework application to query Performance Monitor counters in Microsoft Forefront Threat Management Gateway 2010.
  • The application queries counters for the Forefront TMG Firewall Service.

In this scenario, all the values that are returned by the counters appear incorrect when they’re compared to the values that are returned in Performance Monitor.

For example, this problem occurs when the application queries the Active UDP Connections counter. In this situation, the counter always returns 300 regardless of what the correct value is.

This problem occurs because the Performance Monitor definitions for the Forefront TMG Firewall Service are incorrect.
To resolve this problem, install Rollup 4

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

 for Forefront Threat Management Gateway 2010 Service Pack 2.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
Learn about the terminology

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

Microsoft uses to describe software updates.

Article ID: 2890549 – Last Review: November 8, 2013 – Revision: 1.0


Applies to
  • Microsoft Forefront Threat Management Gateway 2010 Service Pack 2, when used with:
    • Microsoft Forefront Threat Management Gateway 2010 Enterprise
    • Microsoft Forefront Threat Management Gateway 2010 Standard
kbqfe kbfix kbexpertiseinter kbbug kbsurveynew KB2890549

View the original here:
FIX: Incorrect Performance Monitor values when queried from a .NET Framework app in Forefront Threat Management Gateway 2010

Page 323 of 982« First...102030...321322323324325...330340350...Last »

Recent Comments

    Archives

    Categories