Alfasith AX

Alfasith AX
اللَّهُمَّ انْفَعْنِي بِمَا عَلَّمْتَنِي، وَعَلِّمْنِي مَا يَنْفَعُنِي، وَزِدْنِي عِلْمًا

Sunday, February 16, 2014

"The Application Integration Framework doesn't work" in Dynamic AX 2012 for EP

Hi,
 EP will be sucessfully installed but it throw the error.
 "the Application Integration Framework doesn't work"
 Application Integration Framework (AIF) to run on the same computer as Windows SharePoint Services (WSS) and Enterprise Portal, the virtual directory that AIF is using must be excluded from the SharePoint managed path.
  1. Open the SharePoint Central Administration page or, from the browser on a remote computer, type the URL (for example, http://servername:port) for the pages on the administration port.
To open the SharePoint Central Administration page, click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration.

  1. Click Configure virtual server settings, and then click the name of the site that you are managing.
  2. Under Virtual Server Management, click Define managed paths.
  3. Under Add a New Path, enter the AIF virtual directory path, select Excluded path, and then click OK.
Regards

Error message: "http://server/sites/site_name was not created correctly. Exception: Thread was being aborted."


Hi,
This error occurs because of a connection time-out after you select the Microsoft Dynamics AX template while creating a new top-level Web site in Windows SharePoint Administration. To resolve this problem, follow these procedures:
  • Change the Connection timeout and Http Keep-Alive properties on the server that runs IIS.
  • Change connection time-out properties in the web.config file.
Change the Connection timeout and HTTP Keep-Alive properties on the server that runs IIS
  1. Open the Internet Information Services Manager (Start > Run, type inetmgr, and then press ENTER).
  2. Expand the local computer, expand the Web sites directory, right-click the Web site that hosts your Enterprise Portal site (typically the Default Web site), and then clickProperties.
  3. On the Web Site tab, specify a new value in the Connection timeout field. The default value is 120 seconds.
If for example, the server requires up to 4 minutes to create a new site using EP templates, specify a value of 240 seconds.
  1. Select Enable HTTP Keep-Alives (if it is not selected), and then click OK.
  2. Restart IIS (at a command prompt, enter iisreset, and then press ENTER).
Change connection time-out properties in the web.config file
  1. In a basic text editor such as Notepad, open the web.config file (%SYSTEMDRIVE%\Inetpub\wwwroot by default).
  2. Press CTRL + F to open the Find dialog box.
  3. Find the following tag:
<httpRuntime maxRequestLength="51200" />
  1. Replace it with this tag:
<httpRuntime executionTimeout="6000" maxRequestLength="51200" />
  1. Find the following tag (you might need to search from the beginning of the file):
</sectionGroup>
  1. Add the following tags on new lines after the </sectionGroup> tag:
<sectionGroup name="DynamicsAX">
<section name="Deployment" type="System.Configuration.SingleTagSectionHandler, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
</sectionGroup>
  1. Find the following tag:
</SharePoint>
  1. Add the following tags on new lines after the </SharePoint> tag:
<DynamicsAX>
<Deployment SiteCreationTimeOut="1200" />
</DynamicsAX>

  1. Save your changes and close the web.config file.
  2. At the command prompt, type IISReset, and then press ENTER.
  3. Try to create the top-level Web site in SharePoint Portal Administration.

SQL code to upate one Legal entity banner to all the legal entity in D365

 Hi, update companyimage set  companyimage.Image  = companyimageA.Image  from  ( select Image from companyimage where dataAreaid = 'USF...