I have windows service developed by VS.Net 2012 , Windows 7 32 bit and installshield 2012 LE for setup.
In the development machine everything going well ,installation completed and service working fine .
When upload it to the server (windows server 2008 R2 SP1 64bit) during the installation , installation stopped and rolled back because of error 1001 .
Advise Please
You're in a rough spot. Error 1001 comes from an InstallerClass, which uses a very fragile technology. The error 1001 has many different possible sources, ranging from an unhandled exception to what feels like the phase of the moon. However InstallShield LE doesn't really support installing services any other way.
The best advice I can offer is to use Windows Installer support for installing services. But in order to do that you will have to use a different installation creator. If you want to stick with InstallShield, the Professional edition has a view in which you can configure the Windows Installer support for services.
You can use Windows Installer XML (WiX) to author a merge module that installs a windows service and then consume that merge module in a InstallShield LE project. See:
Augmenting InstallShield using Windows Installer XML - Windows Services
Installshield LE 2012 doesn't support 64bit.
There is a new beta available of Installshield LE that is supposed to add this feature: http://blogs.msdn.com/b/visualstudio/archive/2013/08/15/what-s-new-in-visual-studio-2013-and-installshield-limited-edition.aspx
It's also supposed to support the proper Windows Installer for installing services now, even in the LE (via "3 Configure the Target System" -> Services"). However I've not been able to get that bit working yet - maybe there's some magic setting I've missed.
You could try using this version - let me know if you have any luck getting it working via the proper windows installer services!
Related
I need to install Microsoft XML Parser 4.0 from Inno Setup.
How can that be done?
I was given a task to embed MSXML in the installer of ours. It's a proprietary piece of software our company makes (for accounting, it uses XML to store and exchange data). Apart from modern systems It's also going to be installed on many old systems using Windows XP.
I'm using Inno Setup 6.1.2.
Also, is there a quiet mode of installation as an option? So the users won't have to click anything and just be notified that MSXML was installed?
Did you Google this?
https://silent-install.net/software/microsoft/msxml_parser/4.30.2107.0
Eg:
msxml.msi /qn /L* "%temp%\XML Parser 4.30.2107.0.log" /norestart ALLUSERS=2
If you look at the Msiexec (command-line options) it does say the qn switch will display no user interface.
Somewhat of an aside, the requirement of installing both on XP and on 'modern' systems may create a conflict that you or your installer will have to resolve.
From Installing and Redistributing MSXML 4.0:
System Requirements
MSXML 4.0 is supported in Windows Server 2008 R2, Windows 7, Windows
Server 2008, Windows Vista Windows Server 2003, Windows XP, and
Windows 2000
From Installing and Redistributing MSXML 6.0:
System Requirements
MSXML 6.0 is supported in Windows Vista; Windows 2000 Service Pack 4;
Windows Server 2003; Windows Server 2003 Service Pack 1; Windows XP
Service Pack 1; Windows XP Service Pack 2.
MSXML 6.0 is preinstalled with Windows Vista. For earlier versions of
Windows, you can install MSXML 6.0 as a separate download.
So you can only use MSXML4 below Vista. And with Vista and above you should be able to reply on MSXML6 already existing.
Your installer could perform an OS version check (alt ref) and then only install MSXML4 if needed. Or you might be able to detect specifically if MSXML6 is installed and then install MSXML4 only if not (assuming therefore its an older system).
But I would test your application (if you haven't already) and see if it will run against MSXML6; it may, without changes. If so then I would forget MSXML4 and include MSXML6 in the installer instead (*). That way your installer could just run it 100% of the time, and expect that on Vista and up it would just do nothing. Your installer would therefore be simpler plus you would be taking advantage of "MSXML 6.0 provides security and performance improvements over earlier MSXML versions." noted here.
(*) Unless you have to run on WinXP pre-SP1?
I am trying to install Service Bus 1.0 on my developer machine. When i am searching for "Service Bus 1.0" in the web platform installer 4.5, it is not able to find it.
I downloaded .exe file manually from http://go.microsoft.com/fwlink/?LinkID=252361. When the setup runs, it gives me an error message in Web Platform Installer that "Microsoft web platform installer couldn't find the product you tried to install. Either the link you clicked is incorrect or you may be overriding you feed with different feed."
I checked my feed and it is set to "default".
My operating system is windows 7 SP1 Enterprise Edition.
VS 2010 and V2012 installed. I also have SQL Server 2008 R2 Express
Any idea what is causing this problem?
It turned out that my OS is 32 bit and it requires 64 bit OS.
Where I currently work we are using TFS2010 and already have a build controller set up on a Windows Server 2008 R2 box. We are contemplating upgrading our TFS2010 instance to TFS2012, but in the meantime we are about to start development on a new product. The project team have established that it would be a good idea to create a new build server for this new product for the following reasons:
Our current products are .NET 3.5 solutions
The new product will be a .NET 4.5 WPF solution
Preference to install third-party components and tools required by the build of the new product in an environment separate to our current build server so as not affect the building and release of service packs and hot-fixes of existing products.
Can a TFS2010 build controller be installed on a Windows Server 2012 machine, and what are the things that I need to look out for? Or is it more advisable to install a new controller on another Windows Server 2008 R2 machine, and when we have upgraded to TFS2012 to upgrade the controller on the new server, and perhaps upgrade the server to Windows Server 2012 as well?
Installing TFS 2010 build controller in Windows Server 2012 was pretty simple. Note that .NET 3.5 needs to be installed on the build server before installing TFS 2010 build controllers.
Also if building .NET 4.5 applications, and are not keen on installing Visual Studio 2012 on a build server, the Windows 8 SDK should be installed.
Furthermore I would recommend installing MSBuild Community Tasks (https://code.google.com/p/msbuildtasks/downloads/detail?name=MSBuild.Community.Tasks.v1.4.0.56.msi&can=2&q=) for extra MSBuild functionality. This is especially beneficial for applying a version number to your assemblies by obtaining build number values from whatever automated build server technology you are using and supplying these values as parameters to MSBuild. The following article demonstrates this using the Bamboo CI server product: http://itrathnasekara.blogspot.com.au/2011/05/setting-assembly-version-automatically.html.
Possible or not?
I know Sharepoint 2010 Server won't even run on a client side of Vista/Windows 7 64-bit, forget about Windows XP 32-bit.
But if I can install and use Visual Studio 2010 on Windows XP just fine, shouldn't Sharepoint development tools also work on Windows XP 32-bit?
The thing is I have a very old laptop (from 2005) that doesn't even support 64-bit architecture so I am stuck with WinXP 32bit.
If there is any way at all of (Remote?) Sharepoint development on Windows XP 32-bit with VS2010 please let me know.
Most of what the developer tools offer you make two assumptions:
You are running on a 64-bit architecture
SharePoint is installed side-by-side with Visual Studio
Running on a 32-bit XP machine breaks these assumptions. Many of the built-in Visual Studio productivity aids, such as the deploy and retract commands, will fail. I couldn't even create a project using the SharePoint 2010 project template under similar conditions.
You might make some headway by using regular class library or web application projects, copying SharePoint .dll's from a server's GAC (for use as references) and by manually creating your .ddl and .wsp files using MakeCab (as I did with 2007, with a little help from PowerShell); however, it sounds excruciating compared to running on Vista SP2 X64 or Windows 7 X64 with SharePoint installed.
As per the above answer, VS 2010 SharePoint projects require a local installation of SharePoint. You can use external tools for doing your development, such as WSPBuilder, but I do not recommend this approach. You are best sticking to the MS tools.
Your options are:
Upgrade to Windows 7 x64 or Server 2008 R2
Run VMWare Server (free) which should enable you to run a 64-bit VM on a 32-bit host (I think? Not sure about this assumption actually), and create a VM with Win7 x64 or Win 2008 R2 for SP development.
You can use Win7 64bit as your dev environment
http://msdn.microsoft.com/en-us/library/ee554869.aspx
I've been struggling for some time now to be able to use the built-in functions in Visual Studio 2008 to handle *.mdf database files with SQL Server 2008 Express. I'm running on an x64-based system, and I've read that there is a known problem with this setup, but the hotfix has not solved my problems.
Basically, what happens is that when I try to add a new *.mdf file to the App_Data folder of a project, I get an error message saying:
Connections to SQL Server files (*.mdf) require SQL Server Express 2005 to
function properly. Please verify the installation of the component or download
from the URL: http://go.microsoft.com/fwlink/?LinkId=49251
My (unsuccessful) steps to solve this:
Uninstall all possible associated programs to Visual Studio, SQL Server or .NET Framework (which left .NET 2.0 Compact Framework and .NET 3.5 Compact Framework, and nothing else .NET related, installed).
Reboot.
Install .NET 3.5 SP1, SQL Server 2008 Express and SQL Server Management Studio 2008 Express via the Web Platform Installer 2.0 (Beta).
Reboot.
Install Visual Studio 2008 Professional from disc.
Reboot.
Install Visual Studio 2008 Service Pack 1.
Reboot.
Install hotfix.
Reboot.
Start VS, create new Web site and try to add database. Still get the error message...
When I look in the Help/About dialog, the hotfix shows up among applied updates. I have also checked and double-checked that the SQL Server instance name is correctly set in Visual Studio (I copy-pasted the instance name from the login screen in SSMS).
Why does the hotfix not solve my problems? Am I doing things in the wrong order, or do I have the wrong software versions somewhere?
According to the KB article, the problem is that Visual Studio doesn't correctly detect "some registry keys" - but nothing is said about which keys. Does anyone know how to fix this manually?
Oh, and yes - I've seen this post. I know I could just "downgrade" to the x86 version of SQL Server, but I really want to make this work with the x64 version (if nothing else, just because it's supposed to work...), so that solution doesn't really solve my problems. Please don't close this as a duplicate.
I had this same error, VS 2008 SP 1 on Vista Ultimate 64 bit with SQL 2008 Express 64 bit. Downloaded the hotfix and rebooted, started up SQLEXPRESS and still got the error.
Then I changed my "SQL Server Instance Name" (under VS 2008 -> Tools -> Options -> Data Connections), which was blank, to "SQLEXPRESS" (versus ".\SQLEXPRESS", which is what I use in my login screen under SSMS.) and now it works like a charm!
Dave
Try changing the user on which the SQL Server Express is running. This can be changed in Services managment (press Win+R, type in services.msc). Choose SQL Server Express, right click -> Properties. 'Log On' tab and select: 'Local System account', tick the 'Allow service to interact with desktop' - this is what worked for me.
I'm not sure I ever solved this, but I've now moved over to Visual Studio 2010 (RC at the moment, but I'll get the full version when it's availabel) and everything works seemlessly.