Page 322 of 982« First...102030...320321322323324...330340350...Last »

Financial Reports from Management Reporter do not match the General Ledger Trial Balance Reports in Microsoft Dynamics GP

Many different reporting tools can be used to prepare Financial reports used to balance to the GL Trial Balance Report in Microsoft Dynamics GP. So you must determine if your Financial reports are reading from GL data only, or if AA data is also being used. If AA data is being used to prepare the Financial reports, they may be skewed if the data in the AA tables does not match the data in the GL tables. 
  • Data Mart with Management Reporter will read from AA tables if AA has been activated. This is by design.
  • With the Legacy option, you can choose if you want to pull from an AA company or a GL company. So you drive if the AA tables are used or not in your reporting.
  • FRx reporting uses GL tables.

Financial reporting may be incorrect, if AA data was used to assemble the report, and your AA data does not match GL data.  Records may be missing from AA tables, or may be skipped if they differ from the corresponding record in GL.

There are several reasons that the AA data may not match the GL data or have issues, including:

  • The Analytical Accounting module has not been installed on all workstations, where users are keying/posting transactions. Therefore, the record exists in GL, but not AA.
  • Users are disabling the Analytical Accounting module if they received any error referencing ‘aa’, so AA tables are not updated.
  • Records are being imported directly into GL tables, and not AA tables. Or users are disabling AA if they receive any ‘aa’ errors during the import process.
  • Users are closing the GL year on a workstation where AA has not been installed.  As a result the AA records are not moved to history and no Balance Brought Forward journal entry is created in the AA tables.
  • Management Reporter may not read the AA record if the currency ID differs between the AA record and the corresponding record in GL, which could be caused by importing records, activating Multicurrency, or any quality issues with currency ID’s that have since been fixed.
  • The Dynamics database was restored over itself, causing the ‘Next Available Number’ (in the AAG00104 table) to be set back to a value that has already been used. This system will increment off of this value for the next header ID value as it inserts new records into the table, and so it can duplicates if it is inserting in a heard ID value that has already been used.  
  • If you upgrade to Microsoft Dynamics GP 2013 and set a functional currency ID, but are not registered for Multicurrency, or you do not run check links as instructed after setting up the functional currency.
  • osting interruptions
If you need assistance to correct any of the results returned from the scripts below, please open a support incident using the categories below to reach the correct Support Engineer Team. Please include the information as noted within each step. 

STEPS:

Please copy/download the SQL scripts below, and execute against the company database in SQL Server Management Studio.  Data returned by any of these SQL scripts below will cause Financial Reports in MR-Data Mart not to balance with GL Trial Balance reports. 

***Please make a current backup of the company database before running any scripts that will update data.***

See KB #871973 – Set up a test company that has a copy of live company data by using SQL Server 7.0, SQL Server 2000, SQL Server 2005, SQL Server 2008, or SQL Server 2012
http://support.microsoft.com/kb/871973

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

NOTE: To view the results of each script in Text, you can press ALT – T (or click on Query in the top menubar, point to Results To, and click on Results to Text) and then execute the script again. This will provide more details for each section of results returned.

STEP 1 – DISTINCT YEARS

Please run both scripts below to verify that the years are distinct in each table and do not overlap.  If you find the same year listed in both tables or scrambled between the tables, please open a support case for further assistance. Please include the results of both scripts. 

select distinct(YEAR1) from AAG30000 order by YEAR1
select distinct(YEAR1) from AAG40000 order by YEAR1

STEP 2 – FIND CURRENCY ID DISCREPANCIES

Please download the AA_FindCurrencyDiscrepancy.sql script to locate transactions where the Currency ID does not match between GL and AA tables in both open and history:

https://mbs2.microsoft.com/fileexchange/?fileID=5e791b42-42d8-4be4-b293-21415349124b

