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

The "Sent" time stamp on email messages is incorrect in Outlook Web Access or Outlook Web App

The Sent time stamp on email messages may be incorrect when you sign in to Microsoft Office Outlook Web Access or in to Microsoft Outlook Web App. Additionally, the time on meeting requests may also be incorrect.

This issue can occur if all the following conditions are true:

  • You are in a region that does not follow daylight saving time (DST).

  • The server that is running Microsoft Exchange Server where the mailbox is hosted is located in a region that follows DST.

 

To work around this issue, set the time zone on the Exchange Server to a region that matches the Coordinated Universal Time (UTC) zone of the country where the server is located. Make sure that the UTC zone for that country does not follow DST.

You may also have to set the time zone in Outlook Web Access or in Outlook Web App. To do this, follow these steps, as appropriate for your situation. 

Microsoft Exchange Server 2010

  1. Log on to Microsoft Outlook Web App.

  2. Click Options, and then click See All Options.

  3. Click Settings.

  4. Click Regional.

  5. Under Current time zone, click the time zone that you want.

 Microsoft Exchange Server 2007

  1. Log on to Microsoft Office Outlook Web Access.

  2. Click Options.

  3. Click Regional Settings.

  4. In the Current time zone box, click the time zone that you want.

This issue does not occur when you use Microsoft Outlook because Outlook uses the time zone information from the client operating system.

See the article here:
The "Sent" time stamp on email messages is incorrect in Outlook Web Access or Outlook Web App

Event 1000, 1001, or 1002 occurs when SCOM is monitoring Exchange Server 2007 or Exchange Server 2010

Property Value

SMTP connectivity test failed for server_name

The following endpoints aren’t functioning:

server_nameSMTP Connector from Internet (domain_name).0.0.0:2510.8.130. 14:25 4214.3.2 Service not available server_nameSMTP

Connector from Exchange Org.0.0,0:25 10.S.130.14:25 421 4.3.2 Service not available All endpoints were tested. No endpoints were functioning correctly.

Diagnostic command: “Test SmtpConnectivity -MonitoringContext: $true”

1001

Event SourceName: MSsxchange Monitoring SmtpConnectivity
When running the following command in the Exchange Powershell got the following output:

PS C:Windowssystem32>Test-SmtpConnectivity -MonitoringContext $true

ReceiveConnector Binding EndPoint StatusCode
—————- ——- ——– ———-
SMTP Connector from Intern… 0.0.0.0:25 10.8.130.14:25 Error
SMTP Connector from Exchan… 0.0.0.0:25 10.8.130.14:25 Error

Events : Source: MSExchange Monitoring SmtpConnectivity

Id: 1001
Type: Error
Message: SMTP connectivity test failed for
The following endpoints aren’t functioning:

server_nameSMTP Connector from Internet (domain_name).0.0.0:2510.8.130.14:25
421 4.3.2 Service not available
server_nameSMTP Connector from Exchange Org.0.0.0:2510.8.130.14:25
421 4.3.2 Service not available
All endpoints were tested.
No endpoints were functioning correctly.

PerformanceCounters : {}

Continued here:
Event 1000, 1001, or 1002 occurs when SCOM is monitoring Exchange Server 2007 or Exchange Server 2010

SDP 29FD0E15B-6357-4C50-B8EC-74949E538A38 Dynamics GP Update Diagnostic on Windows XP, Windows Vista, Windows Server 2003, and Windows Server 2008

The Dynamics GP Update Diagnostic for Windows XP, Windows Vista, Windows Server 2003, and Windows Server 2008 is designed to collect client & server settings for Microsoft Dynamics GP with specific information for Dynamics GP Upgrade issues.
This article describes the information collected from a machine when running Dynamics GP on Windows XP, Windows Vista, Windows Server 2003, and Windows Server 2008 machines.

Information Collected

SQL Query DU000010 duFileList

Collapse this tableExpand this table

Description File Name
Table – DYNAMICS..DU000010 DYNAMICS_DU000010.*

SQL Query DB_Upgrade

Collapse this tableExpand this table

Description File Name
Table – DYNAMICS..DB_Upgrade DYNAMICS_DB_Upgrade.*

