We have installed two instance of the MS report server (2012) on the same machine for two instances of the same application.
There are some reports that have created using OfficeWriter. For them to work, we need to install office writer.
When installing office writer, we can specify only one report server instance during the installation wizard (if we have multiple instances if RS). But I need to integrate office writer with both RS instances.
Any help would be really appreciated.
Thanks you!
Wijitha
The installer will only setup one instance at a time as you noticed.
However you can do a manual install for the second instance.
Checkout the installation guides at http://wiki.softartisans.com/display/OW9/Installation
or jump straight to the 2012 installation information at http://wiki.softartisans.com/display/OW9/Installing+for+SSRS+2012
Related
I have followed the following guide to try and create an MSI to deploy a VSTO add in for Outlook. https://msdn.microsoft.com/en-us/library/cc442767.aspx?f=255&MSPPError=-2147217396
I have carefully followed this guide on two occasions, ensuring in particular that I placed the registry keys in every place I can imagine they would be need to be in order to be detected.
The MSI is created successfully and installs successfully also, the problem is that when I run Outlook after the MSI is installed, Outlook does not recognize the Add In and load it.
If I use Click once to install the add in it is recognized by outlook without any issue. The problem with that is that we want to install the application silently using SCCM and clickonce cannot be deployed silently.
What could possibly be going wrong?
The issue in this case, was that the guides code for installing the prerequisite "Visual Studio 2010 Tools for Office Runtime" did not work properly and the prerequisite was not installed.
Any user that needs to run the add in will need the VSTO tools from this link installed
https://www.microsoft.com/en-GB/download/details.aspx?id=48217
Hopefully this will be of some help to anyone else
EDIT: For anyone in the UK - The registry entry "LoadBehavior" must be spelled exactly as it appears here. I used the UK spelling "LoadBehaviour" and it was the sole reason my install was not successful. I was held back for several days due to this.
I have a SQL server database on my customer's server which is accessed by aprox 20 users through a winforms client application installed on individual machines.
I was thinking of using Crystal Reports to produce management reports etc and embedding this into my winforms application. However would this mean that crystal reports needs to be installed on every individual client machine, or just on the server?
For winforms you will need to install the Crystal Reports Runtime on the client machines so that they can view and interact with your Reports. You should be able to get the Runtime (msi) from SAP's website or sometimes it will come with your download when you purchase/download the software online (that was the case for me when I got the dev version for 2012).
SAP Crystal Reports, developer version for Microsoft Visual Studio - 2012 Now Available for Download
If that is not your version just Google for your specifics and you should be able to find what what you need.
BukHix is right, you need to install the runtime on each machine.
If you don't want to do this you can consider implementing a report scheduler, which will run the reports on the server and will deliver them to the management as excel, pdf or any other applicable file type
I am running a VB6 with ActiveReports Standard v2 sp3. All of the sudden on one installation when creating a report the application shuts down. Eventually the system wants to report the error to Microsoft on actrpt2.dll Version 2.0.0.1252. If I copy the the clients database down on my machine it runs just fine. We have tried it on several machines. I have reinstalled the application. Reregistered the DLL. The client is using a terminal server running Server 2003. It is simply a columnar report.
I would have suspected a dependency issue for actrpt2.dll.
Check the dependency on your machine and do the same on the clients machine that this is failing.
For details on checking dependency
May be it is best to contact Grape City folks their forum is pretty active.
Update: if you are using win32 version of AR (not the dot net version of active reports).
Try dependency walker to check dependancy
We have a large application that has been developed over 15 years and in installed in 200+ client locations. The application currently consists of an Access database and a bunch of executable and report files located on a network share. A Setup.EXE file is run on each client machine (dlls are installed on the client) and then the client machines run the executables directly from the network share. During our upgrade procedure the new executable and report files are copied to the network share and that way each client gets the update immediately.
Our current installation program is very old and, among other things, it doesn't handle x64 so we are in the process of moving to a new deployment tool. At the same time we are migrating client Access databases to SQL Server. I am having difficulty finding a deployment tool to do what we require. Specifically we need the install/upgrade file to do the following:
It must be able to be run from a client machine on a network and copy the new executable and report files to the network share. That share could be a Linux box or a dumb storage device.
Accept a password before running the installation
Allow the user to select the network share as the location to copy the executables
It must NOT add anything to the client machine from where the package is run (Add/Remove Programs, registry, etc.)
Connect to a SQL Server database and run a script
The install/upgrade must be contained in a single, standalone .msi or .exe file. (no dependencies on dlls or frameworks other than those that come with Windows XP)
The file must be able to be run in one simple step. It is the end user that runs the upgrade without our support and without involvement from IT.
It looks like the closest thing to what I need is WiX but the problem there is that whenever the .msi file is run from a client, the client machine thinks that a program is being installed so it allows the client machine to uninstall the product, which is not acceptable.
If the product were written today it would certainly be architected differently but it currently is what it is and we can’t change that. Any help here would be greatly appreciated!
WiX is just a toolset built on top of Windows Installer technology. It makes many things easier and simpler as well as hides lots of Windows Installer weird features... But, it is still limited by Windows Installer, its underlying technology.
Your list of requirements made me think that Windows Installer is not the right technology to choose. I would assume that you'll spend more time on workarounds, than on functional code... But I have no experience with other installation technologies, so I'll leave those recommendations to others.
I'm trying to test the DB2 adapter for BizTalk 2006 (not R2).
While trying to configure an instance in an application, I get an error stating:
DB2 Transport Component is not registered correctly
The enivronment is 2 BizTalk servers sharing a messagebox.
The DB2 adapter works fine on the first server. It is the second server I am having problems with.
I've exported the .msi files from the first server, then installed them onto the second server and imported them into BizTalk. All of the other adapters that I'm using work fine on both servers.
Google searches don't bring up a whole lot regarding troubleshooting the BizTalk DB2 adapter.
Further troubleshooting has shown that MS BizTalk Adapters for Host Systems is installed on both machines. However, it was only configured on the machine that is giving me the issue.
I've unconfigured it, but that still has not helped.
I've double checked tht version numbers of the .dll's for the DB2 adapter are the same on both servers, and made sure that they are installed in the GAC.
None of this has helped.
Has anyone run into an issue like this before, or point me in the direction of where to look for BizTalk DB2 adapter troubleshooting guidence?
When the "registered" word appears, I think about the registration of COM components, not the installation of .NET assemblies. The underlying driver the DB2 adapter uses is the Microsoft ODBC Driver for DB2. You may want to check if your ODBC DSN control panel shows up that particular driver for you to configure a DSN.
I'd recommend a reinstallation for the Adapter pack for Host Systems.