I've followed the instructions to set the license but it doesn't work. I am using this as a simple test to see if I can activate Aspose.Words with the xml license file but I get two errors.

<%
response.write "test"

'---License file
Dim license
Set license = Server.CreateObject("Aspose.Words.License")
license.SetLicense "Aspose.Words.lic"
%>

results in:

test
Aspose.Words error '80070002'

Cannot find license 'Aspose.Words.lic'.

/test.asp, line7

 

Tried this as well:

<%
response.write "test"

'---License file
Dim license
Set license = Server.CreateObject("Aspose.Words.License")
license.SetLicense "Aspose.Words.lic.xml"
%>

Results in:

test
mscorlib error '80070005'

UnauthorizedAccessException "C:\Program Files\Aspose\Aspose.Words\Bin\Aspose.Words.lic.xml"。

/test.asp, line7

Please set file access rights for you application in IIS.

---

Vladimir Averkin
Developer/Technical Support
Aspose Auckland Team

For File NTFS Permissions, I gave FULL ACCESS to {MACHINE_NAME}/IUSR_MACHINENAME for C:\Inetpub\wwwroot and C:\Program Files\Aspose\Aspose.Words\Bin

In IIS, for the default website I also gave FULL ACCESS to {MACHINE_NAME}/IUSR_MACHINENAME where test.asp is located.

But now I get a HTTP 500 error, it can't even initiate the webpage.

If I comment out the license part:

<%
response.write "test"

'---License file
'Dim license
'Set license = Server.CreateObject("Aspose.Words.License")
'license.SetLicense "Aspose.Words.lic.xml"
%>

the page loads and I can read "test"

If I don't use IIS/ASP and directly create a .vbs script and CreateObject instead of Server.CreateObject, it works fine since it doesn't throw back an error at me. So the problem is with IIS.

Am I supposed to edit the DefaultAppPool?

Please check the following articles:

http://www.webwizguide.com/asp/faq/server_permissions.asp

http://support.microsoft.com/default.aspx?scid=kb;en-us;313075

Maybe you will be able to find some helpful information there.

---

Vladimir Averkin
Developer/Technical Support
Aspose Auckland Team

Thank you, it works fine now :)

Glad to hear that.

Can I ask you to describe what was required to make it work? It could be helpful to other users having similar problems.

Best regards,

---

Vladimir Averkin
Developer/Technical Support
Aspose Auckland Team

Spoke too soon.. still having problems. After I set the permission for IUSR_MACHINENAME for the file  Aspose.Words.lic.xml I still get this error:

ASP CODE:
<%
response.write "test"

'---License file

Dim license
Set license = Server.CreateObject("Aspose.Words.License")
'license.SetLicense "Aspose.Words.lic.xml"

'Set license = nothing
%>


ERROR OUTPUT:

test

ServerObject Error 'ASP 0177 : 800401f3'

Server.CreateObject Failed

/testa.asp, Line7

800401f3

Still stuck on this problem, if I comment out the Server.CreateObject line then it's ok...

FILENAME: wwwroot/test.vbs
=============
'---License file
Dim lic, licenseFile
Set lic = CreateObject("Aspose.Words.License")
licenseFile = "C:\Program Files\Aspose\Aspose.Words\Bin\Aspose.Words.lic.xml"
lic.SetLicense licenseFile
Set lic = Nothing
=============

OUTPUT: After running this script on the local machine, nothing happens which means that the object was created successfully. No errors display.

FILENAME: wwwroot/test.asp
=============
'---License file
Dim lic, licenseFile
Set lic = Server.CreateObject("Aspose.Words.License")
licenseFile = "C:\Program Files\Aspose\Aspose.Words\Bin\Aspose.Words.lic.xml"
lic.SetLicense licenseFile
Set lic = Nothing
=============

OUTPUT: browsing to localhost/test.asp results in "Cannot create ServerObject Error."

I'll play around with IIS and Security some more to see if I can fix this... please leave any suggestions here as well. Thanks.

I reinstalled Windows 2003 and Aspose.Words. Same problem occurs. This is very odd. My first post displayed a problem related to file permissions. After I playing around with the NTFS file permissions, I *thought* I fixed it since I could browse to test.asp and have no error in IE browser.

So I reinstalled Windows 2003 and Aspose.Words again as I always like to reinstall everything once I know where the problem is and start anew and now the "Cannot create ServerObject Error." pops up. I started anew twice and the same thing happens, it can't even get to the point where it looks for "Aspose.Words.lic.xml" which is a step backward from my first error post. What is happening here? Running a vbscript on the local machine has no problems so at least Aspose.Words is a registered COM component in the system, just that IIS6 can't see it...

Please instruct me how to set and run the test ASP application on Windows 2003 system and I will try to reproduce the problem and look for possible fixes.

Also please check the following articles from MS Knowledge Base. Maybe you will find them helpful:

http://support.microsoft.com/kb/258932/en-us
http://support.microsoft.com/kb/273744/en-us
http://support.microsoft.com/kb/175804/en-us

Regards,

---

Vladimir Averkin
Developer/Technical Support
Aspose Auckland Team

1) Install Windows 2003 w/ SP1
2) Install IIS 6 - Enable ASP.NET and Classic ASP
3) Install Aspose 3.6.1 msi
4) Enable IUSR_MACHINENAME read/write file permissions for Aspose.Words.lic.xml (I think this step is optional since it can't even create the serverobject yet)

Then copy the script I have above and create test.asp under wwwroot.

Hope you can reproduce the same error.

Hm.. seems like I'll be tackling this problem again since I'll be starting this project that I've been delaying for so long. I read in one of the articles that I should install Aspose.Words using EVERYONE and not just THIS USER, maybe that's why I was having problems not being able to create objects under IIS/ASP last year. This might also explain why I could use my ADMIN account and write a VBSCRIPT to work with Aspose.Words successfully but not with ASP. ASP might not have worked because a user who is connected to IIS is seen as a IUSR internet guest account which is different from the initial THIS USER which was ADMIN in my case. Hopefully this INSTALL FOR EVERYONE is the solution for my problem that I couldn't figure out for so long...

Yes, that probably was the case. Took quite a long time before I was able to figure it out myself :)

---

Vladimir Averkin
Developer/Technical Support
Aspose Auckland Team