Hello Henrik,

Thank you for posting in our forum.

What we found is that our Word engine use FileStream with FileMode parameter set as OpenOrCreate, while same parameter in Excel engine is set to Create. To test if this rise the exception you are receiving I have implement a small sample project. This project creates two text documents. First with FileMode set to OpenOrCreate and second with same parameter set to Create. Please run this sample and try to create this two files on your server. Please let me know if you receive the same exception.

Please note, in order to be able to investigate this issue in deeper details I will need a little bit more information

   - Can you send me the entire exception stack?

   - From your post I have understood that you were able to create the Word file on your server. You received the exception after the file was created. Is this correct?

Waiting for your feedback.

The exception looks the same as Before and I have posted it in a previous post. It looks like this.

Exception: The type initializer for 'MS.Utility.EventTrace' threw an exception.

  ex.StackTrace.ToString "   at MS.Utility.EventTrace.EasyTraceEvent(Keyword keywords, Event eventID)     at System.IO.Packaging.Package.Open(Stream stream, FileMode packageMode, FileAccess packageAccess, Boolean streaming)     at Infragistics.Documents.Core.Packaging.PackageFactory.Open(Stream stream, FileMode packageMode)     at Infragistics.Documents.Word.WordprocessingMLWriter.Open(Stream stream, IPackageFactory packageFactory)     at Infragistics.Documents.Word.Document.SaveHelper(Stream stream)     at Infragistics.Documents.Word.Document.Save(String filename)     at XBOW.DB.FileManager.CreateOffer() in C:\Users\LPHB\Documents\Visual Studio 2010\Projects\XBOW\XBOWclient\Classes\General\FileManager.vb:line 662" String

I understand if you have problems repreducing it on your side. I am just fishing for some sort of hint that can solve it.

The excel workbook format is sent into the export function.

I have two different scenarios that I am testing, one works and one doesn't:

Workbook format 97-2003, filename ending with .xLs = working!

Workbook format 2007, filename ending with .xlsx = not working!

strange...

/Henr

Hi Zlatan,

In order to be able to try to investigate this further can you please give us more information regarding your scenario:

1. What is the environment on your developer machine where the application is running?

2. What is the environment on the server where you are trying to save Word and Excel files?

3. Can you save the files at your local machine?

4. How you are access the server?

Looking forward to your reply.

Hello Miko!

Finally, I have found some interesting things for you. I had a long discussion with our service desk and we tried a lot of different scenarios.

When I am creating the file on the server, I am doing it using a dedicated service user:

First, I log on with the service user, I call impersonate, and last of all I create the file. Something like this:

If LogonUser(ConfigFS.ServiceAccountUserID, ConfigFS.ServiceAccountDomain, ConfigFS.ServiceAccountPassword, 2, 0, tokenHandle) Then

Dim newId As New WindowsIdentity(tokenHandle)

Using impersonatedUser As WindowsImpersonationContext = newId.Impersonate()

What I tried was that I added the service user as local admin on my computer, and that worked.

This means that the user that creates the file on our server must be local admin on the computer executing the application.

This seems to be needed for xlsx files, but not for XLs files.

I hope that you can verify this scenario.

Perhaps this is normal, but I don't understand why different file types behave differently.

/Henrik

Milko, any news in this topic?

/Henrik

It works like a charm, thanks Milko!

/Henrik

Hello Henrik,

Thank you for your feedback.

So we have check this in much deeper details. What we found is somehow, the .NET framework is able to assert for registry read permissions (within the MS.Utility.EventTrace.IsClassicETWRegistryEnabled method) on the HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics\ registry key, but then it is not able to actually read from that location. So something very odd is going on.

Looking around on online, it appears that many of the people experiencing an error in the same stack trace are also in an impersonated user scenario. So, we think this is probably a bug in the .NET Framework when doing user impersonation. Trying to disable tracing will not help work around this issue by the way, because the error is happening in the static constructor of the class that checks whether tracing is enabled, so it never gets to the point of checking. So please do not try to change your app.config file.

What we found as a workaround is to force the static constructor of the tracing class to get executed before the user impersonation is done. This bypasses the bug in the .NET Framework. To do so we have added this code exactly before the user is impersonated:

Dim m As New MemoryStream()
Dim p As System.IO.Packaging.Package = System.IO.Packaging.Package.Open(m, System.IO.FileMode.Create)
p.Close()
m.Close()

With this piece of code added it successfully have created the xlsx file at my server.

Please let me know if you need any further assistance.