(https://mbs2.microsoft.com/fileexchange/?fileID=5e791b42-42d8-4be4-b293-21415349124b)

*If you do not use Multicurrency, or just use only one currency ID, you can simply update the CURNCYID and CURRNIDX fields directly in the AA (AAG30001/AAG40002) or GL (GL20000/GL30000) tables. Test to make sure the currency ID is matching on recently keyed transactions to ensure there is not an ongoing issue. Please open a support incident if you need assistance to update the CURNCYID directly in the SQL table, or if you are able to recreate this on a current transaction. 

*If Multicurrency is being used, please open a support incident and include the following:

  • Provide the results of the script in text format. We need to know which table had the currency ID and which table did not. And are these older or newer transactions? If older transactions and you just installed Multicurrency Management, did you run check links on Multicurrency Setup? Check links should go back and update the currency ID on all existing transactions. 
  • What version of Microsoft Dynamics GP are you using?
  • Where did the transactions come from? Test to see if this is an ongoing issue. Verify if Multicurrency Management is marked in the Registration window (under Microsoft Dynamics GP, point to Tools, point to Setup, point to System, and click on Registration.)
  • What is your functional currency? How many currency ID’s do you use?
STEP 3 – FIND UNMATCHED DISTRIBUTIONS

Please download the AA_FindUnmatchedDists.sql script. If any results are returned, please open a support case for further assistance. Please attach the file of results in text format. These problem records are usually due to importing issues, or users working on a workstation where AA was disabled or not installed. 

https://mbs2.microsoft.com/fileexchange/?fileID=0d654196-5853-46c8-b478-f31decd60096

(https://mbs2.microsoft.com/fileexchange/?fileID=0d654196-5853-46c8-b478-f31decd60096)

STEP 4 – FIND DUPLICATE AA CODE ID’S

Please download the AA_FindDupaaTrxDimCodeID_AAG00401.sql script. If any results are returned, please open a support case for further assistance. Please attach the results of the script in text format, and also the contents of the AAG00401 table. We can provide you the steps to resolve this, but having Microsoft do this for you may be a consulting expense. This issue is usually caused by importing, or by restoring an older copy of the Dynamics database over itself. 

https://mbs2.microsoft.com/fileexchange/?fileID=32b007ba-bd82-4a5e-ac10-983f3f32b157

(https://mbs2.microsoft.com/fileexchange/?fileID=32b007ba-bd82-4a5e-ac10-983f3f32b157)

STEP 5 – FIND DUPLICATE AA HEADER ID’S

Please execute the below script to determine if you have header ID’s duplicated between the AA open and historical tables. We can provide the steps to resolve this, but having Microsoft do this for you may be a consulting expense. This issue is usually caused by importing, or by restoring an older copy of the Dynamics database over itself, or a posting interruption.

select * from AAG30000 where aaGLHdrId in (select aagLHDrId from AAG40000)

If any results are returned, please open a support case and include the following information:

  • Results of the script in text format.
  • Research the records and advise if they are the exact same record, or if they are different records, but just have the same Header ID only.
STEP 6 – FIND MISMATCHED SEQUENCE NUMBERS

Download and run the AA_FindYEC_RetainedEarnings.sql script to look for records where the Sequence Numbers do not match between AA and GL between open and history tables for the Retained Earnings journal entry. If any results are returned, please open a support case and include the results of the script in text format.

https://mbs2.microsoft.com/fileexchange/?fileID=fe4b1ddf-718f-4e40-bcae-799b31df749d

(https://mbs2.microsoft.com/fileexchange/?fileID=fe4b1ddf-718f-4e40-bcae-799b31df749d)

STEP 7 – FIND MISSING BBF ENTRIES

If you find that your Financial reports are off by the amount of the beginning balances, the Balance Brought Forward (BBF) entries may be missing from the AA tables. Please run the script below to determine if the BBF entries in GL are missing from AA tables. This is caused by the user closing the GL year on a workstation where AA was disabled or not installed. If the journal entry is missing in AA, you will need to have a consulting service set up to have the GL year reopened. Then when you reclose the year again in GL on a workstation where AA is active, the BBF entries will be created in both GL and AA by the year-end close process. 

-----------------------------------------------------
Select distinct (JRNENTRY) from GL20000
where JRNENTRY not in (select JRNENTRY from AAG30000)
and SOURCDOC in ('BBF','P/L')
-----------------------------------------------------

STEP 8 – REBUILD THE DATA MART

After all of the results have been fixed above, rerun each script to make sure no results are no longer returned.

Then rebuild the Data Mart in Management Reporter and generate your Financial reports again. Here are the steps to do this (as a precaution, you can backup the DDM database, as this will be deleted and re-created):

1. Open the Configuration Console on the server from the Start menu.
2. In the left hand navigation pane, click ERP Integrations.
3. Click the integration being used (note the server name and the database names), and disable the integration with the “Disable Integration” button.
4. Click “Remove” to remove the ERP Integration.
5. Click the Management Reporter Services in the left hand navigation and stop both of the Management Reporter Services.
6. Delete the DDM database in SQL (you can make a backup first, if needed).
7. Start the Management Reporter Services.
8. Configure the ERP Integration again by going to “File > Configure”.
9. Once the setup is completed, enable the ERP integrations.

With the AA data corrected, and the DDM updated MR should pull in the correct values.

STEP 9 – VERIFY REPORT BALANCES

Detemine if the report balances to the GL Trial Balance report or not.  If not, see if you can determine what the difference is. Is the difference still related to the Balance Brought Forward Entries not being correct? If so, please open a support incident for further assistance.

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.

View original post here:
Financial Reports from Management Reporter do not match the General Ledger Trial Balance Reports in Microsoft Dynamics GP

Users are unable to release messages from the Exchange Online Protection quarantine when using a Mac

Users may see a certificate related error when trying to release a message from the Exchange Online Quarantine.

ERROR MESSAGE

The website “na01-quarantine.dataservice.protection.outlook.com” requires a client certificate.

1) Find the Keychain Access program on your Mac. To find it, open up Finder, then open up the Applications folder. Inside the Applications folder there is a folder called Utilities. The Keychain Access program is in the Utility Folder.

2) Open Keychain Access and search for all of the certificates that are listed in the Safari dialog box that tell you “This client requires a certificate“.

3) When you find those particular certificates, select them and then DELETE those specific certificates out of Keychain Access.

4) Restart Safari and try again.

