I have recently installed Installshield LE on my local PC for vs2010, built a package and now wanting it to be built on our build server. I have also installed it on our build server.
I am getting the error:
error : -7159: The product license has expired or has not yet been initialized.
I have logged onto the build server, started vs and entered in my licence code. However, this has has not resolved the error.
I have read about the stand alone version but that appears to be only available for premium edition. Anyone have any ideas?
if you are using the 2012 Spring edition of Installshield LE run the license activator on the build server at :
C:\Program Files (x86)\InstallShield\2012SpringLE\System\TSConfig.exe
The location may be different for other versions of Installshield LE.
You should be able to use the same activation code they sent you when you signed up for the Installshield LE, according to the license it allows for installation on more than one machine for automated build purposes.
InstallShield has online activation. You'll need to request multiple license keys and activate them on different machines.
Ran into this issue on our TeamCity build server. Initially I was able to run TSConfig.exe as the build server user and that worked. After a disaster recovery exercise, however, TeamCity reported the license was expired again, but running TSConfig.exe didn't do the trick.
I ended up launching VS 2015 as the build server user and opened a new InstallShield project. Instead of informing me the license was expired it said the license was corrupted and needed to be repaired. It performed the repair and I'm back on track.
I didn't know it was an option until after, but TSConfig /repair likely would have done the trick without opening Visual Studio.
Related
I am very new to Jenkins and sort of new to build .net application, but the guy left team so I have been assigned to do this. I have read tons of articles online about setting up Jenkins master, but little about slave configuration. The guy created a new slave and connect with Jenkins master successfully before he left. And he told me that slave is responsible for 1) downloading source code from TFS server and 2) building them.
now my issue is what do I need to install in the slave machine( windows system) to be able to perform that two tasks?
1) for downloading source code, do I need to install TFS client on slave ?
2) for building source code, do I need to install MSbuild or entire Visual studio ?
Thank you very much !
Assuming you installed a recent version of the Team Foundation Server Plugin, then no TFS Client is required (see https://github.com/jenkinsci/tfs-plugin#400-and-later-new).
Depending on what you are building, installing Visual Studio maybe required or not. In my experience, only a limited set of project types build with just MSBuild and without Visual Studio. There are hacks or supported tips but they work only in specific cases: YMMV.
The new Build Tools for Visual Studio 2017 RC are making this requirement a thing of the past: if you can migrate your code to Visual Studio 2017 you will be able to use them.
I am trying to build a project with build server and it keeps giving me the following error:
C:\Program Files (x86)\MSBuild\InstallShield\2013Limited\InstallShield.targets (108): -7159: The product license has expired or has not yet been initialized.
I have added the account used by Build in the build collection administrator group and project collection administrator group. I also activated installshield both through Visual Studio (creating new setup project) and then going in this location
c$\Program Files (x86)\InstallShield\2013LE\System\TSConfig.exe
I have VS 2010 (Shell), VS 2012 and VS2013 installed.
I have also added this user in the administrator group on that server. I have restarted the build server multiple times. I am not sure what else to try. Could anyone please help
Be ensure that the BuildService is not running with a local account such as "NT_AUTHORITY\Network Service". If so, please change it with a domain account and add the user account to the administrator group. Restart TFS build server machine, and re-queue the build.
In addition, please also have a check on this blog for the details on how to work with Installshield with TFS build:
http://blogs.msdn.com/b/girishp/archive/2014/03/04/installshield-and-team-build-on-tfs.aspx
The procedure for unattended configuration is well defined (Unattended Install of TFS 2012), while the setup part is obscure at best. The only known command is
tfs_server.exe /quiet
but there is no way to specify a different installation folder.
I have tens of build servers to upgrade from 2012.4 to 2013, and need to automate the process.
Got this response on Visual Studio official forum.
For the specify different installation folder in unattended installation scenario, please submit it to User Voice site at: http://visualstudio.uservoice.com/forums/121579-visual-studio. Microsoft engineers will evaluate them seriously.
In other words, it is not possible with current installer, i.e. TFS 2013.
Recently moved project to tfs preview and having trouble with software licenses installed on local dev boxes building correctly but on on tfs preview.
TFS fails the build saying it can't access registry due to those dll's that require installation. When removing the license contents from the .licx file tfs builds ok but the resulting drop and install issues a warning due to the license not being imbedded in the .exe.
Is there a way to install 3rd party licenses on tfs preview or is there another work around I am missing?
I'm going to assume you're using the hosted build controller. If so, you can't install software on those machines as they use standard base images and are reset after each build.
Any builds where you want/need custom software installed are best done using your own build server, either with an on premise machine or an IAAS VM in Azure.
For reference the software included on the hosted build servers is listed here.
We recently moved to Team Foundation Server 2008 from Source Safe. We are setting up some automated builds and have run into some issues with the publish of click once apps that seem to require additional installs on the build server.
I've seen posts that indicate that the Visual Studio IDE needs to be installed. I've also seen posts that say that installing the .Net Framework SDK would fix the issue. We don't want to install more than we need on the build server, but we also don't want to have to make multiple requests to our server team to install different pieces at different times. So, I'd like to know what most teams end up installing.
If it's important, we don't have a dedicated build server at this point. We are a small team (6 devs, all local). Builds are happening on our main TFS box, the SQL Server piece is the only part that is on a separate server.
If you are just compiling applications in with Team Foundation Build, then the .NET Framework will do - however as soon as you start wanting to do anything more advanced (such as running unit tests and having their results published into TFS) then you will need to bite the bullet and install a Visual Studio Team Edition on your build server. I usually just install a copy of Team Suite on the build server so that people who are licensed to use the various features can have those features run as part of any automated build.
Having to have it installed on your server is not ideal, but gives you the best experience at the present time.
Regarding using your TFS server as your build server, this is not recommended for larger teams because builds tend to be pretty CPU and IO intensive beasts - however for a small team such as yours and assuming that you don't have too many build definitions that could run at once you should be able to get away with it.
According to this, Visual Studio shouldn't be required--just the .NET Framework. One other note to consider from the link is that they recommend against builds happening on the TFS box.
Yes, I installed VS on the build server. I followed their manual for setting up TFS.