I created a Microsoft Word 2013 Automation process that opens a Microsoft Word template, replaces bookmarks with some texts and saves it as a PDF. It works fine on my local machine because I have Microsoft Word 2013 installed.
However, when this is deployed to the web server it does not work because Microsoft Word 2013 is not installed on it. As far as I know, Microsoft Word 2013 needs to be installed on the server in order for this to work. However, some here believe only select components are needed to be copied to the bin folder in order for it to work and Microsoft Word 2013 does not need to be installed.
Does anyone here know what those minimum components would be? The components I have so far are
Interop.Microsoft.Office.Interop.Word.dll,
office.dll
However it process returns the error message 'Cannot create ActiveX component.' (Since I don't have Visual Studios Installed on the WebServer I don't know which line is causing it).
Or am I correct and we would have to install MS Word 2013 in order for this to work?
In order to automate any Office application that application must be installed and licensed on the machine where the code is executing. No ifs, ands or buts. There is no such thing as "just some components needed".
All that said, running and automating Office applications server-side is not supported and can cause problems (see https://support.microsoft.com/en-us/help/257757/considerations-for-server-side-automation-of-office). For this reason, the Office Open XML file formats were developed, so that Office documents can be generated and manipulated in a server environment.
Related
Is there any hidden tool from MS we can use for BizTalk application migration prior to load solution into VS2015 ? I need some information about what are characteristic we may need to change specially BizTalk.btproj solution to load all project file etc., wonder to know easy approach migrating BizTalk application solution if any.
As various blogs posts and MSDN threads you needed to have an intermediate Development BizTalk environment (BizTalk 2010) and then upgrading it to the later version like BizTalk 2013/R2 and up.
You can download the developer edition here and install the SDK so you can open it in Visual Studio.
The only other way to migrate is to create new BizTalk Projects in Visual Studio 2015 / BizTalk 2016 environment, and then copying the artefacts such as Schemas, maps and re-creating any Orchestrations.
In either case you will have to do extensive retesting as there are certain changes such as the XSLT compiled transform that may cause you issues
No need for a hidden tool. Visual Studio is the tool.
When you open a downlevel Solution, Visual Studio will attempt to update any project and provide a report of what was automatically updated and what could not be updated, requiring manual intervention.
You can do this on a copy of you Solution to get a preview of any work necessary for the real upgrade.
Coming from BizTalk Server 2006, you will need an intermediate version to eventually target BizTalk Server 2016. You can download BizTalk Server 2010 from MSDN. All you need to install is the SDK. You don't need to setup/configure full BizTalk Server.
I Googled for this error, and found many links on SAP as well as StackOverflow, but none of these seem to answer my specific problem.
I have developed a web application using VS 2010, ASP.NET 4.0 and Crystal Reports. I have deployed this application on Windows 2003 R2, Enterprise Edition, SP 2, 32-bit, on IIS 6. I have installed Crystal Report Distributable 32-bit, Version - 13.0.8.1216, on the server. The data source is Oracle 11g XE, on a separate server
When I browse the report from the browser (IE, FF), the reports are visible in the viewer for some time. The problem is after some time, I start getting the following error:
Unsupported Operation. A document processed by the JRC engine cannot be opened in the C++ stack
As suggested in many solutions, i have checked the availability of the report files(.rpt) and they are available on \Reports folder. The aspnet_client folder is also available which has a crystalreportviewer13 folder inside aspnet_client\system_web\4_0_30319
I have no clue, why it will work perfectly fine initially, but later it will start giving this error. I thinks it is probably when I try to access the application concurrently from 3-4 different machines. I replicated this behaviour once.
Now if restart the server machine, it again works fine. Restarting just IIS does not help
Would appreciate any help, as I am at my wits end to find a solution. I will readily provide any other information if required.
issue: populating values for word document is not happening.object reference error in production server.
development server( working fine)
i am trying to populate the values for the word document using c#.am using microsoft.office.interop.word dll (version 12.0 related to word 2007) as a reference in my project. in my development server office 2007 is installed. am able to populate the values and save the document properly without any error.
Production Environment
getting object reference error. the one difference i see in this server is microsoft word 2010 is installed. i tried my level best but no luck.
*is this because word 2010 is installed in the production server?
*when i hosted the application in the other production server where word 2007 is installed.the application is working fine.
That could be the issue, it looks like Office 2010 uses Version 14 of the dlls:
http://www.microsoft.com/en-us/download/details.aspx?id=3508
Maybe try to use the 14 version in your dev server and see if that works, if so should be ok with production as well. otherwise see if the 2007 dll was copied into you bin, if not try to drop the 2007 version (v 12) into you application's bin and see if that works, could be the production application can't locate the dll in your bin and is then looking in the GAC, GAC would have 2010 version installed. If it's in your bin it might use that one first.
I know this is a strange situation, but consider a situation where two programmers are working on one project. One programmer is working on a database driven website in ASP.NET in Visual Studio 2012, while other programmer is working on Visual Studio 2008 on another part of the same database driven ASP.NET website.
What in your opinion is the best way to integrate the two codes?
PS: Downvoters please explain in comments, before downvoting. :-)
Make the second developer update his VS copy to 2012. If you are working with two disparate versions of VS, you will very simply be unable to have either developer work on any part of the codebase that was built with (or upgraded to) the other version.
Once everyone's working on the same platform, and thus can load and build the same solution, project and source code files without error, "integrating" the two codebases becomes rather trivial. Of course, the conversion process may not be so trivial.
My first step would be to ensure that a reliable backup of the entire codebase has been taken; you can copy the flat files to a file store, or more reliably you can use a centralized VCS like Subversion to make sure a single authoritative copy of the codebase as-is exists and can be easily retrieved. Then, while the 2008 dev is updating his machine to 2012, have the 2012 developer pull the whole codebase and load whatever solution the 2008 dev had been working in, and run through the conversion wizard. This wizard will update the XML behind the project and solution files to support features of the new IDE version.
If you absolutely positively cannot get both devs onto the same IDE version, there's still hope. Have the 2012 developer open a new solution file in his copy, and pull in the 2008 projects. If VS asks to convert them, you're SOL; the other dev will HAVE to upgrade, or the 2012 dev will have to revert. But, if the IDE doesn't complain, the 2012 dev can save the new solution under a different name and work with the projects and their source code using that solution file, while the 2008 dev can continue to use the original one. Understand that as long as this state of affairs continues, the 2012 dev cannot use any features of C# 4.0/4.5, such as dynamic types, covariance/contravariance keywords, optional parameters/named arguments, async/await keywords, etc cannot be used in any source code that must remain usable by the 2008 dev. Language-wise, the 2012 developer is limited to C# 3.0, and the .NET Framework 3.5. This does not solve the problem of the 2008 dev not having access to code written from scratch by the 2012 dev in projects created by that IDE; he simply must upgrade to work in these parts of the codebase.
We recently upgraded our biztalk server 2006R2 to SP1. The problem is that we're having some small issues now, for example the administration console crashes when I browse for a folder if I want to make a file send/receive port.
Any idea what might cause this problem?
I'm having no problems when I browse for a folder with our normal explorer and then copy paste its address into the biztalk folder browser.
Make sure you update towards the latest CU for your service pack.
For BizTalk 2006 R2 with SP1, this is CU4.
See http://support.microsoft.com/kb/2682056 for more information on CU4 for BizTalk 2006 SP1.
If this still does not help, there is a temporary workaround to export/import bindings of existing receive locations/send ports with a FILE adapter. This allows you to still create the ports/locations you need and unblocks the situation.
In any case, if the problem persists, you might want to check with Microsoft about the issue.
That is in case your license includes the extended support option which lasts until 12 July 2016.
If you don't have extended support, the support ended on July 11th 2011 I'm afraid...