Article ID: 2909418 – Last Review: November 18, 2013 – Revision: 1.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Exchange Online Protection

Follow this link:
Users are unable to release messages from the Exchange Online Protection quarantine when using a Mac

FRx Report Displays Chart of Accounts from Wrong Database

SYMPTOMS

In the Row Format, when adding accounts to the Link to GL column the incorrect accounts for the company logged into in FRx, are not appearing. They appear to be from another database.

CAUSE

The FRx Company Information screen is connecting to an incorrect GL ODBC Data Source (application database), System Database Name, or Company ID.


RESOLUTION

Enter the correct GL ODBC Data Source, System Database Name, and Company ID in FRx Company Information | System Specific Information.

1. Access FRx Company Information | System Specific Information.

2. Enter the correct GL ODBC Data Source (if it does not exist it would need to be created), System Database Name, and Company ID in their corresponding fields.

3. Save changes and exit.

MORE INFORMATION

If using FRx 6.x refer to

This article was TechKnowledge Document ID: 133325

Article ID: 873620 – Last Review: November 18, 2013 – Revision: 3.0


Applies to
  • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
  • Microsoft Dynamics SL 6.5
  • Microsoft Business Solutions–Solomon 6.0
  • FRx Financial Reporter 6.5
kbsolomonfrx kbmbsmigrate KB873620

Original post:
FRx Report Displays Chart of Accounts from Wrong Database

Gridlines not printing as expected in Excel

When printing a workbook or worksheet, and gridlines are set to print, Excel is not printing the gridlines as expected.
This is seen in the following scenario:

The default printer driver with a Universal Printer Driver connected to a printer that is capable and set to a high resolution setting (e.g. 1200 dpi).

AND

The workbook is printed and saved with these print settings.

AND

From the same system, or another system, using the same Universal Printer Driver, but connected to a different printer, which has a lower resolution capability (e.g. 600 dpi) the workbook is then printed to this printer.

Option 1: Prior to printing the workbook or worksheet, open the printing preferences, and select the printer properties option. Within the printer properties, set the print quality to 600 dpi, and save the file to retain the 600 dpi setting for future printing.

Option 2: Install and load the model-specific driver for the printer rather than the Universal Printer Driver. (Example: When printing from an HP Laserjet 4020, install and use the Laserjet 4020 printer driver, not the Universal Printer Driver)

Option 3: Print to a printer that is 1200 dpi capable if using a Universal Printer Driver (e.g. HP LaserJet 9040). 

