When I install MSCRM 2015, I have met the problem
Microsoft.Crm.Setup.Server.GrantAspNetServiceAccountAccessAction failed
"The parameter is incorrect"
Microsoft.Crm.Setup.Server.GrantAspNetServiceAccountAccessAction failed
Our team has used the solution mentioned in Unable to install crm 2013 on server 2012, and the installed is performed by domain administrator account, but still the above problem exists.
We have checked the OU, there are no "Account Unknown" entries in AD.
Finally, We managed to solve the problem. The cause is due to the customer’s AD version. The customer has 4 AD servers.
One of the AD servers is on Window 2008 which we thought fulfill the AD requirement for MSCRM2015. However, the functional levels of the AD is actually window 2003 as it takes the lowest function level version from other AD servers even it has the higher version. The pre-requisite for MSCRM2015 is that AD is window 2008 and above therefore it gives the error.
Related
I trying to use EasyRepro https://github.com/microsoft/EasyRepro/tree/releases/OnPremise to automate UI testing for our on premise Customer Relationship Management site part of the Dynamic 365 apps.
What I have tried so far is running the sample test which comes with the EasyRepro as well as using an ADFS login function. I have also tried the later and earlier branches of the Easy Repro and the on premise branch, since I am using an on premise version of CRM. I ensured the drivers were installed and that I am using the correct versions as well that they are all compatible.
What happens is the google chrome browser opens up to the CRM website then meets the login page. Nothing happens till the test times out after about 3 minutes.
Specs
Visual Studio Enterprise 2017
Google Chrome v74
Windows Server 2012 R2
CRM Version 1612 (8.2.2.112) on-premises
I'm trying to configure MSOffice 2016(x64) on a Windows Server 2012(x64) to run with ABCPdf 9.1.2.5(x64).
At runtime, the application fails because of this message: "Failed to get MS Office installation path."
So far I couldn't find an explicit explanation of why this problem occurs.
The application pool uses the "ApplicationPoolIdentity" (instead of dedicated account) and Office has been installed with an account having Admin privileges.
I also followed recommandation on websupergoo website link here
Machine has been restarted after installation, DCOM config has been made accordingly to instructions given (both for folders and launch/activation);
Is there any way to login as Application Pool user in cmd to run WinWord once ?
Is there any AppData file to copy from one user to another - like for OpenOffice installation ?
For anyone trying this kind of configuration, please be aware that highest compatible version with AbcPDF is Office 2013. Office 2016 is compatible from version 10.
Below, answer from support
The highest version with ABCpdf 9 is Office 2013 - for Office 2016 you
would need to upgrade to ABCpdf 10.
Since office was preinstalled on my laptop, i had to reinstall office 365 through the Office app that was already available.. then abcpdf was able to find my installation path
After cloning a 2010 TFS server, upgrading the clone's OS to 2012R2, upgrading SQL Server to 2012 SP2 (11.0.5343), uninstalling TFS 2010, and upgrading to TFS 2013 with update 5, we are running into issues starting the Build Service on the clone.
I've removed the agents and build controllers referencing the other original server through Manage Build Controllers, in Visual Studio 2013.
I've tried to use the TFS 2013 upgrade wizard and it fails when attempting to start the build service so I tried to unconfigure: "tfsconfig.exe setup /uninstall:TeamBuild" and reconfigure through the TFS 2013 upgrade wizard but it yielded the same result.
The TFS database server, Build Server, controller, and agent are located on the same box
For measure, I've even deleted the agents, controllers, and Unregistered and Registered the Build Service in the Team Foundation Server Administration Console as both the batch account used on the original server but that failed so to rule out authentication, I used my domain account (I'm a Local Admin, SQL Server Admin, and TFS Admin) but still had the same result with both accounts.
The Windows event log states “Service cannot be started. The handle is invalid”.
I'm not sure what else could be missed does anyone have any pointers?
There were over 100 Microsoft patches/updates applied over the weekend and the issue went away. Microsoft confirmed that the issue was related to the OS, not the TFS configuration or installation/upgrade.
Thanks for all your suggestions. Hopefully this will help someone else out if they are in the same situation and spinning wheels to find the answer. Keep your systems as up to date as possible!
Try to remove build service by going to Team Foundation Server Administration Console, select server name, and click Remove Feature, to remove build service feature, then re-configure it.
I have TFS 2013 Update 3 installed on a machine and I'm trying to configure the TFS Build service on another machine on the same domain. The registration of the build service completes successfully but the service, controller, and build agents go into an endless start/stop/restart loop. The event viewer on the build machine gives the following error in the Build Services Operational log:
Build machine 'x' lost connectivity to message queue tfsmq://buildservicehost-18/.
Reason: TF30063: You are not authorized to access http://tfs2013:8080/tfs/defaultcollection.
Things I have tried:
Both NetworkService account and a domain account for the build configuration
Unregistering/re-registering the build service
Uninstalling TFS on build machine and reinstalling
Creating a fresh server 2012 install, installing TFS build component on it
The domain account I tried to use was in the build service account group for the collection and I've even tried putting it in the admin group. I also tried running it as my own domain account which is a tfs admin and domain admin account. All with the same results. The fact that this occurred on 2 different machines, one with a completely fresh everything install leads me to believe the problem is on the TFS application tier itself but I have no idea where to go from here. Visual studio is able to connect to TFS just fine for all users.
It sounds like you have a TFS 2012 server that you are trying to connect a TFS 2013 build agent to. This is not a supported configuration.
It is recommended that your build Agents version of TFS matched the version on the server. This does not mean that you can't build with any version of MSBuild or VS that you want on that agent. That's configuration.
I ended up resolving this by doing the following:
Detach Collection
Backup Collection as a precaution
Uninstall TFS 2013 from the App Tier (which is also the Data Tier)
Re-install TFS 2013 and configure it for single server like it was without creating a collection
Attach the existing collection
Uninstall TFS on the build server
Re-install TFS on the build server and configure the service, controller, and agents.
This worked fine and didn't cause me to lose anything. I still don't understand why I was having problems in the first place but my only guess is that it was some type of remnant from doing a migration based upgrade from TFS 2010.
I'm having problems installing development machine for Sharepoint (Foundation) 2010. This is what I did so far on the same machine:
Installed a clean Windows 7 x64 with 4GB of RAM without being part of any domain. Just a simple standalone machine.
Enabled IIS related features as described here except IIS6 related ones (two of them)
Installed SQL Server 2008 R2 Development Edition (DB Engine and Writer being enabled but not SQL Agent)
Installed Visual Studio 2010 Premium
Started installing Sharepoint Foundation 2010 with first extracting files, changing config to enable Windows 7 installation and then installed it as Server Farm (then Complete) to avoid installing SQL Express.
Created a separate SPF_CONFIG local user with Logon on as a service right.
Opened SPF Management Shell and run New-SPConfigurationDatabase so I am able to use a non-domain username (SPF_CONFIG that I created in the previous step)
But all I get is this:
The outcome after this error is:
Database Sharepoint2010Config is created
User SPF_CONFIG is added to SQL Server and attached to this newly created database as dbowner
Checking SQL server security logins this user has following rights:
dbcreator
securityadmin
public
Resolved it myself after trying all kinds of things
The main thing is I haven't given up and installed stadalone installation.
I've followed two guides:
this blog post
and this MSDN resource
Step by step instructions I followed (may be helpful to someone else as well):
Then I've uninstalled SPF2010
Setup all accounts as described in the first document
Reinstalled all prerequisites and KBs described in MSDN resource.
Cancelled configuration wizard and ran Sharpoint PowerShell
Executed
New-SPConfigurationDatabase -AdministrationContentDatabaseName "SomeDBName"
Command than asked me about all other missing info
Waited for the command to finish (few minutes)
And it succeeded
FINALLY!
Rerun psconfigui and finished configuration
Successfully launched SPF Admin Web.
clap clap clap