vb.net app not finding application configuration file on Windows 2003 Server Standard

[Steve]

Hi All

I have a vb.net 2008 SP1 windows forms app 'SAM' which runs fine on XP /
Vista
I have an app.config file with <probing privatePath="DLLs" />
This is where my DLLs are stored and all works fine in XP and Vista

I recently installed Windows 2003 Server standard R2 on a new computer and
installed my vb app

The app will not run. No error messages, log entries. Nothing

I then installed VS 2008 SP1 on this new computer and loaded the Project

Running from within VS IDE ALL works fine

Mike (see prev post) advised me to turn off 'Enable the Visual Studio
hosting process' in the IDE Project Debug tab
When project is now run, I get error messages that the DLLs cannot be found

Running fuslogvw.exe shows that NO App config file was found, even though
SAM.exe.config file exists in the same folder as SAM.exe

Can anybody help me with this, as I am lost

Regards
Steve

 

[Mike]

Googling:

"LOG: No Application configuration file found"

yields many similar reports.

These threads seem to suggest some things with resolution:

http://social.msdn.microsoft.com/Forums/en-US/clr/thread/1f86f274-f75c-430a-aaf5-96ddf465a86a
http://blogs.msdn.com/suzcook/archive/2003/05/29/57143.aspx
http://www.eggheadcafe.com/conversation.aspx?messageid=31413620&threadid=31405481

and this one seems to get you the CLR details. I bookmarked this one
so I have it around when I get to this point

http://msdn.microsoft.com/en-us/magazine/dd727509.aspx

From what I can this, this is all related to the SxS crap I read
about and I'm completing ignoring this at this point. I head/read
somewhere that MS is doing away or has done away with this SxS stuff
in VS2010.

Maybe others can chime in on this.

 

[Jie Wang [MSFT]]

Hi Steve,

Some request of information first:

Is your application WinForm or WPF?

What's the target .NET version (2.0 or 3.0 or 3.5)?

What's the version of mscoree.dll in Windows\System32 folder?

Do you have .NET Framework 1.1 installed on that machine?

Could you post your complete fusion log of the SAM.exe? And if possible,
the content of the SAM.exe.config.

And could you use the Process Monitor to log the SAM.exe's activities and
find out whether or not the config file has ever been touched?

http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

You can post what you find in the Procmon log here or just send me the log
file if it is not large.

Besides, the Dependency Walker doesn't work well with .NET applications.
What you saw from the depends log is a bug in there caused a buffer overrun
instead of the real problem of the application.

I can understand the feeling when facing this kind of problems. So looking
forward to the log and I'll see what can be done.

Best regards,

Jie Wang

Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 2 business days is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions. Issues of this
nature are best handled working with a dedicated Microsoft Support Engineer
by contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Jie Wang [MSFT]]

Hi Steve,

I found from the Procmon log this interesting event:

The following file was not found.
C:\Program Files\Osmont Technologies\Salon Applications
Manager\DevExpress.BonusSkins.v9.1\DevExpress.BonusSkins.v9.1.dll

From the CSV file record 775 to 781, I saw the CLR tried various ways to
locate the file but all failed with path not found.

Is that the DLL file failed to be loaded?

If not, could you identify which DLL?

By the way, the CSV format log file is really hard to read. Could you get a
PML format instead (which I can open it in my Procmon)?

Thanks,

Jie Wang

Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 2 business days is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions. Issues of this
nature are best handled working with a dedicated Microsoft Support Engineer
by contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Mike]

Hi Steve, Having squash this bugger yet?

With the logs it looks like this BonusSkin stuff could be the issue.
Do you know what it is? It isn't loading and its an EXPLICIT load
which means your application is attempting to load it.

Singling Step with debugger doesn't help? You should be able to find
the exact spot OP CODEs even its in assembly code.

Time to roll up sleeves, pull out the hammer and Divide And Conquer.

PS: A quick google of this Bonus Skin by DevExpress shows there are
reports of binary file curruptions. Smells like might be having this
problem. There is an a BUSINESS for fixing these files:

http://www.corruptedfilerepair.com/...Express.BonusSkins-Developer-Express-Inc..asp

--

Hi Jie

I had to send 2 replies as the file sizes of the attachments were getting
rejected

here is the procman log file in .csv format zipped

Regards
Steve

Hi Steve,

Some request of information first:

Is your application WinForm or WPF?

What's the target .NET version (2.0 or 3.0 or 3.5)?

What's the version of mscoree.dll in Windows\System32 folder?

Do you have .NET Framework 1.1 installed on that machine?

Could you post your complete fusion log of the SAM.exe? And if possible,
the content of the SAM.exe.config.

And could you use the Process Monitor to log the SAM.exe's activities and
find out whether or not the config file has ever been touched?

http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

You can post what you find in the Procmon log here or just send me the log
file if it is not large.

Besides, the Dependency Walker doesn't work well with .NET applications.
What you saw from the depends log is a bug in there caused a buffer
overrun
instead of the real problem of the application.

I can understand the feeling when facing this kind of problems. So looking
forward to the log and I'll see what can be done.

Best regards,

Jie Wang

Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 2 business days is acceptable. Please note that each
follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions. Issues of this
nature are best handled working with a dedicated Microsoft Support
Engineer
by contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.

 

[Steve]

Hi Jie

The problem is none of the DLLs are being found on windows 2003 server

If I move the DLLs into the root folder with SAM.exe all works fine

On windows XP and Vista SAM runs fine with the DLLs in the DLLs sub folder
using the same SAM.exe.config file

If I copy the BonusSkins.dll to the root folder then the error is just the
next DLL SAM is looking for
In other words the Probing section in SAM.exe.config is not being found in
Windows 2003 Server

The reason I sent the .csv file is that the PML format is too big and the
newsgroup rejects it (even when zipped)

I found this through google. Do you think this is the problem

http://blogs.msdn.com/junfeng/archive/2006/08/09/692996.aspx

Regards
Steve

 

[Steve]

Hi Jie

The manifest bug in windows 2003 was the problem, as per
http://blogs.msdn.com/junfeng/archive/2006/08/09/692996.aspx

I added the suggested section to app.manifest file under 'My Project' folder
for SAM, recompiled and now all works fine on Windows 2003 server

Thanks for your efforts anyway

Regards
Steve