We are using Microsoft Dynamics CRM 2013. I have added a user as deployment administrator to one of our servers but when she opens up Deployment Manager she gets the following error
"Only the Deployment Administrators are able to use Deployment Manager. Your are not a Deployment Administrator".
Have checked and she is indeed a deployment manager. When I execute Get-CrmDeploymentAdministrator, her account is present in the list.
Have following are the steps in the blog post http://blogs.msdn.com/b/crminthefield/archive/2013/10/07/6-steps-to-add-a-deployment-administrator-in-microsoft-dynamics-crm-2011.aspx
but the error persists. Any ideas please?
Finally resolved the issue by doing the following
1) Removed user from being a deployment administrator by removing it from the Deployment Manager console (Please note that trying to remove the user using PowerShell commandlet Remove-CrmDeploymentManager resulted in the error "System User xxx is not a deployment manager".
2) Removed the user from the table [SystemUser] and [SystemUserAuthentication].
3) Adding the user again as deployment administrator by running the PowerShell commandlet "New -CrmDeploymentAdministrator.
It's a bit strange the Microsoft Dynamics Crm errors when deleting users using powershell and allows it to be deleted from Deployment Manager console.
The deployment administrator that you added should be a CRM user, did you added him as CRM user?
Thanks for the steps, I had a deployment Administrator account deleted(causing a lot of problems). But maybe some reboots should be expressed.
Working with CRM2015
1) Removed user from being a deployment administrator by removing it from the Deployment Manager console (Please note that trying to remove the user using PowerShell commandlet Remove-CrmDeploymentManager resulted in the error "System User xxx is not a deployment manager".
2) Removed the user from the table [SystemUser] and [SystemUserAuthentication].
Here I had to remove from [SystemUserRoles] as well. A Reboot here may have helped with the next steps
3) Adding the user again as deployment administrator by running the PowerShell commandlet "New -CrmDeploymentAdministrator.
This gave me an error, conflicting arguments in [SystemUserAuthentication]. But it still added the user to [SystemUser]. Second time around I rebooted at this point. After reboot User didn't appear in Deployment Manager. Added the user through Deployment Manager and it worked. Db Tables look correct.
At this point, Deployment Manager is working for Added User. And I am working with CRM2015. Not 2013.
Related
For some time, I get an error when I try to log into my Microsoft account from Visual Studio for my Azure subscription.
My Microsoft account is associated to : Outlook.com (obviously), Office 365, Azure and a Windows Developer.
I ignored this message until now, because I could connect to my database, my websites functioning, etc.
But now I need to publish an application in the Windows Store. When I try to generate my Windows app packages, I found the same error:
We could not refresh the credentials for the account
AADSTS50059: No tenant-identifying information found in either the request or implied by any provided credentials.
Trace ID: eaf34263-377e-41d3-8f72-177827315914
Correlation ID: 15bbcfe8-8bc9-4a83-aa02-288a54e50dd5
Timestamp: 2016-09-19 11:27:20Z
I have already try to clean up cookies, temporary files, another Windows developer account, ...
UPDATES
I have try to download Azure AD Application Proxy Connector.
I had this same problem again on Visual Studio 2017 (15.1).
Solution found:
You have to go to REGEDIT.
Navigate to "Computer\HKEY_CURRENT_USER\Software\Microsoft\VSCommon\ConnectedUser"
And empty all the values, except EnableAzureRMIdentity (change to true if isn't) :
To :
It seems that you’re trying to sign in through a Microsoft account and not a domain that is part of the organization ID of the directory you are trying to access.
So please make sure that the admin is part of the same domain name as the tenant domain.
For example, if your Azure AD domain is contoso.com, the admin should be admin#contoso.com.
You could refer to Troubleshoot Application Proxy.
Moreover, this thread might be helpful to you. Please also try the answer provided by Rich.
I followed some of the advice for this error, including modifying my registry key, however the error changed. And it seems that the #Andrés Talavera is also using a sovereign cloud like I am.
I deleted my Environment Picker JSON file and that is when I got this error when I restart Visual Studio.
After deleting the JSON file, located here: %localappdata%\.IdentityService\AadConfigurations\AadProvider.Configuration.json, I restarted VS17 and I got this error. The JSON file seemed to reappear after the restart. The next time, after I deleted the Registry Key, and removed the JSON file again, SSO worked great.
Note: It seems to be associated to the Environment Picker and pointing to the Sovereign cloud AAD.
When running Sitecore Setup the following error pops up:
Failed to open XML file, system error:-2147024786
I've tried going through the eventviewer but to no avail.
Not unimportant is that I used the installer but forgot to change my rootdirectory. As a consequence I had to uninstall (using the same installer Sitecore).
Now however it "feels" as though there are some references or remnants left behind somewhere.
Who has a clue or can give me an idea of what is going on?
You are correct, this issue is because the previous Sitecore instance, with the same name, has not been removed completely. You will need to manually complete the following tasks to remove the remnants and be able to run the installer, it has worked for me in past;
Stop the App Pool for the uninstalled site in IIS
Stop the Web Application for the uninstalled site in IIS
Perform an iisreset in command line
Delete the App Pool and Web app in IIS
You should now be able to completely delete the folder containing the Website and Data folder completely
If you are still having trouble deleting it check the folder's Security Permissions, the Users and their Permissions and Read Only checkbox. Ensure you have control to delete
Delete the relating entry in the hosts file
If you also installed Databases access them via MSSQL Management Studio, take all relating databases Offline then delete them.
This will effectively remove all remanants of the previous site. If what ever reason the issue still persists, Sitecore's own Sitecore Instance Manager has a delete option which will completely uproot the site for you. Try installing with SIM then.
I need to create installer package for WCF(service) class library,which i created in VS2012 with .net framework 4.5.
2.I try to install the service manually using VS2012 command prompt with the following link, http://www.youtube.com/watch?v=vTPCWrZedKI
Actually it put entry in Window services, when i try to start the service manually i am getting an error like "The service on local computer started and then stopped,Some services stop automatically if they are not in use by other services or programs.
I tried to fix those errors by changing to local system account and clearing the evenlog,
but nothing works fine for me.
I tried it using Advance installer by providing the dll file in Services tab,but it fails to start the service getting an error like "Verify that you have sufficient privileges to start the stystem sevices".
Please tell me how can i proceed further?
I don't need to use third party softwares like wix for creating installer package.
*Is there any way to achieve this task. If so please guide me and give me a sample application to achieve this task.*
I am spending more than 10 days for this task..
Awaiting for your repliessss!!!
Regards,
Lokesh.J
I restarted IIS on our TFS server, and ever since then I haven't been able to access my workspace.
Regardless of what I do, it continually creates a workspace owned by a service account, and not my corporate account.
A couple days ago I had opened SSMS 2008 with "Run as different user" and used that service account. That's the only way I can think that it got in the picture.
So if I run tf workspaces /owner:* I see two workspaces, one owned by me, and one owned by the service.
When I open VS2010, it loads the workspace owned by the service account, and I can't view the other workspaces. Running tf /delete on the wrong one deletes it and running tf /remove:* clears my cache, but when I open VS2010, it is created again.
I tried running VS2010 with "Run as different user" and used my credentials, with no luck.
Anyone have any ideas as to how to get my workspace back??
You can change the owner of a workspace using the /newowner flag to the tf workspace command. For example:
tf workspace /collection:http://server:8080/DefaultCollection workspaceName;oldOwner /newowner:newOwner
This should work as a stopgap measure to allow your old workspace to be owned by the service account. To update this, make sure that you do not have credentials saved for your TFS server in Control Panel -> Credential Manager. These credentials will always override your logged in user credentials or anything specified to runas.
So, not an answer, but a workaround.
I set the actual workspace to public, and now I can at least load it.
I have no idea why VS/TFS thinks I am a service account.
EDIT: Turns out I had the service account credentials for the tfs server saved in Credential Manager. Removing the credentials and restarting VS2010 resolved the issue.
We have a an ASP NET MVC website solution which only one out of three devs on the team is able to publish to the live server. When I, and another colleague, attempt to publish the site from VS 2010, the output window will display an error:
Unable to create the Web site
'\blah'. The path '\blah' does not
exist or you do not have access. The
specified path is invalid.
This points to a logon issue which my account, but the developer who can publish the site is a member of all the same user groups as me. As a long-shot, we gave Everyone full access to the folder, but this did not resolve the problem.
Can anyone suggest a more detailed way to try and figure out why we cannot publish the site? There must be a permission set somewhere that is allowing my colleague to publish the site from Visual Studio.
I had this problem and racked my brain trying to resolve it so I wouldn't have to copy the publish files to a remote server manually. I spent a great deal of time actively trying to get this to work.
Here's how I solved the problem: I went to File>Open in Visual Studio 2010 Express and navigated to the remote server (\\255.255.255.255\folder1\folder2\folder3 and so on). Right away I was challenged for a User Name an Password. I entered the credentials for the REMOTE server, checked the box to 'Remember my credentials'. I immediately tried to publish and voilá - it worked like a charm.
I hope this saves a lot of people a lot of time.
I had this issue - certain members of our team were able to publish directly from VS2010, whereas for some reason I was always getting permission denied errors, even though we were all able to connect to the server we were trying to deploy to. I fixed it in the following way:
Go to "Server Explorer".
Right click "Servers" and go to "Add server..."
Type in the name of the server you are trying to connect to, and then click on "Connect using a different user name..." - put the credentials for logging into the server in here.
Click OK and wait for it to add the server.
Now try and publish to that server and it should be ok...
Not sure why I needed to do this and others were able to deploy without adding the server in this way... remains unexplained.
According to the comments below:
You may need to restart Visual Studio in order for this to take effect.
This should also work for newer versions of Visual Studio
Faced the same problem today. In my situation I had to close VS2010 and open it NOT as an admin and it worked without any problems.
This got me for a long time...Go to Project - Properties and select the Package/Publish Web tab. Under the header "Web Deployment Package Settings", there's a ellipsis button that you can use to map to the location you want to publish. You will be asked for your credentials during that process.
Are you using web deploy (right click and choose Publish)?
Have you tried copying the ProjectName.Publish.xml file from the one machine where you can publish to the other two machines? The login credentials for publishing are saved in this file.
In IIS can you check to see that all users/groups are listed under Management Service Delegation in IIS Manager? It is listed under the Server node in IIS. Alternatively you can give all administrators access by clicking on Edit Features from the side-menu and checking Allow Administrators to bypass rules.
You could also check under IIS Manager Permissions for the individual site to see if the person that can publish is listed under there and you are not.
I just recently setup MSDeploy access on my server and found the following two tutorials helpful:
http://william.jerla.me/post/2010/03/20/Configuring-MSDeploy-in-IIS-7.aspx
http://code-inside.de/blog-in/2011/04/03/howto-setup-of-webdeploy-msdeploy/
I have also found that mapping a drive to the UNC location can be a work around.
#soupy1976's solution has also worked for me.
I can not explain why one day it will work and one day it won't
Frustrating....