KB Articles

Page 1 of 76312345...102030...Last »

Troubleshooting basics for Lync Online and Office Communicator in Office 365 Dedicated

Article ID: 2649420 – Last Review: December 19, 2014 – Revision: 11.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal
  • Microsoft Office Communicator 2007
  • Microsoft Office Communicator 2007 R2

See more here:
Troubleshooting basics for Lync Online and Office Communicator in Office 365 Dedicated

How to use the Configuration Information feature in Office Communicator R2 and Lync 2010 and 2013 clients

The Configuration Information feature in Microsoft Office Communicator (OC) R2 and Microsoft Lync 2010 and 2013 clients can be used to troubleshoot Outlook integration and address book issues.

To access this information, press and hold the Ctrl key while you right-click the Communicator or Lync icon in the notification area, and then click Configuration Information. The information that the Configuration Information feature retrieves occurs during logon and is typically set up by Group Policy. Although this information can be found in the log files and registry, this dialog box offers an easy way to read it. This makes Configuration Information a good starting point for troubleshooting.

Article ID: 3026442 – Last Review: December 19, 2014 – Revision: 2.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal
  • Microsoft Office Communicator 2007
  • Microsoft Office Communicator 2007 R2
  • Microsoft Office Communications Online
  • Microsoft Lync 2010
  • Microsoft Lync 2013

Continue reading here:
How to use the Configuration Information feature in Office Communicator R2 and Lync 2010 and 2013 clients

A muted Polycom HDX serial phone device cannot hear audio from a remote HDX device in a Lync conference

A Polycom HDX serial telephone device that is used in a Lync audio-video conference cannot hear audio from a remote HDX serial telephone device after the mute function is engaged in Lync Server 2010.

Consider the following scenario between three participants in a Lync Server 2010 audio-video conference:

  1. A Lync client calls Polycom HDX telephone device A.
  2. A Lync client calls Polycom HDX telephone device B.
  3. The user on Polycom HDX telephone device A presses Mute.
  4. After 10 to 15 minutes, the user on HDX telephone device A cannot hear audio from the device B.
This problem occurs because the Lync Server 2010 Audio/Video Conferencing Server inadvertently enables an audio codec to support Forward Error Correction (FEC) when it processes the mute operation for device A. The Polycom HDX endpoint does not support FEC. Therefore, the Polycom HDX telephone device A cannot receive audio from the conference.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
Third-party information disclaimer

Collapse this imageExpand this image

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Collapse this imageExpand this image

Article ID: 3022416 – Last Review: December 19, 2014 – Revision: 1.0


Applies to
  • Microsoft Lync Server 2010 Enterprise Edition
  • Microsoft Lync Server 2010 Standard Edition
kbqfe kbfix kbexpertiseinter kbsurveynew KB3022416

Continued here:
A muted Polycom HDX serial phone device cannot hear audio from a remote HDX device in a Lync conference

Microsoft Dynamics CRM 2011 List Component is available for download

A new version of Microsoft Dynamics CRM 2011 List Component for Microsoft SharePoint Server 2010 and Microsoft SharePoint Server 2013 is now available for download.

Fixes in this version of the list component include the following:

  • Using Microsoft SharePoint 2010 or 2013 does not allow document properties to be scrollable after 20 fields are added to a Microsoft SharePoint custom list.
  • Script errors are occurring during document record creation. Error message “SCRIPT5009: ‘IsNull’ is undefined createfolder.aspx, line 11 character 4createfolder.aspx, line 11 character 4″ can occur.
  • Changing the Microsoft SharePoint display language will no longer load documents in the Microsoft Dynamics CRM 2011 list view.

The following file is available for download from the Microsoft Download Center:

Microsoft Dynamics CRM 2011 List Component for Microsoft SharePoint Server 2010 and Microsoft SharePoint Server 2013