Microsoft is aware of this issue. When saving the file, Excel stores printer related information within the workbook.  This cached information is then compared to the client’s default printer information when the workbook is printed.  If the information is different, Excel will use the client’s default printer information. 

However, in the scenario described above, since the same Universal Printer Driver is being used in both cases, Excel does not consider the lower resolution printer to be different, and as such uses the cached information when printing the workbook.  This results in the workbook being printed at a higher resolution than the printer supports and this leads to the issue described within the Symptoms section.

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: 2893418 – Last Review: November 15, 2013 – Revision: 2.0


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

Read More:
Gridlines not printing as expected in Excel

Mail access issues in a hybrid Exchange deployment with cloud-based archive

554 5.2.0 STOREDRV.Deliver.Exception:UserWithoutFederatedProxyAddressException;

Failed to process message due to a permanent exception with message User doesn’t have any SMTP proxy address from a domain that is federated.

UserWithoutFederatedProxyAddressException: User doesn’t have any SMTP proxy address from a domain that is federated. ##

View original post here:
Mail access issues in a hybrid Exchange deployment with cloud-based archive

FIX: The host name affinity expires unexpectedly when you enable the External Cache option in Application Request Routing 3.0

Assume that you install the Microsoft Application Request Routing (ARR) 3.0 module on a server that is running Internet Information Services (IIS) 7.0, 7.5, or 8.0. Then, you enable the External Cache option when you configure the host name affinity of an ARR server farm. In this situation, the host name affinity expires before the configured time-out period. Additionally, the client affinity cookie for the requests is changed.

Hotfix information

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

Collapse this imageExpand this image

Download the package now.

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

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591

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

How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

To apply this hotfix, you must have Microsoft Application Request Routing (ARR) 3.0 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfix.

File information

The English version of this hotfix 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.

Collapse this imageExpand this image

For all supported x86-based versions of ARR for IIS 7.0, 7.5 or 8.

Collapse this tableExpand this table

File name File version File size Date Time Platform
Ecache.dll 7.1.1901.0 123,096 21-Oct-2013 13:42 x86
For all supported x64-based versions of ARR for IIS 7.0, 7.5 or 8.

Collapse this tableExpand this table

File name File version File size Date Time Platform
Ecache.dll 7.1.1901.0 123,096 21-Oct-2013 13:42 x86
Ecache.dll 7.1.1901.0 129,752 21-Oct-2013 13:42 x64

Collapse this imageExpand this image

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
For more information about how to use multiple ARR servers, go to the following Microsoft website:

Article ID: 2904746 – Last Review: November 14, 2013 – Revision: 2.0


Applies to
  • Microsoft Internet Information Services 7.0
  • Microsoft Internet Information Services 7.5
  • Microsoft Internet Information Services 8.0
kbfix kbsurveynew kbexpertiseadvanced atdownload KB2904746

Link:
FIX: The host name affinity expires unexpectedly when you enable the External Cache option in Application Request Routing 3.0

Update adds Windows 8 and Windows Server 2012 support to stand-alone Forefront Endpoint Protection 2010 clients

This article describes an update that enables the Microsoft Forefront Endpoint Protection 2010 client to support Windows 8 and Windows Server 2012.

After you install this update, you can install the Forefront Endpoint Protection 2010 client on a computer that is running Windows 8 or Windows Server 2012.

Note This update applies to the stand-alone Forefront Endpoint Protection 2010 client.

Update information

How to obtain this update

This update is available from Windows Update

