There is error about certificates when I ran the installation scripts.
Install-SitecoreConfiguration : No registration found for extension 'NewRootCertificate' of type 'Task'.
At C:\sc9_install\sc9_install.ps1:17 char:1
Install-SitecoreConfiguration #certParams -Verbose
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Install-SitecoreConfiguration
Sometimes, if you have tried the installation script more than once, you can have some undesired behavior. You are possibly trying to go forward with the wrong certificates. Also, some of these services were actually created on previous installation attempts.
Here is what I think should help you get through.
Clean your workspace
Remove your databases that are related to the installation if exists.
Remove your certificates (using certlm -> you can type in your windows search bar "cert" and then you should be able to pick "Manage computer Certificate".
On the left sidebar, Click on Personal > Certificates.
Remove your installation-related certificates
nameOfYourInstallation.identityserver
nameOfYourInstallation.sc
nameOfYourInstallation.xconnect
Open your Windows Services Manager (you can type in your windows search bar "services" and select the services app)
You should be able to see those services :
Sitecore Marketing Automation Engine - nameOfYourInstallation(might be one of your previous install)
Sitecore Processing Engine - nameOfYourInstallation
Sitecore XConnect Search Indexer - nameOfYourInstallation.
Write those down. Keep your service app open.
Using NSSM (probably installed already from some of your previous installed, if not, can use chocolatey ( https://chocolatey.org/packages/NSSM ) remove those services.
in a cmd : nssm remove serviceName
Note that you can remove them by right clicking etc. I just prefer the nssm way.
When its done, restart your computer (some services and in a state of removal, that needs a restart to be completely removed)
Try to install with SIA again.
Related
We are migrating some code from CF 10 to CF 2016 virtual machines that needs to connect to a couple Access databases. I installed the necessary drivers and setup odbc datasources in Windows but have found that our CF 2016 VM was setup without the ODBC service and I have not been able to find a clear way to add it.
When I go to add/remove programs the only option is to uninstall CF and when I run a CF 2016 installer it will not let me go through the "Server configuration" process because an existing install already exists. Is there a standard approach for adding sub-components to a CF server that were not chosen on first install?
Looks like I found my answer after digging around for a while. The migration wizard needs to be run again to add the ODBC service but there could be various complications with this depending on permissions and other factors. I was not able to get this to work after a brief period of time so I am just going to wrap up my transition to using python for our limited Access needs but I do believe this to be the answer.
https://community.adobe.com/t5/ColdFusion/ColdFusion-11-ODBC-service/td-p/6207226
Here are the basic steps. See link above for various troubleshooting info from Charlie Arehart and others.
Navigate to adminconfig.xml at C:\ColdFusion11\cfusion\lib\ and open it with text editor (say notepad).
Change the value from “false” to “true” in runmigrationwizard
Change the value from “false” to “true” in odbc
Save the file and restart ColdFusion Service.
After restarting the service, access the cf admin url and you will get the migration wizard. Follow the onscreen wizard to continue.
I came upon the answer by way of a thread about getting Access data sources setup in CF11 and CF2016 which Charlie Arehart contributed to and linked over to info about the ODBC service setup.
I have set up an elastic beanstalk deployment of Drupal to host a Drupal built website.
When I start up my ec2 instance, I go through the installation steps of setting up Drupal.
However, when the instance is Restarted, or Stopped, restarting the instance goes back to this page!
How can I configure the instance so that these installation steps do not need to be repeated even when the instance goes down. This is quite worrying as I am looking to host my website this way.
Any help on this issue would be greatly appreciated!
This step means that drupal can't find database or it can find it but installation is not done yet (required tables are not created). So if you pass installation and you see again this screen it can mean 2 things:
Your database configuration is lost, so drupal can't find DB.
DB configuration file is ok, but DB it self is lost so configuration must be done again.
So first check what is the problem in your case and then solve it. Probably since you are installing in instance, DB configuration is then recorded and then lost when your box expires. If so...find a way to make permanent change do config file (should be /sites/default/settings.php).
I am trying to install SIM version 13 rev 1404021 using Administrative priveleges
When i click on Grant button it give me error that " you dont have neccessary permission set".
Also i have given full permission to Network Service,IUSR, IIS_USR and network to the folder
C:\Inetpub\wwwroot
Kindly let me know whate else permission need to be given inorder to run sitecore instance manager succesfully.
It may be caused by bug in SIM that doesn't get actual SQL Server user account (LocalService or custom) and thinks that it is always NetworkService. So work around is to switch your SQL Server service from using LocalService or custom account to NetworkService.
Same context with Alen's answer, but in windows 10.
Use 'Local System account' and tick the 'Allow service to interact with desktop'.
Then, restart the service.
At this point, you don't need to reopen the SIM installation window. You can just click the Grant button and it would work.
Well, for me the issue was that the database user didn't have the dbcreator role so the wizard couldn't create databases in SQL Server.
Open SQL Server Management Studio
Expand Security > Logins
Double-click on the user to open the properties dialog
In Server Roles, check the dbcreator role
Press OK and enjoy
Source: http://sitecoreblog.patrickperrone.com/2015/04/a-simple-error.html
When you downloaded the SIM zip file from Marketplace, did you click "Properties" on the zip file and click the "Unblock" button before unzipping and running it?
I've found in the past that forgetting this step can be the cause of odd security related errors with applications.
I ran across a similar issue I had, but for me root issue was that the wwwroot folder was on a VM/Parallels and that folder was marked "compress" and "archive"
unset that for wwwroot and child items, and then SIM proceeded correctly.
I was trying to set up a Sitecore dev instance and I accidentally installed to the wrong path. It seemed like the easiest way to fix this was to delete the IIS instance, and remove the Sitecore DB's.
Unfortunately, I am now getting an error when I try to uninstall ("An error caused the Sitecore Installation Wizard to end prematurely"), and a "not a unique name" error when I try to install a new instance. What do I need to do to allow me to use the same instance name again?
So, #OptimizedQuery got me most of the way, until the Windows uninstaller stopped working. I then went into the registry and found the relevant entries here [HKEY_LOCAL_MACHINE\SOFTWARE\Sitecore CMS].
So, here is a list of steps.
Try the Sitecore installer and choose to remove the offending instance.
If that fails, manually remove it from IIS and delete the databases before using the uninstaller in the Programs and Features application.
If that fails, use regedit and delete the relevant children of [HKEY_LOCAL_MACHINE\SOFTWARE\Sitecore CMS]. Be sure to delete only the one with the matching InstanceName key.
Try uninstalling that Sitecore instance via the Windows Programs and Features dialog within the Control Panel.
#cwallenpoole the path is wrong. Sitecore is installed in a different location like the followings:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sitecore CMS]
So the steps look like the following to uninstall:
try to uninstall by using sitecore installer and choose the instance to uninstall
try to remove form Control Panel > Programs and Features and then choose the instance to remove or uninstall
if the above steps are failed, then go to the regristry and choose the path [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sitecore CMS] and then choose the instance to uninstall
Hope, it will work for most cases. if you find any more steps, please add those :) happy uninstalling!
We are using multiple vmware servers, that each host several vmware images/instances. Each department uses its own vmware server. The vmware instances are always accessed through the "VMWare infrastructure web access" web page from the console tab panel. The vmware servers are plain windows servers (nothing fancy).
Now it turns out that some of these vmware images are useful for multiple departments.
Of course we considered to copy these images, distributing them to all vmware servers, hosting the same image multiple times.
But we would in fact prefer to only host 1 copy of each instance. But still we would like to have all images accessible from 1 web page. Merging them to 1 server is of course impossible (performance-wise).
So, this got me wondering, perhaps there is a way to create hyperlinks within the vmware web access portal to vmware instances that are actually hosted on a different server. They would appear to be all on the same server but in fact they are distributed.
Does such thing exist, and how should it be configured ?
In mean time I found a reasonable solution for my problem.
The vmware-vmrc.exe can be called from the commandline with several parameters. For example with following parameters it will open the vmware session immediately without the need of specifying any credentials.
vmware-vmrc.exe -X -h hostname:8333 -u "username" -p "password" "[standard] ... .vmx"
Important: The "[standard] ... .vmx" value is not just a file name.
To know this value, you need to visit the webpage of your vmware
(e.g. https:// hostname:8333/ui/).
Next click the button "Configure VM" which will open a tab panel with configuration settings.
There you will find a setting called "Virtual Machine Configuration File". It often starts with the string "[standard]".
Next, it was really easy to write a little batch file that allows me to pick the desired vmware from a menu.