(http://www.microsoft.com/en-us/download/details.aspx?id=5283)

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: 3026326 – Last Review: December 16, 2014 – Revision: 2.0


Applies to
  • Microsoft Dynamics CRM 2011
kbmbsmigrate kbsurveynew KB3026326

Continued here:
Microsoft Dynamics CRM 2011 List Component is available for download

Repair update messages are triggered by TimeZoneMatchCheck failures in Exchange Server

In a Microsoft Exchange Server 2013 or Exchange Server 2010 environment, you receive one or more repair update messages on an iOS 8.x or iOS 7.x device. These messages indicate that the Calendar Repair Assistant (CRA) has updated a meeting.

The body of the message contains the following:

Your meeting was found to be out of date and has been automatically updated.

            Updated meeting details:
            Meeting Recurrence        

Analysis of the CRA logs shows that the TimeZoneMatchCheck process failed:

040000008200E00074C5B7101A82E00800000000F076BAF92303D001000000000000000010000000F75B1C45DB47C344BF73214BACD3ED66
      -281888802
      
        
          
            
              Checks whether the counterpart user can be validated or not.
            
            
              Calls Validate() on the base calendar item.
            
            
              Checkes whether the item can be found in the owner's calendar or not.
            
            
              Checkes to make sure that the meeting cancellations statuses match.
            
            
              Checks to make sure that the attendee has correct recurring time zone information with the organizer.
              
                
              
            
            
              Checks to make sure that the attendee has the correct critical properties for the meeting.
            
          
          
            
              
                RecurringTimeZone
              
            
          
        
      
    
    
      

Note The default location for the Calendar Repair Assistant logs is %ExchangeInstallPath%LoggingCalendar Repair Assistant.

Meeting repair update messages may appear in the attendee’s Inbox 12–48 hours after the attendee updated the meeting on his or her iOS 8.x or iOS 7.x device. CRA is trying to correct a discrepancy that was introduced by the iOS device to the time zone property of the attendee’s copy of the meeting.
Resolution of this issue requires changes to the iOS implementation of the Microsoft Exchange ActiveSync protocol. 

Apple has been made aware of this issue, and customers who experience any of these symptoms should contact Apple for help.

Third-party information disclaimer

Collapse this imageExpand this image

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Collapse this imageExpand this image

Article ID: 3019798 – Last Review: December 16, 2014 – Revision: 2.0


Applies to
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
  • Microsoft Exchange Server 2013 Enterprise
  • Microsoft Exchange Server 2013 Standard
  • Microsoft Exchange Online
kbsurveynew kbtshoot kbexpertiseinter KB3019798

More here:
Repair update messages are triggered by TimeZoneMatchCheck failures in Exchange Server

Users can’t sign in to Communicator or Lync in Office 365 Dedicated

oneMscomBlade,oneMsomNav,oneMscomFooter,

Read More:
Users can’t sign in to Communicator or Lync in Office 365 Dedicated

Trial Balance Detail Report is out of balance in General Ledger using Microsoft Dynamics GP

The Trial Balance Detail report in GL is out of balance due to an unbalanced journal entry, or rounding difference using Multi-currency.

To print the Trial Balance Detail report, click on Reports, point to Financial and click on Trial Balance. Under Reports, select Detailed. Insert a report option or create a new report option. In the Trial Balance Report Options window, select the report restrictions as needed and save. Print the report to verify if the total debit amount is equal to the total credit amount.

There is an unbalanced journal entry in the General Ledger tables.
Follow the steps below to locate unbalanced journal entries:

Step 1: Print the Trial Balance report

  1. Open the Trial Balance Report Options window for the Detailed Trial Balance Report by selecting the report option and click the Modify button
  2. In the Include section, make sure the checkbox for Unit Accounts is not marked.
  3. In the Include section, make sure the checkbox for Inactive Accounts is marked.
  4. Print the report again.
  5. Verify that the Detailed Trial Balance Report is still unbalanced.


Step 2: Identify unbalanced General Ledger transaction(s)

To identify unbalanced GL transaction(s), use one of the options below. To run a script that will identify the GL transaction for you, go to the Option 1: “Fix it for me” section. To run a script yourself that will identify the GL transaction, go to the Option #2: “Let me fix it myself” section.

Option #1: Fix it for me

To have us run a script that will identify (not ‘fix’) the GL transaction automatically, click the Fix this problem button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.
Note This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

Option #2: Let me fix it myself

To identify (not ‘fix’) the GL transaction yourself, follow these steps:

Method #1: Use SQL scripts

  1. Use the appropriate step below to open SQL Server Management Studio:
    • If you use SQL Server 2000, start SQL Query Analyzer. To do this, click Start, point to Programs, point to Microsoft SQL Server, and then click Query Analyzer.
    • If you use Microsoft SQL Server 2005, start SQL Server Management Studio. To do this, click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
    • If you use Microsoft SQL Server 2008 or R2, start SQL Server Management Studio. To do this, click Start, point to Programs, point to Microsoft SQL Server 2008, and then click SQL Server Management Studio.
  2. Copy the below script in to a query window and execute against the company database to identify unbalanced journal entries.
    select JRNENTRY, sum(DEBITAMT) - sum(CRDTAMNT) from GL20000, GL00100 where ACCTTYPE = 1 group by JRNENTRY having sum(DEBITAMT) - sum(CRDTAMNT) <> 0

Method #2: Use the automated solution for “General Ledger Out of Balance” to find the unbalanced journal entries. This solution can be found using the link below to KB 935384.

KB 935384 – Automated Solutions that are available for the Financial series in Microsoft Dynamics GP
https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;EN-US;935384

(https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;EN-US;865712)

Step 3: Fix

Once you have identified the unbalanced journal entry, the course of action will vary depending on if it is in a current open year, or in a historical year as follows: 

  • If the unbalanced journal entry is in a current open year, you can delete the entry directly from the GL20000 table, and reconcile the year in the front-end (to get the GL summary tables updated). Then rekey the journal entry correctly.
  • If the unbalanced journal entry is in a historical year, you will need to reopen the GL year first. If you are on Microsoft Dynamics GP 2013 R2 or later versions, you can do this yourself using the ‘Reverse Historical Year’ checkbox in the Year-End Closing routine window. However, if you are Microsoft Dynamics GP 2013 SP2 or a prior version, you must contact your Partner to start a consulting service to have the GL year reopened for you via SQL Scripting. Once the year is reopened, you can delete the entry directly from the GL20000 table, reconcile the year in the front-end, rekey the entry correctly, and then reclose the year again. 
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: 2428683 – Last Review: December 16, 2014 – Revision: 9.0


Applies to
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0, when used with:
    • General Ledger
    • Financials General Ledger
    • Multicurrency Management
kbmbsmigrate kbsurveynew kbfixme kbmsifixme KB2428683

Originally posted here:
Trial Balance Detail Report is out of balance in General Ledger using Microsoft Dynamics GP

MS14-082: Description of the security update for Microsoft Office 2010: December 9, 2014

This security update resolves a vulnerability that could allow remote code execution if a specially crafted file is opened in an affected edition of Microsoft Office.
Microsoft has released security bulletin MS14-082. Learn more about how to obtain the fixes that are included in this security bulletin: 
  • For individual, small business, and organizational users, use the Windows automatic updating feature to install the fixes from Microsoft Update. To do this, see Get security updates automatically

    (http://www.microsoft.com/security/pc-security/updates.aspx)

    on the Microsoft Safety and Security Center website.

  • For IT professionals, see Microsoft Security Bulletin MS14-082

    (http://technet.microsoft.com/security/bulletin/MS14-082)

    on the Security TechCenter website.

Known issues with this security update

  • After you install this security update, you may receive an error message that resembles any of the following when you insert a Forms ActiveX control (forms3) into an Office document, or when you edit the properties of a control:

    Visio cannot insert this control because its TypeInfo did not merge correctly. Ensure all parameter types are VBA friendly. Delete TEMP *.exd file if necessary.

    Object library invalid or contains references to object definitions that could not be found.

    OR

    OR

    The program used to create this object is Forms. That program is either not installed on your computer or it is not responding.
    To edit this object, install Forms or ensure that any dialog boxes in Forms are closed.

    Note In this error message, the Forms text may also be replaced by the GUID of the control.

For more information about how to resolve this issue, click the following article number to view the article in the Microsoft Knowledge Base:

3025036

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

 ”Cannot insert object” error in an ActiveX custom Office solution after you install the MS14-082 security update

Download information

This update is available for download from the Microsoft Download Center

(http://www.microsoft.com/downloads/details.aspx?FamilyId=2cad2f33-5a05-48ff-9a9d-afec218e73c6)

.

Prerequisites to apply this security update

To apply this security update, you must have Service Pack 2

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

for Microsoft Office 2010 installed on the computer.

Restart information

You may have to restart the computer after you install this security update.

In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message is displayed that advises you to restart the computer.

To help reduce the possibility that a restart will be required, stop all affected services and close all applications that may use the affected files before you install this security update.

Learn about why you may be prompted to restart your computer

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

after you install a security update on a Windows-based computer.

Removal information

Note We do not recommend that you remove any security update.

To remove this security update, use the Add or Remove Programs item or use the Programs and Features item in Control Panel.

Note When you remove this security update, you may be prompted to insert the disc that contains Microsoft Office. Additionally, you may not have the option to uninstall this security update from the Add or Remove Programs item or the Programs and Features item in Control Panel. There are several possible causes for this issue.

Learn about the ability to uninstall Office updates

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

.

Security update replacement information

This security update does not replace any previously released security update.

File information

Collapse this imageExpand this image

The English version of this security update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

For all supported x86-based versions of Office 2010

Collapse this tableExpand this table

File name File version File size Date Time
Fm20.dll 14.0.7140.5001 1,217,192 19-Nov-2014 12:31
For all supported x64-based versions of Office 2010

Collapse this tableExpand this table

File name File version File size Date Time
Fm20.dll 14.0.7140.5001 1,614,504 19-Nov-2014 12:26

Collapse this imageExpand this image

Article ID: 2553154 – Last Review: December 16, 2014 – Revision: 4.0


Applies to
  • Microsoft Office 2010 Service Pack 2
kbsecvulnerability kbsecurity kbsecbulletin kbfix kbexpertiseinter kbbug atdownload KB2553154

See original article:
MS14-082: Description of the security update for Microsoft Office 2010: December 9, 2014

Replicationapp.exe crashes when FIPS is enabled on a Lync Server 2013-based computer that has .NET Framework installed

When this issue occurs, the following events are logged in Application log for Microsoft Lync Server 2010:

Log Name: Lync Server
Source: LS Routing Data Sync Agent
Date: Date Time
Event ID: 48007
Task Category: (1058)
Level: Error
Keywords: Classic
User: N/A
Computer: Computer Name
Description:
An unhandled exception was encountered in Routing Data Sync Agent.

Message=System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

at System.Security.Cryptography.SHA1Managed..ctor()
at System.IO.IsolatedStorage.IsolatedStorage.GetAccountingInfo(Evidence evidence, Type evidenceType, IsolatedStorageScope fAssmDomApp, String& typeName, String& instanceName)
at System.IO.IsolatedStorage.IsolatedStorage._InitStore(IsolatedStorageScope scope, Evidence domainEv, Type domainEvidenceType, Evidence assemEv, Type assemblyEvidenceType, Evidence appEv, Type appEvidenceType)
at System.IO.IsolatedStorage.IsolatedStorage.InitStore(IsolatedStorageScope scope, Type domainEvidenceType, Type assemblyEvidenceType)
at System.IO.IsolatedStorage.IsolatedStorageFile.GetStore(IsolatedStorageScope scope, Type domainEvidenceType, Type assemblyEvidenceType)
at MS.Internal.IO.Packaging.PackagingUtilities.ReliableIsolatedStorageFileFolder.Dispose(Boolean disposing)
at MS.Internal.IO.Packaging.PackagingUtilities.ReliableIsolatedStorageFileFolder.Finalize()

Cause: This is an unexpected error. Look through the exception details for more information.

Resolution:

More information may be available in the server traces. If the problem persists, contact product support and provide the event details.

Log Name: Lync Server
Source: LS Server
Date: Date Time
Event ID: 12331
Task Category: (1000)
Level: Error
Keywords: Classic
User: N/A
Computer: Computer Name
Description:
Worker process exited prematurely.  The process will be automatically restarted.

Process: ‘C:Program FilesMicrosoft Lync Server 2010ServerCoreReplicationApp.exe’  Exit Code: E0434F4D!_HRX! (No Message Text Found!_HRM!).

Note FIPS means Federal Information Processing Standard.

Cause

This issue occurs because Microsoft .NET Framework uses non-FIPS compliant implementation of Secure Hash Algorithm 1 (SHA1), such as the SHA1Managed Class.

Article ID: 3021977 – Last Review: December 13, 2014 – Revision: 1.0


Applies to
  • Microsoft Lync Server 2010 Enterprise Edition
  • Microsoft Lync Server 2010 Standard Edition
  • Microsoft .NET Framework 2.0 Service Pack 2
kbqfe kbfix kbsurveynew kbexpertiseinter KB3021977

Read More:
Replicationapp.exe crashes when FIPS is enabled on a Lync Server 2013-based computer that has .NET Framework installed

"Cannot insert object" error in an ActiveX custom Office solution after you install the MS14-082 security update

After you install the security update that is described in Microsoft Security Bulletin MS14-082

(http://technet.microsoft.com/security/bulletin/MS14-082)

, you may experience either of the following symptoms:

Symptom 1

When you insert a Forms3 control into a Microsoft Office document, or when you edit the properties of a control, you may receive an error message that resembles one of the following in an ActiveX custom Office solution: 

Object library invalid or contains references to object definitions that could not be found.

The program used to create this object is Forms. That program is either not installed on your computer or it is not responding.
To edit this object, install Forms or ensure that any dialog boxes in Forms are closed.

Note In this last error message, the Forms text may be replaced by the GUID of the control.

Symptom 2

When you use Office Click-to-Run to install Office 2013 on a computer that has a Side-by-Side installation of the 2007 Office suite or Office 2010, you may experience the same errors that are mentioned in the “Symptom 1″ section. 

Resolution 1

To resolve the issue that is described in the “Symptom 1″ section, delete the cached versions of the control type libraries (extender files) on the client computer. Search the hard disk for files that have the “.exd” file-name extension, and delete all the MSForms.exd files that you find. To do this, follow these steps:

  1. In Windows Explorer, open the %TEMP% folder, and then search for “MSForms.exd” in all subfolders.
  2. Delete all instances in which that file is found. This includes all subfolders.

Note The .exd files will be re-created automatically when you use the new controls the next time that you use VBA. These extender files will be under the user’s profile and may also be in other locations, such as the following folders:

  • %appdata%microsoftforms
  • %temp%excel8.0
  • %temp%word8.0
  • %temp%PPT11.0
  • %temp%vbe

Resolution 2

To resolve the issue that is described in the “Symptom 2″ section, follow these steps:

  1. Follow the steps that are described in the “Resolution 1″ section.
  2. Make sure that the 2007 Office suite or Office 2010 and Office Click-to-Run have the latest updates installed. To obtain the latest updates for Click-to-Run, perform an online repair of Office 2013.

Learn about how to repair Office

(https://support.office.com/en-au/article/Repair-an-Office-application-7821d4b6-7c1d-4205-aa0e-a6b40c5bb88b)

.

Learn more about Office Click-to-Run

(https://support.office.com/client/Learn-more-about-Office-ClicktoRun-9948b3a9-e3ef-4d73-b645-727bb2d9e365)

.

Article ID: 3025036 – Last Review: December 13, 2014 – Revision: 2.0


Applies to
  • Microsoft Excel 2013
  • Microsoft Excel 2010
  • Microsoft Office Excel 2007
  • Microsoft Word 2013
  • Microsoft Word 2010
  • Microsoft Office Word 2007
  • Microsoft PowerPoint 2013
  • Microsoft PowerPoint 2010

Continued here:
"Cannot insert object" error in an ActiveX custom Office solution after you install the MS14-082 security update

Page 1 of 76312345...102030...Last »

Recent Comments

    Archives

    Categories