(http://update.microsoft.com/)

.

Prerequisites

To apply this update, you must have Forefront Endpoint Protection 2010 Update Rollup 1 installed.

For more information about Update Rollup 1 for Forefront Endpoint Protection 2010, click the following article number to view the article in the Microsoft Knowledge Base:

2551095

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

Update Rollup 1 for Forefront Endpoint Protection 2010

Restart requirement

You do not have to restart the computer to apply this update.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Additional information

This update brings the antimalware client version to 4.1.0522.0. You can find the version information by clicking About on the Help menu of the Endpoint Protection client user interface.

File information

This update includes a new version of the Forefront Endpoint Protection Configuration Manager deployment package. For more information about how to deploy the client update, go to the “Installing FEP 2010 Update Rollup 1″ TechNet article that is described in the “References” section.

The Forefront Endpoint Protection deployment package installs the FepInstall.exe file. FepInstall.exe contains several .msi files, which are listed in the following tables. The English version of these packages has the file attributes that are listed in the following tables:

For x86-based versions of Forefront Endpoint Protection 2010

Collapse this tableExpand this table

File name File version File size Date Time Platform
Dw20shared.msi Not applicable 1,850,368 08-Feb-2012 08:06 Not applicable
Epp.msi Not applicable 7,094,272 12-Sep-2012 12:56 Not applicable
Eppmanagement.msi Not applicable 688,128 12-Sep-2012 12:56 Not applicable
Fepclient.msi Not applicable 872,448 12-Sep-2012 12:56 Not applicable
Setup.exe 4.1.522.0 857,888 12-Sep-2012 09:25 x86
Sqmapi.dll 6.1.7600.16385 196,416 08-Feb-2012 08:06 x86
Windows6.0-kb981889-v2.msu Not applicable 1,241,780 08-Feb-2012 08:06 Not applicable
Windows6.1-kb981889.msu Not applicable 907,883 08-Feb-2012 08:06 Not applicable
For x64-based versions of Forefront Endpoint Protection 2010

Collapse this tableExpand this table

File name File version File size Date Time Platform
Dw20shared.msi Not applicable 2,081,792 08-Feb-2012 08:06 Not applicable
Epp.msi Not applicable 8,265,728 12-Sep-2012 15:38 Not applicable
Eppmanagement.msi Not applicable 819,200 12-Sep-2012 15:38 Not applicable
Fepclient.msi Not applicable 1,011,712 12-Sep-2012 15:38 Not applicable
Setup.exe 4.1.522.0 1,140,496 12-Sep-2012 13:21 x64
Sqmapi.dll 6.1.7600.16385 241,984 08-Feb-2012 08:06 x64
Windows6.0-kb981889-v2.msu Not applicable 1,909,720 08-Feb-2012 08:06 Not applicable
Windows6.1-kb981889.msu Not applicable 1,318,677 08-Feb-2012 08:06 Not applicable
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
For more information about how to deploy the client update, go to the following Microsoft TechNet website: For more information about the update applies to Forefront Endpoint Protection 2010 clients that are integrated with Microsoft System Center Configuration Manager 2007, click the following article number to view the article in the Microsoft Knowledge Base:
2758685

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

Update adds Windows 8 and Windows Server 2012 support to Forefront Endpoint Protection 2010 clients

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

824684

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

Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 2780435 – Last Review: November 13, 2013 – Revision: 4.0


Applies to
  • Microsoft Forefront Endpoint Protection 2010
kbqfe kbfix atdownload kbsurveynew kbexpertiseadvanced KB2780435

See more here:
Update adds Windows 8 and Windows Server 2012 support to stand-alone Forefront Endpoint Protection 2010 clients

Update adds Windows 8 and Windows Server 2012 support to Forefront Endpoint Protection 2010 clients

This article describes an update that adds Microsoft Forefront Endpoint Protection 2010 client support to Windows 8 and Windows Server 2012.

After you install this update, you can install the Forefront Endpoint Protection 2010 client on a computer that is running Windows 8 or Windows Server 2012.

Note This update only applies to Forefront Endpoint Protection 2010 clients that are integrated with Microsoft System Center Configuration Manager 2007.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this update, you must have the following products installed:

  • System Center Configuration Manager 2007 Service Pack 2 (SP2)
  • Forefront Endpoint Protection 2010 Update Rollup 1

    For more information about Update Rollup 1 for Forefront Endpoint Protection 2010, click the following article number to view the article in the Microsoft Knowledge Base:

    2551095

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

    Update Rollup 1 for Forefront Endpoint Protection 2010

Restart requirement

You do not have to restart the computer to apply this update.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Additional information

This update brings the antimalware client version to 4.1.0522.0. You can find the version information by clicking About on the Help menu of the Endpoint Protection client user interface.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

System Center Configuration Manager 2007 file information

For x86-based versions of Forefront Endpoint Protection 2010

Collapse this tableExpand this table

File name File version File size Date Time Platform
Commonconstants.dll 2.1.1116.110 26,232 01-Jul-2011 02:15 x86
Commonsetuputils.dll 2.1.1116.110 68,232 01-Jul-2011 02:15 x86
Fep2010su1-fepext-kb2758685-x86-enu.msp Not applicable 25,153,536 01-Jul-2011 02:15 Not applicable
Fepinstall.exe 4.1.522.0 25,078,248 20-Sep-2012 00:06 x86
Fepregistrator.exe 2.1.1116.110 121,464 01-Jul-2011 02:15 x86
For x64-based versions of Forefront Endpoint Protection 2010

Collapse this tableExpand this table

File name File version File size Date Time Platform
Commonconstants.dll 2.1.1116.110 26,232 01-Jul-2011 02:15 x86
Commonsetuputils.dll 2.1.1116.110 68,232 01-Jul-2011 02:15 x86
Fep2010su1-fepext-kb2758685-amd64-enu.msp Not applicable 25,153,536 01-Jul-2011 02:15 Not applicable
Fepinstall.exe 4.1.522.0 25,078,248 20-Sep-2012 00:06 x86
Fepregistrator.exe 2.1.1116.110 121,464 01-Jul-2011 02:15 x86

Note Because of dependencies, some other files may be updated. However, the binaries of these files are not changed.

Client update

This update includes a new version of the Forefront Endpoint Protection Configuration Manager deployment package. For more information about how to deploy the client update, see the “Installing FEP 2010 Update Rollup 1″ TechNet article that is described in the “References” section.

The Forefront Endpoint Protection deployment package installs the FepInstall.exe file that is listed in the tables earlier in this article. FepInstall.exe contains several .msi files, which are listed in the following tables. The English version of these packages has the file attributes that are listed in the following tables:

x86

Collapse this tableExpand this table

File name File version File size Date Time Platform
Dw20shared.msi Not applicable 1,850,368 08-Feb-2012 08:06 Not applicable
Epp.msi Not applicable 7,094,272 12-Sep-2012 12:56 Not applicable
Eppmanagement.msi Not applicable 688,128 12-Sep-2012 12:56 Not applicable
Fepclient.msi Not applicable 872,448 12-Sep-2012 12:56 Not applicable
Setup.exe 4.1.522.0 857,888 12-Sep-2012 09:25 x86
Sqmapi.dll 6.1.7600.16385 196,416 08-Feb-2012 08:06 x86
Windows6.0-kb981889-v2.msu Not applicable 1,241,780 08-Feb-2012 08:06 Not applicable
Windows6.1-kb981889.msu Not applicable 907,883 08-Feb-2012 08:06 Not applicable

x64

Collapse this tableExpand this table

File name File version File size Date Time Platform
Dw20shared.msi Not applicable 2,081,792 08-Feb-2012 08:06 Not applicable
Epp.msi Not applicable 8,265,728 12-Sep-2012 15:38 Not applicable
Eppmanagement.msi Not applicable 819,200 12-Sep-2012 15:38 Not applicable
Fepclient.msi Not applicable 1,011,712 12-Sep-2012 15:38 Not applicable
Setup.exe 4.1.522.0 1,140,496 12-Sep-2012 13:21 x64
Sqmapi.dll 6.1.7600.16385 241,984 08-Feb-2012 08:06 x64
Windows6.0-kb981889-v2.msu Not applicable 1,909,720 08-Feb-2012 08:06 Not applicable
Windows6.1-kb981889.msu Not applicable 1,318,677 08-Feb-2012 08:06 Not applicable
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
For more information about how to install a System Center Configuration Manager 2007 hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
2477182

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

System Center Configuration Manager 2007 Hotfix Installation Guidance

For more information about how to deploy the client update, go to the following Microsoft TechNet website:

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

824684

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

Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 2758685 – Last Review: November 12, 2013 – Revision: 4.0


Applies to
  • Microsoft Forefront Endpoint Protection 2010
kbqfe kbexpertiseadvanced kbsurveynew kbfix kbautohotfix kbhotfixserver KB2758685

See the article here:
Update adds Windows 8 and Windows Server 2012 support to Forefront Endpoint Protection 2010 clients

How To Populate a DataSet Object from a Database by Using Visual C# .NET

DataSet objects, a key part of data access in the Microsoft .NET Framework, are in-memory objects that can hold tables, views, and relationships. This article demonstrates how to fill a DataSet object with the results of one or more database queries and how to access that data after it is loaded into the DataSet object.

Requirements

The following list outlines the recommended hardware, software, network infrastructure, and service packs that you need:

  • Microsoft Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, or Windows NT 4.0 Server
  • Microsoft SQL Server 7.0, Microsoft SQL Server 2000, or Microsoft Data Engine with the Pubs sample database installed
  • Microsoft Visual Studio .NET

This article assumes that you are familiar with the following topics:

  • Database terminology
  • Structured Query Language (SQL)


Filling a DataSet

Using a variety of objects from within the System.Data namespace, you can connect to a database server, run a query, and have the results placed into a DataSet object. The DataSet is a disconnected object. Therefore, after the data is loaded, the connection to the database is no longer used until you want to load more data or update the server with the changes you have made to your in-memory copy of the information.

To load data from a database into a DataSet, follow these steps:

  1. Start Visual Studio .NET.
  2. Create a new Console Application project in Visual C# .NET. Visual Studio .NET creates a Static Class for you, along with an empty Main procedure.
  3. Make sure that the project references the System and System.Data namespaces.
  4. Use the using statement on the System, System.Data, and System.Data.SqlClient namespaces so that you are not required to qualify declarations from these namespaces later in your code. You must use these statements before any other declarations.
    using System;
    using System.Data;
    using System.Data.SqlClient;
    					

  5. The first step to get data from the database to the DataSet is to establish a database connection, which requires a System.Data.SqlClient.SqlCommand object and a connection string. The connection string in the code to follow connects a SQL Server server that is located on the local computer (the computer where the code is running). You must modify this connection string as appropriate for your environment. After the SqlConnection object is created, call the Open method of that object to establish the actual database link.
    string sConnectionString;
    sConnectionString = "Password=myPassword;User ID=myUserID;"
      					   + "Initial Catalog=pubs;"
    						+ "Data Source=(local)";
    SqlConnection objConn
    	= new SqlConnection(sConnectionString);
    objConn.Open();
    					

  6. Create a DataAdapter object, which represents the link between the database and your DataSet object. You can specify SQL or another type of command that is used to retrieve data as part of the constructor object of the DataAdapter. This sample uses a SQL statement that retrieves records from the Authors table in the Pubs database.
    SqlDataAdapter daAuthors
    	= new SqlDataAdapter("Select * From Authors", objConn);
    					

  7. You must declare and create an instance of a DataSet object, at which time you can supply a name for the entire DataSet before you can start to load any data. The name may contain several distinct tables.
    DataSet dsPubs = new DataSet("Pubs");
    					

  8. The SqlDataAdapter class provides two methods, Fill and FillSchema, that are crucial to loading this data. Both of these methods load information into a DataSet. Fill loads the data itself, and FillSchema loads all of the available metadata about a particular table (such as column names, primary keys, and constraints). A good way to handle the data loading is to run FillSchema followed by Fill. For example:
    daAuthors.FillSchema(dsPubs,SchemaType.Source, "Authors");
    daAuthors.Fill(dsPubs,"Authors");
    						

    If you only use Fill, you can only load the basic metadata that is required to describe the column names and data types. The Fill method does not load primary key information. To change this default behavior, you can set the MissingSchemaAction property of the DataAdapter object to MissingSchemaAction.AddWithKey, which loads the primary key metadata along with the default information. For example:

    daAuthors.MissingSchemaAction = MissingSchemaAction.AddWithKey;
    daAuthors.Fill(dsPubs,"Authors");
    					

  9. The data is now available as an individual DataTable object within the Tables collection of the DataSet. If you specified a table name in the calls to FillSchema and Fill, you can use that name to access the specific table that you want.
    DataTable tblAuthors;
    tblAuthors = dsPubs.Tables"Authors";
    					

  10. You can use a For Each loop to loop through all of the DataRow objects within the Rows collection of a DataTable. This gives you access to each row of the table. You can access columns by name or by positional index (with ’0′ being the first column position). For example:
    foreach (DataRow drCurrent in tblAuthors.Rows)
    
    	Console.WriteLine("0 1",
    		drCurrent"au_fname".ToString(),
    		drCurrent"au_lname".ToString());
    }
    Console.ReadLine();
    					

  11. Save your project. On the Debug menu, click Start to run your project and make sure that it works.