SQL Query DU000030 Failed Table Query

Collapse this tableExpand this table

Description File Name
Table – DYNAMICS..DU000030/SY01500/DU000010 Failed_Table_FailedCompanyTables_DYNAMICS.*

SQL Query sp_help

Collapse this tableExpand this table

Description File Name
For any table that has failed to update correctly, run sp_help on the table Failed_Table_sp_help_XXXX.*

Log Files

Collapse this tableExpand this table

Description File Name
Dynamics client install log (duInstall.log)
Dynamics GP install Log File (GPInstall.log)
Dynamics GP Login Errors (GP_LoginErrors.log)
Dynamics Installer Log File (MSI****.log)
Script.log (if 1 day or less old)
DexSql.log (if 1 day or less old)
Profile.txt (if 1 day or less old)
duInstall.Log
GPInstall_.Log
GP_loginerrors_.log
MSI***.log
Script*.log
Dexsql*.log
Profile*.txt

Additional Information

This diagnostic will run with SQL credentials chosen by the user.  Administrative rights to the local machine is preferred (but not required) as this diagnostic may collect local files & lists of file names.

This diagnostic will also collect information as detailed in this KB:

2640011
(http://support.microsoft.com/kb/2640011)
SDP 3cd735886-e25a-4d66-a351-7469261e2cee Microsoft Dynamics GP System Baseline for Windows 7 and for Windows Server 2008 R2

References

KB 973559 – Frequently asked questions about the Microsoft Support Diagnostic Tool (MSDT)
http://support.microsoft.com/kb/926079
(http://support.microsoft.com/kb/926079)

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.

Continue Reading:
SDP 29FD0E15B-6357-4C50-B8EC-74949E538A38 Dynamics GP Update Diagnostic on Windows XP, Windows Vista, Windows Server 2003, and Windows Server 2008

Week numbers do not match between OWA and Outlook calendars in the English and French versions in an Exchange Server 2007 environment

In a Microsoft Exchange Server 2007 environment, the week numbers that are displayed in the Outlook Web Access (OWA) calendar do not match the week numbers that are displayed in the Microsoft Office Outlook calendar. This issue occurs when you use the English or French version of OWA and of Outlook. For example, in the English version of OWA, the first week number is 2 instead of 1 for the year 2010. However, it is different when you use the English version of Outlook.
To resolve this issue, install the following update rollup:
2608656 

(http://support.microsoft.com/kb/2407025/
)
Description of Update Rollup 6 for Exchange Server 2007 Service Pack 3

After you install this update rollup, Exchange Server 2007 OWA provides an option to select when the week numbers start.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
For more information about the client features in Exchange Server 2007 OWA, visit the following Microsoft website:For more information about how to display the week numbers in Outlook, visit the following Microsoft website:

Original post:
Week numbers do not match between OWA and Outlook calendars in the English and French versions in an Exchange Server 2007 environment

A Lync 2010 user can still send files that contain a long file name after the file transfer is blocked

Assume that you use Microsoft Lync Server Control Panel to set the global file transfer filter to Block all. In this situation, a Lync 2010 user can still send files that contain a file name of more than 58 characters.
To resolve this issue, install the following cumulative update:
2670352 

(http://support.microsoft.com/kb/2670352/
)
Description of the cumulative update for Lync Server 2010: February 2012
For more information about how to change the global filter, visit the following Microsoft website: 

View article:
A Lync 2010 user can still send files that contain a long file name after the file transfer is blocked

The typing status message is not displayed when you use an IME to type double-byte characters in Lync 2010

Assume that you use Microsoft Lync 2010 to join an instant message (IM) conversation or IM conference. You enter double-byte characters in the conversation window by using an Input Method Editor (IME) that uses a buffer to display candidate words (for example, you use a Japanese or Chinese IME). However, the following message is not displayed at the bottom of the conversation windows that belong to other participants of the IM conversation or conference:

sender is typing a message…

To resolve this issue, install the following cumulative update:
2670326 

(http://support.microsoft.com/kb/2670326/
)
Description of the cumulative update for Lync 2010: February 2012

Read the article:
The typing status message is not displayed when you use an IME to type double-byte characters in Lync 2010

You receive a System.UnauthorizedAccessException exception when you disconnect a call in a Lync 2010 SDK-based application

Consider the following scenario:
  • You set a telephone that is running Microsoft Lync 2010 Phone Edition as your default audio device in Lync 2010.
  • You run an application that is based on Lync 2010 SDK to make an audio call.
  • You disconnect the call when the telephone is ringing.

In this scenario, you receive a System.UnauthorizedAccessException exception on the Microsoft.Office.Uc.ModalityClass.Disconnect call. Additionally, the following error message is logged in the Lync 2010 ETL log:

HRESULT failed=0×80070005(ERROR_ACCESS_DENIED)

To resolve this issue, install the following cumulative update:
2670326 

(http://support.microsoft.com/kb/2670326/
)
Description of the cumulative update for Lync 2010: February 2012
For more information about the client-side logging and diagnostics, visit the following Microsoft website:

Read More:
You receive a System.UnauthorizedAccessException exception when you disconnect a call in a Lync 2010 SDK-based application

A customized Lync 2010 Help URL does not work in Lync 2010

Consider the following scenario:
  • You set the CustomizedHelpUrl and EnableEnterpriseCustomizedHelp parameters to configure a client policy to customize the Lync 2010 Help Menu in a Microsoft Lync Server 2010 environment.
  • You apply the client policy to the users in the environment.
  • The update that is mentioned in Microsoft Knowledge Base (KB) article 2514982 is applied to a computer that Lync 2010 runs on.
  • A user signs in to Lync 2010. 
  • The user clicks Lync Help F1 under Help.

In this scenario, Lync 2010 opens the following webpage instead of the customized webpage:

Lync 2010 Help
(http://office.microsoft.com/client/helphome.aspx?lcid=1033&NS=COMM14&pc=oc&ver=4&subver=0&bld=7577&bldver=314)

To resolve this issue, install the following cumulative update:
2670326 

(http://support.microsoft.com/kb/2670326/
)
Description of the cumulative update for Lync 2010: February 2012
For more information about how to set a client policy, visit the following Microsoft website:
For more information about how to customize the Lync 2010 Help menu, visit the following Microsoft website:
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2514982 

(http://support.microsoft.com/kb/2514982/
)
Description of the cumulative update for Lync 2010: November 2011

See more here:
A customized Lync 2010 Help URL does not work in Lync 2010

You cannot use client policy to exclude a folder from contact search in Lync 2010

Consider the following scenario:
  • You deploy Microsoft Exchange Server in a Microsoft Lync Server 2010 environment.
  • You use the SetCsClientPolicy command together with the ExcludedContactFolders parameter to apply a client policy. The policy excludes a folder from contact search.
  • A user signs in to Lync 2010, and then performs a contact search to search a contact that is in the folder.

In this scenario, the contacts in the folder are still displaying in the search results.

To resolve this issue, install the following cumulative update:
2670326 

(http://support.microsoft.com/kb/2670326/
)
Description of the cumulative update for Lync 2010: February 2012
For more information about the Set-CsClientPolicy command, visit the following Microsoft website:

Continue reading here:
You cannot use client policy to exclude a folder from contact search in Lync 2010

The time stamp that is displayed in the IM conversation windows is truncated in Lync 2010

Consider the following scenario:
  • You open Region and Language in Control Panel.
  • You change Short time under Date and time formats to tt h:mm.
  • You change the Format to one of the following languages:
    • Chinese (Simplified, PRC)
    • Chinese (Traditional, Taiwan)
    • Japanese (Japan)
    • Korean (Korea)

  • You sign in to Microsoft Lync 2010, and start an instant message conversation.

In this scenario, the time stamp that is displayed in the instant message (IM) conversation windows is truncated.

To resolve this issue, install the following cumulative update:
2670326 

(http://support.microsoft.com/kb/2670326/
)
Description of the cumulative update for Lync 2010: February 2012

More here:
The time stamp that is displayed in the IM conversation windows is truncated in Lync 2010

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

Recent Comments

    Archives

    Categories