I am using...
XrmToolBox version 1.2017.7.18
Dynamics 365 Online (login is with user#org.onmicrosoft.com)
I try to create a new connection.
I enter http://orgname.crm.dynamics.com for the Organization url.
then my user / pass
I get this error.
Then, I try...
using a connection string.
I click the link "Let me try to connect using a connection string"
I have tried many connection strings but the one that I think to be correct is listed below.
org is an example name for my Org Name
<connectionStrings>
<add name="Crm" connectionString="Url=https://org.crm.dynamics.com; Username=user#org.onmicrosoft.com; Password=mypass; AuthType=Office365" />
</connectionStrings>
When I try to connect I get the following error.
I am not sure why I am getting these errors.
I too faced same issue. When I try to connect with latest version of XRM toolbox(1.2018.3.21), it's connected successfully. You too try with this version and regarding connection using connection string we should not supposed to use as you specified.We just need to specify the connection string content only.For example as follows
Url=https://org.crm.dynamics.com; Username=user#org.onmicrosoft.com; Password=mypass; AuthType=Office365
Related
I tried several times to publish my website from Visual Studio 2019 to the Azure server but I getting errors.
I have an MVC-CORE 3.0 project which works fine using IIS EXPRESS (localhost).
In my web-application, there is a login page (home page), which is the first view. It perfectly works both on Azure and the localhost.
But once I using the published website and log in to my account (=move to the next view), I got this error:
*The login process works great using localhost
*I already published my app 2 months ago and it perfectly worked!
This error appeared just after republishing (private needs).
Please HELP ME !!!
I think you should try these way to solve you issues.
According to your describe, you can open you site correctly. But when you do other operations, the error occured. Here are my advice,
Tips 1, check your web.config file ,make sure you dbConnection is correct. Pls pay attention to Connection strings in portal.And the priority on the portal is higher than that in the web.config.
Tips 2, check your web.config file ,modify the config, like the post. Add settings like below,
<configuration>
<system.web>
<customErrors mode="Off" />
</system.web>
</configuration>
If my advices don't work, you can try to solve the problem by Monika Reddy-MSFT's way.
Update
If you can't open you site correctly, pls check Stack settings in portal.
And next time when you republish your apps, you can backup publish file first in order to restore previous version. Or you can publish your app in slot, if it works fine then you can swap it.
Have you tried to set the environment variable inside the web app on Azure?
If not, please try this:
Open the Application Settings blade --> Scroll Down to -->"Application Settings" --> add the "ASPNETCORE_ENVIRONMENT" and "Development".
Also please take a look at this doc for more reference.
I am try to use the visual studio add-in "CRM 2011 Web Resource Linker/Publisher" from http://webresourcelinker.codeplex.com/.
When connecting to CRM 2013 Online, I get this error "Connection failed: There is an error in XML document(5, 5)"
I have checked Discovery Url, Username, Password, Unique Org Name.
Could you tell me what's wrong?
Thank you
I've found out how to resolve it, but still don't know the root cause. Here the steps:
Go to path: C:\Users\<current user>\LiveDeviceID
Delete the LiveDevice.xml
Try to connect from the application.
If this doesn’t solve the error, follow steps 1 and 2, reboot and try connecting from the application.
This should solve the problem.
Reference: http://skynetr.wordpress.com/2012/04/24/crm-2011-error-there-is-an-error-in-xml-document-5-5/
I have installed Exchange server version 2013. Then I tried to create and connect to the server using MFCMAPI tool manually. While login to the message store it throws the following error
"Error:
Code: MAPI_E_FAILONEPROVIDER == 0x8004011D
Function CallOpenMsgStore( lpMAPISession, (ULONG_PTR)m_hWnd, lpEntryID, ulFlags, (LPMDB*)lppMAPIProp)
File MainDlg.cpp
Line 437 "
And i had gone through to the article given below and followed the instructions given in the same. But, now also i get the same "MAPI_E_FAILONEPROVIDER == 0x8004011D"error as before.
link : http://blogs.msdn.com/b/dvespa/archive/2013/05/21/how-to-mfcmapi-create-mapi-profile-exchange-2013.aspx
Please help me to resolve my problem.
Problem:
You will get this error message if the Outlook profile is in the Cache mode.
Solution:
On the client computer, open the Control Panel and click the Mail icon.
Open the <Profile>, click the email account and select the related <Account>.
Click Change.
Verify that the Use Cached Exchange Mode box is unchecked.
Exchange 2013 only allows ROH (RPC-over-HTTP) connections. See http://blogs.msdn.com/b/dvespa/archive/2014/01/16/create-outlook-profile-exchange-2013.aspx and http://blogs.msdn.com/b/dvespa/archive/2014/01/17/how-create-outlook-profile-office-365.aspx for the steps on how to create ROH profiles.
I had a similar problem and found that the link on dave vespas blog is pointing to an old version of mapicdo.
Make sure you have the latest version of mapicdo & mfcmapi and try again.
I've run into an issue with Breeze such that when I try to call the Metadata action on my controllers, they fail with a 504 error.
The approximate call is
//servername/breeze/controller/metadata
Environment
Web Api running via IIS7 on load balanced Win 2k8 Azure Virtual Machines
Versions (installed via NuGet)
Breeze Client 1.4.2
Breeze Client and Server 1.4.2
Breeze Server - for ASP.NET Web Api (Core) 1.4.2
Breeze Server - for ASP.NET Web Api and Entity Framework 1.4.2
Update: Upgrading to Breeze 1.4.5 makes no difference
Previously it worked fine and the only recent change is the introduction of load balancing.
Of note, I also have multiple controllers, each with their own metadata.
Cases where it runs sucessfully
Running via localhost.
Removing the [BreezeController] attribute from my controller
Renaming the metadata function
Cases where it fails
When deployed
When running a simple test to return a string, eg:
[HttpGet]
public string Metadata()
{
return "This was a test";
}
For some reason Breeze does not seem to like the Metadata function in my controller.
Updates:
It doesn't look like its specifically related to using a load balanced endpoint as I tried setting it up running directly on port 8080 with a non load balanced endpoint and had the same issue.
IIS failed request tracing doesn't seem to log anything for the failed request, though the request does appear in the IIS logs.
I had the same problem after updating from 0.72 to 1.41 and changing the route from api/{controller}/{action} to breeze/{controller}/{action}. I did not get an answer from the breeze folks so I withdrew the question.
However, I now think the problem was permissions. Localhost:50033 in VS ran as me and I have a SQL Server account, so I though it would be cool. After deployment to my local IIS and to a test server IIS, I was getting a 500 error.
I finally got way into the jquery code and determined from the jqXHR, that the error was SQL not handling the credentials for the anonymous user; a Doh! moment if there ever was one. I changed my connection string in web.config and that did it.
<!--<add name="PilotPlant" connectionString="Data Source=dataweb;Database=PilotPlant;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />-->
<add name="PilotPlant" connectionString="Data Source=dataweb;Database=PilotPlant;Trusted_Connection=no;User Id=sa;Password=sapassword" providerName="System.Data.SqlClient"/>
This is less secure, but I am running inside the firewall, so it is not a problem for me.
So my answer is check your permissions on the cluster. I hope this helps.
I am in the process of creating a blog site from scratch using MVC 3.0 and the Entity Framework. I am using a SQL CE .sdf file for the data store. This is stored in the projects App_Data folder. Locally, everything works fine. Not a problem. The .sdf file is read and processed without error. However, after using Web Deploy to publish to a shared hosting provider, I get the following error when trying to view the remote site:-
Access to the database file is not allowed
The connection string I am using in web config is:-
<connectionStrings>
<add name="DataAccess.BlogDbContext" connectionString="Data Source=DansMVCBlog.sdf" providerName="System.Data.SqlServerCe.4.0" />
</connectionStrings>
I have researched the problem and have hit a brick wall. Suggestions have included adding App_Data/DansMVCBlog.sdf to the connection string file path rather than just the file name. This does not work as you are advised the file path is invalid. On the shared hosting control panel, I have set read/write permissions on the App_Data folder to be true. Also, in my Global.asax file, I have disabled
`Database.SetInitializer(new DataInitializer());
Am I making a schoolboy error here? Does anyone have any suggestions? Thanks
Looks like the OP may have solved their problem but in my case, it turned out that the database file had been marked as Read Only by my source control system. Clearing the Read Only flag solved the problem.
You probably need to update your connection string
<connectionStrings>
<add name="DataAccess.BlogDbContext"
connectionString="Data Source=|DataDirectory|DansMVCBlog.sdf"
providerName="System.Data.SqlServerCe.4.0" />
</connectionStrings>
Who knows what the solution to this was. All I can say is I was having problems publishing using web deploy, so I switched to using ftp. After that everything worked just fine.