Complete Code Listing

using System;
using System.Data;
using System.Data.SqlClient;

namespace PopulateDataSet

	///

	/// Summary description for Class1.
	/// 

	class Class1

		static void Main(string[] args)

			string sConnectionString;
			sConnectionString = "Password=myPassword;User ID=myUserID;"
								+ "Initial Catalog=pubs;"
								+ "Data Source=(local)";
			SqlConnection objConn
				= new SqlConnection(sConnectionString);
			objConn.Open();

			SqlDataAdapter daAuthors
				= new SqlDataAdapter("Select * From Authors", objConn);
			DataSet dsPubs = new DataSet("Pubs");
			daAuthors.FillSchema(dsPubs,SchemaType.Source, "Authors");
daAuthors.Fill(dsPubs,"Authors");

			DataTable tblAuthors;
			tblAuthors = dsPubs.Tables"Authors";

			foreach (DataRow drCurrent in tblAuthors.Rows)

				Console.WriteLine("0 1",
					drCurrent"au_fname".ToString(),
					drCurrent"au_lname".ToString());
			}
			Console.ReadLine();
		}
	}
}
				

For more information about ADO.NET, DataSet objects, and SQL, refer to the following Microsoft Web sites:

Article ID: 314145 – Last Review: November 12, 2013 – Revision: 4.0


