logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominik Psenner" <dpsen...@gmail.com>
Subject AW: 64bit problem?
Date Thu, 26 Feb 2015 14:40:08 GMT
To be honest, the error message is rather cryptic to me. What I know is that
log4net is not compiled against a specific architecture. If the targeted
.NET framework is installed it should work. Have you checked that?

 

Von: Thiemo.Kellner@bfs.admin.ch [mailto:Thiemo.Kellner@bfs.admin.ch] 
Gesendet: Donnerstag, 26. Februar 2015 13:48
An: log4net-user@logging.apache.org
Betreff: AW: 64bit problem?

 

I found https://issues.apache.org/jira/browse/LOG4NET-138 . Maybe there is a
problem?

 

Liebe Grüsse/Cordialement/Cordialità

 

Thiemo Kellner

 

--

Office fédéral de la statistique 
Espace de l'Europe 10 
2010 Neuchâtel / Suisse

IT-AB

Tel     +41 32 71 36516

 

Von: Thiemo.Kellner@bfs.admin.ch <mailto:Thiemo.Kellner@bfs.admin.ch>
[mailto:Thiemo.Kellner@bfs.admin.ch] 
Gesendet: Donnerstag, 26. Februar 2015 13:36
An: log4net-user@logging.apache.org <mailto:log4net-user@logging.apache.org>

Betreff: 64bit problem?

 

Hi all

 

I am at my wits’ end. We developped PowerShell script which uses log4net. I
can run the script successfully from a batch file on my laptop but on the
server I get

 

Attempting to perform the InitializeDefaultDrives operation on the
'FileSystem'

provider failed.

I:\WA_ANALYSE\AAA_INFA_CORE\Scripts\metadata_join_params-thiemo.ps1 :

Exception calling "LoadFile" with "1" argument(s): "The parameter is

incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))"

At line:1 char:1

+ I:\WA_ANALYSE\AAA_INFA_CORE\Scripts\metadata_join_params-thiemo.ps1

-stat_activi ...

+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~

~~~

    + CategoryInfo          : NotSpecified: (:) [Write-Error],
WriteErrorExcep

   tion

    + FullyQualifiedErrorId :
Microsoft.PowerShell.Commands.WriteErrorExceptio

   n,metadata_join_params-thiemo.ps1

 

 

I found
http://stackoverflow.com/questions/10249406/powershell-v2-load-a-com-interop
-dll which points to a possible problem with mixing 32 dlls in 64 bit
PowerShell. As my laptop is 32 and the server 64 bit, I was wondering if
this might cause the problem. At least I could pin the line of code where
the exception gets thrown:
[void][Reflection.Assembly]::LoadFile($log4netDllPathString)

 

Has anyone an idea?

 

Liebe Grüsse/Cordialement/Cordialità

 

Thiemo Kellner

 

--

Office fédéral de la statistique 
Espace de l'Europe 10 
2010 Neuchâtel / Suisse

IT-AB

Tel     +41 32 71 36516

 


Mime
View raw message