We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Cannot deploy .NET application with any Aspose DLL

Aspose.Total Product Family
#1

We publish our applications using the Publish feature of Visual Studio 2013.

The server to which we publish the applications was just upgraded to Windows Server 2008 R2 and the Front Page server extensions were installed.

We have approximately 10 applications, 2 of which use one or more Aspose DLLs. The eight applications that do not use Aspose all published to our upgraded server without difficulty.

The two applications that use Aspose will not publish and get the "Failed to copy file.......Apose.Cells.dll.deploy......." message.

The full error is provided in the attachment.

Can someone help identify the problem?

#2

Hi,

Thanks for your posting and using Aspose APIs.

It seems none of the Aspose DLLs (Aspose.Cells, Aspose.Email, Aspose.Pdf etc) is not being copied to your destination directory.

Please post screenshots in some word document showing step by step guide to replicate this issue so that we reproduce this issue at our end and investigate how it could be resolved.

Please also download and try the latest version: Aspose.Cells for .NET 8.5.1 and see if it makes any difference in resolving this issue.

#3

Please see the attached.

The important issues as I see it:

The problem began for deployments following our upgrade of the server OS to Windows Server 2008 R2.

All applications other than the two using Aspose DLLs publish fine.

The problem is probably not with the DLLs directly, as the same DLLs would deploy before the server upgrade.

It's probably some kind of configuration issue, but where?

#4

Hi,

Thanks for your screenshots and using Aspose APIs.

I have looked into this issue and found you are right, this error is not directly related to Aspose APIs but it is some sort of configuration errors. I have looked it on the internet and found many other users are facing this type of error. Please post your issue in the relevant sites to find the solution to this problem.

Here are few links related to this error for your reference.

( http://stackoverflow.com/questions/5858811/frontpage-server-extensions-install-problem )
( http://stackoverflow.com/questions/8787946/the-web-server-does-not-appear-to-have-frontpage-server-extensions-installed-a )
( http://forums.codeguru.com/showthread.php?519965-quot-The-Web-server-does-not-appear-to-have-FrontPage-Server-Extensions-installed-quot-althou )

#5

I am very much not happy with your response.

First, I have already seen most of these articles.

Second, they ignore a fundamental distinction:

These articles describe issues in not being able to deploy any projects use FPSE.

I CAN DEPLOY EVERY PROJECT EXCEPT THE ONES THAT HAVE ASPOSE DLLs. SO THE ISSUE IS NOT THAT FPSE IS NOT INSTALLED, IT IS INSTALLED! EVERY PROJECT EXCEPT ASPOSE PROJECTS CAN USE IT!

#6

Hi,

Thanks for your posting and using Aspose APIs.

We will have to prepare the environment similar to yours so that we could replicate this issue at our end.

Please let us know do we need to install these things in sequence.

1 - Windows Server 2008 R2
2 - Visual Studio 2013
3 - Front Page server extensions

Do we need to install anything else too?

Could you please also guide us more about the Front Page Server Extensions. Are they related to IIS 7 or part of it?

Thanks for your cooperation.