Applies to
  • Microsoft ADO.NET 1.1
  • Microsoft Visual C# .NET 2002 Standard Edition
  • Microsoft Visual C# .NET 2003 Standard Edition
kbhowtomaster kbsqlclient kbsystemdata KB314145

Read the article:
How To Populate a DataSet Object from a Database by Using Visual C# .NET

Integration between Lync Server and Exchange Online fails because a firewall or proxy blocks the connection

When you deploy on-premises Microsoft Lync Server 2013 or Microsoft Lync Server 2010 with Microsoft Exchange Online integration, you experience the following symptoms:
  • When you view the Lync client Configuration Information, the EWS Information is displayed as Not Deployed. When this occurs, the Lync client can’t check the Calendar or Out of Office (OOF) information by using Exchange Web Services (EWS).
  • The Lync client Autodiscover process with Exchange Online fails.
Important Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration

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

in case problems occur.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this issue, add the OverrideDirectHttpConnection registry key so that the Lync client won’t try a direct HTTP connection. To do this, follow these steps:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:

    For Lync 2010:

    HKEY_CURRENT_USERSoftwareMicrosoftCommunicator

    For Lync 2013:

    HKEY_CURRENT_USERSoftwareMicrosoftOffice15.0Lync

  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type OverrideDirectHttpConnection, and then press Enter.
  5. Right-click OverrideDirectHttpConnection, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor.

