I'm in the intitial stages of setting up our new production VM. Kentico 9 has been installed, but when i apply the same hotfix version we have in development i get this. I'm RDV'd into the VM while attempting this.
Our infrastructure team set the VM up, and did the base install, and said the matched our DEV, QA, and UAT environments, and we're running on Windows Server 2012 R2.
Try to apply hotfix manually.
1) download hotfix setup from http://devnet.kentico.com/download/hotfixes
2) check that hotfix_x_y.exe was downloaded correctly (right-click on exe -> Properties -> Digital Signatures -> select signer and click "Details" - "This digital signature is OK")
3) start hotfix_x_y.exe and follow installation wizard (next, next...), in hotfix utility browse to your instance, next, next...
Try to run hotfix as remote installation?
Are you logged into your VM with RDP when you are doing this or doing it remotely from another machine? If remotely, then the answer above might help, but overall I would try re-downloading the hotfix and try again as it appears the hotfix package might of been corrupted during the download process.
One possible cause is if your infrastructure team has the traffic throttled or majorly firewalled on that machine. If so, sometimes it can cause downloads to miss packets and become corrupted. If it does not work again, try downloading to another system and then move to that one and see if that helps.
Related
I'm trying to use Packer form Hashicorp to create VMs. The idea is that I can create Windows 10 VMs for for each of my assignments, and run those VMs on my "main" Windows 10. I have access to Hyper-V, and as of late 2016, Packer supports that too.
Grabbing several files from Matt Wrock's Github repository, I have created a json file, an Autounattend and some scripts. When running Packer, I ended up with an error saying "Error getting WinRM host: No ip address". This had gone on for 5+ hours, so something was not going right. Interestingly, the Hyper-V Manger said that the VM was there, and I could even log in. Then I noticed that none of install scripts had been executed. For instance, in my Autounattend I execute Matt's boxstarter.ps1 script to install Boxstarter, but Boxstarter has not been installed.
To get a better visual on the process, I changed the Autounattend.xml to have all WillShowUI properties set to true. Nothing appears. To me this seems like Windows 10 is not booted. Any idea how I can check this? Also, from a different Github repository, I found in a json file for Windows Server 2013 the "boot_command" with value aaa. Without having any idea whether this applies to Windows 10 as well, I put that in my json file too. Maybe this boot command is wrong?
Alternatively, is there anyone out there having a public repository which I can use to create Windows 10 VMs that will run on Hyper-V on a Windows 10 machine?
Got some good news :) You don't need to build Packer from source for the Hyper-V provisioner. It was merged in at version 0.12.1 so if you have the latest you're good to go.
Here are some samples that I used when testing it for version 0.12.1+:
https://github.com/StefanScherer/packer-windows - Samples for Windows 10 & Windows Server 2016 set up with Docker & Windows containers
Ubuntu 16.04, hyperv-iso, generation 2 (UEFI) https://github.com/taliesins/packer-baseboxes/blob/master/hyperv-ubuntu-16.04.json
Feel free to ping me on GitHub (#patricklang) with issues in any of those repos.
There is not enough details to tell what's wrong.
Try using taliesins basebox - Windows 10, he is the main author of the Hyper-V support in Packer and I expect his examples to work.
When I try and deploy to my AI into a local liberty Eclipse informs me that I don't have servlet 3.0 installed.
My liberty installation is:-
Launching server1 (WebSphere Application Server 8.5.5.6/wlp-1.0.9.cl50620150610-
1749) on Java HotSpot(TM) 64-Bit Server VM, version 1.8.0_45-b15 (en_GB)
and it contains servlet 3.1
Even after installing the servlet 3.0 feature, it still says I need to install the feature
Here's some troubleshooting suggestions specific to your scenario.
If you're having issues with your own Liberty install, you can try using the one that ships with the Code Rally install (it's automatically included when you install using the Installation Manager install). You can find it under the Code Rally install dir, for example, on my Windows machine the Liberty install dir is:
C:\Program Files\IBM\CodeRally\wlp
As of July 2015, the Code Rally 1.4 install includes the Liberty 2015.5.0.0 beta, which does includes the servlet-3.0 feature by default.
I would also suggest creating a new workspace for Code Rally, rather than reusing an old workspace. This way you can ensure that there are not any old servers/runtimes defined (either Servers in the Servers view, or Runtimes defined under Preferences > Server > Runtime Environments). Code Rally should work with an existing workspace, but using a new workspace helps rule out these types of issues.
Ensure that you have the correct Liberty server defined in the Servers view, such that the 'WebSphere Application Server Liberty Profile at localhost' entry should be the only one listed. Note that you may also see Web Preview Server in the Servers view list; it can't hurt to remove this.
Finally, Code Rally Agents have a target Liberty server defined in their vehicle info. Right click on your vehicle in the Vehicles tab, and select Edit. Ensure that the "Liberty Server:" combo box is pointing to the correct server.
Thank you Jonathan for your help. The extra step I needed to do, was delete the contents of the c:\users\bondj\user.coderally directory - and then reinstall.
I am trying to setup a new connection to TFS with VS2012. Early on I was able to add my TFS server and, using the Microsoft Git Provider, clone a copy of the remote repository from within Visual Studio. Later, as I was fiddling with things in Team Explorer trying to find the branch I wanted to use, something broke. My local repository remains, but my connection to the remote repository was somehow corrupted, as evidenced with this error:
TF31004: Unexpected error encountered while connecting to Team Foundation Server at http: //my.server.com:8080/tfs. Wait a few minutes and try again. If the problem persists, contact the server administrator ok help
Things I have tried to resolve this:
Wait and try again (as the error message suggested).
Restart Visual Studio.
Reboot my machine.
Reboot TFS server.
Use system restore to revert back before I installed msysgit and Microsoft Git Provider, or had attempted to connect to the TFS server.
Review the MSDN help for the error (see below).
Search Stack Overflow (found one other related issue but did not seem to apply).
Tried devenv /ResetSkipPkgs
Tried devenv /setup
Re-install Team Explorer for VS2012.
Clear IE cookies (per this post).
Clear TFS caches (per this post).
The help page offers these tidbits, but none of them seem likely given that I had, as I said, the connection working at one point:
The version of Team Foundation running on the local computer does not match the version running on the Team Foundation Server server {name}.
The server returned HTML content instead of XML content.
The required Web service on the server could not be found.
Any ideas would be appreciated!
I have had an exactly the same problem.
My solution was to clear all the credentials in the Windows Vault (Credential Manager residing in the Control Panel).
I have no idea why the credentials did get messed up.
I can't get an Umbraco installation set up completly. I have been running into the error:
Oops...the installer can't connect to the repository
Starter Kits could not be fetched from the repository as there was no
connection - which can occur if you are using a proxy server or
firewall with certain configurations, or if you are not currently
connected to the internet. Click Continue to complete the
installation then navigate to the Developer section of your Umbraco
installation where you will find the Starter Kits listed in the
Packages tree.
I have tried this via manual install, Web platform installer and WebMatrix.
When I tried this wie WebPI and manual I gave the IIS_IUSRS FULL ACCESS to the Umbraco folder and de C:\windows\temp folder to be on the safe side. Which has brought no effect.
I have also tried using the steps described here and on google.
Every option has been tested on my physcial windows 7 professional machine, as well as on my virtual Windows server 2008 R2 dev-environment with the actual Umbraco 6.0.5 build.
I am hoping you can provide me with a working solution
Kind Regards
This problem is probably caused due to the umbraco installer not being able to connect to the internet, it doesn't look like a file permission problem.
If you are behind a proxy or firewall, you could add a proxy to the web.config that will allow umbraco to connect to the repository.
<defaultProxy useDefaultCredentials="true" />
http://msdn.microsoft.com/en-us/library/kd3cf2ex.aspx
Setting the permissions for ISS_IUSRS should work, though I would use the "IIS APPPOOL\{application-pool-name}" user to set the permissions.
A ps script is available at the bottom of the following page: http://our.umbraco.org/wiki/install-and-setup/set-umbraco-folder-permissions-from-command-line
However, if you reached the point where the installer is asking to install a package, isn't the application already running?
What happens if you quit the process, and login to umbraco?
Our team is going to be developing against SharePoint using local VMs. Our VMs are not allowed to join the host domain. Additionally our host nics are prohibited from using Internet Connection Sharing. We have a requirement to source control all our development work using Team Foundation Server. Our TFS installation is using Kerebos for authentication.
To be able to use TFS for source control we were thinking we could share a folder between the host and VM, do our work on the VM, save to the shared folder and then do check ins and such from the host which will be able to authenticate against TFS.
I'm hoping there is a cleaner way to do this or someone with similar restrictions can provide some insight.
Note: I have successfully setup a similar mechanism using Tortoise SVN and Ankh SVN that works, but management will not budge on the TFS requirement. Not that I blame them either, the license is very expensive and they want to feel they are getting their money's worth. Therefore TFS has to be included in the answer.
Here's a solution that works perfectly for SharePoint 2007 development.
We run virtualised instances of Windows Server 2008 on our Windows XP machines at the project i'm on. We use Sun VirtualBox as the virtualisation software.
secondly, each VM is a standalone domain controller + sql server + reporting server + analysis server + sharepoint server and as such isn't joined to the main domain.
when opening up Visual Studio 2008 and connecting to TFS you don't need the machine/server to be connected to the domain as the VM NATs through the host machines network adapters - use a fully qualified address for your TFS and you shouldn't have any problems connecting to TFS from within the VM.
you may need to turn off integrated windows authentication (IE -> Tools -> Internet Options -> Advanced)...
We also run VS08 in the VM and not on the host..
Another thing is to use WSPBuilder to build your solutions and create the deployment scripts for you (or alternatively just set up an external tool/command from VS08 that runs the stsadm.exe -o deploysolution command)..you can deploy effortlessly to the VM and ensure that it runs fine - then just check in your code, set up build scripts that fires off WSPBuilder on the build server to build the solutions for you and deploy from there (or copy the WSP up to the server and run them there).
I think your solutions is as clean as it will get.. you could map a folder on your host machine and open the Visual Studio project straight from there within the VM. Saves copying. Committing will have to be from the host. Use of TFS features will be a bit awkward, you'll have to open VS on your host machine as well to connect commits to work items etc. Not exactly what the investment in TFS was for.
How come they've dished out the cash for TFS but are not willing to facilitate it? The VM's should really be in the domain.. or at least a trusted domain.
We run the same setup except we do have SVN and can commit directly from the VM. Workable :)
BTW, if you develop for SharePoint 2010 this gets better; it'll allow installation on non-server OS's so you can develop on your local machine (which I guess, is on the domain).
I generally use VS2008 running on the host with the SharePoint assemblies installed to the GAC of the host. I use build events/build targets with a shared folder and sysinternals to build directly to the SharePoint VM's bin/GAC folders. This way Visual Studio builds directly to the SharePoint server and you do not have to manage 2 installations (host and VM). I would also recommend installing VS2008 debugger as a service on the VM for easy debugging.
Hope this helps!