Monday, March 26, 2012
If you get this error then you give the full access to "C:\intepub\wwwroot\". One more thing you run the business portal set up using "Run as Administrator" mode.
The above two methods solved my BP Installation Issue.
I hope this will help to all.
Monday, January 9, 2012
Wednesday, July 21, 2010
System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.EnterpriseServices.Thunk.Proxy.CoCreateObject(Type serverType, Boolean bQuerySCInfo, Boolean& bIsAnotherProcess, String& uri)
at System.EnterpriseServices.ServicedComponentProxyAttribute.CreateInstance(Type serverType)
at System.Runtime.Remoting.Activation.ActivationServices.IsCurrentContextOK(Type serverType, Object props, Boolean bNewObj)
Problem in MSTDC or Some DTC prerequest is not installed in that system.
1.Go To Component services(Start--Administrative Tools-->Component Services)
2.Go To My Computer in Component services
3.Right Click and go to properties of My computer
4.Click MSTDC tab and goto Security Configuration
4.Make sure that following fields are checked in that window AllowInbound.Allow outbound,XA transactions,No authentication
5.Then you restart the Distributed Transaction Service in Services.
6. Some time service restart will through same exception.
7.If DTC throw any exception then you should check the system has installed MSMQ or not.Mostlt DTC throw error due to absence of MSMQ
8.Install MSMQ and restart service
9.Now you execute your application.
Friday, June 18, 2010
When you want to change your sa login property in sql server, it could not allow you to change with this messge "Alter failed for Login 'sa'".
Solution: If you change anything in 'sa' Login property then you should mark 'Map to Credential' field in General tab before you click OK.
Monday, December 8, 2008
This is typically caused by something being damaged in .NET framework in that particular system.
The eConnect .NET bits are all written on the 1.1 framework or There is an invalid version of mscoree.dll on the computer
So repairing .NET framework 1.1 would probably be the first step to try to solve this problem.
Repair .NET framework 1.1:
Steps to repair the .NET Framework installation
Step1: Obtain the original installation source. For example, if you installed the .NET Framework from a CD-ROM or from a
DVD, insert that disc. If you downloaded the .NET Framework , download the .NET Framework again. Make sure that you
click save to disk. If you installed the .NET Framework from a network share, reconnect to that share.
Step2: Click Start, click Run, type the following command, and then click OK: Step3:N:\dotnetframework\dotnetfx.exe /t:c:\temp /c:"msiexec.exe /i c:\temp\netfx.msi REINSTALL=ALL ReinstallMODE=vomus" Note Replace N:\ in this command syntax with the original installation path.
Important If you do not have a C:\temp folder on your computer, create one before you run this command.
Try to delete mscoree.dll from system32 directory and then install .NET Framework (or move it somewhere if you cannot delete it).
Or do the following steps
1.From the desktop, double-click My Computer.
2.Open the C drive.
3.Open the WINDOWS or WINNT folder.
4.Open the System32 folder.
5.Right-click the mscoree.dll file and select Rename. (For Windows 98 and ME systems, this file is located in the system folder instead of system32).
6.Rename the file to oldmscoree.dll and press
7.Delete the URTTEMP folder. (For Windows 98 and ME systems, this file is located in the system folder instead of system32)
8.Go back to My Computer.
9.Open the WINDOWS folder and delete the Microsoft.NET folder.
Reinstall the Microsoft.NET Framework by removing and inserting the Point installation CD-ROM.
10.When the installation is complete, open My Computer.
11.Open the C drive.
12.Open the WINDOWS or WINNT folder.
13.Open the System32 folder and delete the oldmscoree.dll file.
This error may occurring in the Microsoft installer and may be caused by either anti-virus or other file detection software.
Disable Anti-Virus / Anti-Spy ware programs as they may be preventing the Microsoft installer from writing to the registry.
Sunday, November 9, 2008
1.Check the hardware requirement mentioned in BPInstallation document.
2.Check the Software requirement
2.1. Before install the WSS/SharepointPortalserver 2003, you should make the following setups
2.1.1. You can do this by using the wizard to “Administer Your Server” or you can go into “Add/Remove Programs” within the Control Panel.
2.1.2. After opening Add/Remove Programs, click on the left pane item named “Add/Remove Windows Components”. In the list that appears, select “Application Server”.
2.1.4. In the component list, also select “IIS” and then click on
2.1.5. If you’re going to anticipate the need for some backward compatible components functionality, you should add in “SMTP Service” as a selection also.
2.1.6. If you elect to install the backward compatible components, it may take over an hour. It might give the appearance of a locked system or that nothing’s happening; don’t be misled by that.
2.2. Catalog Maintenace Installation.
2.2.1. Catalog Maintenace is not properly woking in Windows Server 2003 with SP2.So After installing the catalog maintenace, Open it(StartUp-->Programs-->Microsoft Dynamics-->Catalog Maintenance.Now Login to catalog maintenance.)
2.2.2. You Receive error about "frmmain",then you uninstall the SP2 and install SP1.
2.2.3.Nowreinstall the catalog maintenance.
3.Now install the BusinessPortal.
Friday, October 10, 2008
1.When loading a PO Receipt containing items with a FIFO/LIFO Periodic valuation method (standard cost), eConnect is not creating the distributions properly. eConnect is not handling this.
2.When loading a PO Receipt containing Non-Inventory items, eConnect is not creating the distributions properly for PPV.
You should handle this problem in taPOPEnterMatchInvHdrPost event.
While I am going to talk about eConnect, I would like to disclaim that the explanations are JUST out of my understanding of the concepts of eConnect and the structure. Please do refer to some more articles from Microsoft, Consultants worldwide and others to know more about this and also correct my own understanding in case you find it irrelevant.eConnect use Windows Authentication to converse with GP Databases instead of the traditional SQL Authentication (which GP uses). There could be various reasons why it is designed in such a way.
I am listing some of the important reasons:
1. eConnect does not require GP Application, or precisely, it does not depend on an Instance of GP Application to be running (which is the case with Integration Manager for most of its Integrations). This would mean that, the login credentials for an eConnect integration cannot be inherited from anywhere. We still have to establish a Connection String (ODBC) to the GP Databases to access the data and manipulate it.
2. eConnect is designed to run in the background and access/manipulate the GP databases without anyone's idea of what's going on with the records and database. Apparently, there should be a kind of authentication which is much more stronger than the basic SQL Authentication, which the Windows Authentication provides us.
3. eConnect is the base for almost all the web based features we have for Dynamics GP, such as Webservices, Business Portal, etc. We cannot have a compartively weaker Authentication level when we allow anyone to access GP Databases from anywhere.4. eConnect can utilize MSMQ (Microsoft Message Queuing), to queue the integrations from anywhere to the Dynamics GP server. In such cases, it has to have a Windows Authentication to pass the MSMQueuing validations.I am still learning more concepts on these two Authentications and its scope with respect to GP and related products. I will update more points with references, so it does not just go in as a theory.