This issue occurs when the following conditions are true:
  • A firewall is configured to block direct connections from internal client computers (end-users on Lync) from making direct connections to the Internet over HTTP port 80 and HTTPS port 443.
  • The proxy settings in Internet Explorer are configured to redirect all traffic that’s trying to go out over ports 80 or 443 through the proxy server. However, Lync will try to connect directly to Exchange over port 80 or port 443 to autodiscover.contoso.com instead of using the proxy settings that are defined in Internet Explorer. NoteContoso.com is a placeholder for the domain that you use for your organization.
  • The firewall will block this direct connection attempt and by the time Lync tries to fall back to use the proxy server, the request times out. Therefore, we have to force Lync to use the proxy first in this situation.

Article ID: 2907651 – Last Review: November 12, 2013 – Revision: 2.0


Applies to
  • Microsoft Office 365 for enterprises (pre-upgrade)
  • Microsoft Office 365 for small businesses  (pre-upgrade)
  • Microsoft Office 365 for education  (pre-upgrade)
  • Microsoft Lync Online
  • Microsoft Exchange Online
  • Microsoft Lync 2013
  • Microsoft Lync 2010
  • Microsoft Lync Server 2013
  • Microsoft Lync Server 2010 Enterprise Edition
o365062011 o365022013 o365e o365p o365a o365m pre-upgrade after upgrade o365 KB2907651

See more here:
Integration between Lync Server and Exchange Online fails because a firewall or proxy blocks the connection

Page 322 of 982« First...102030...320321322323324...330340350...Last »

Recent Comments

    Archives

    Categories