Return-Path: X-Original-To: apmail-logging-log4net-user-archive@www.apache.org Delivered-To: apmail-logging-log4net-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9527E10C4F for ; Fri, 27 Feb 2015 12:54:29 +0000 (UTC) Received: (qmail 48252 invoked by uid 500); 27 Feb 2015 12:54:29 -0000 Delivered-To: apmail-logging-log4net-user-archive@logging.apache.org Received: (qmail 48213 invoked by uid 500); 27 Feb 2015 12:54:29 -0000 Mailing-List: contact log4net-user-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Log4NET User" List-Id: Delivered-To: mailing list log4net-user@logging.apache.org Received: (qmail 48202 invoked by uid 99); 27 Feb 2015 12:54:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Feb 2015 12:54:29 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Thiemo.Kellner@bfs.admin.ch designates 162.23.32.14 as permitted sender) Received: from [162.23.32.14] (HELO mail14.admin.ch) (162.23.32.14) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Feb 2015 12:54:23 +0000 Received: from mail02.admin.ch (mail02.admin.ch [162.23.97.167]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail14.admin.ch (mailout) with ESMTPS id 4E2EE200A0AC for ; Fri, 27 Feb 2015 13:54:01 +0100 (CET) Received: from mail42.admin.ch (mail42.admin.ch [162.23.97.171]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail02.admin.ch (mailhub) with ESMTPS id 4312E400A09F for ; Fri, 27 Feb 2015 13:54:01 +0100 (CET) Received: from mail42.admin.ch (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 1DCBF3C342B for ; Fri, 27 Feb 2015 13:54:01 +0100 (CET) Received: from mail03.admin.ch (unknown [162.23.97.168]) by mail42.admin.ch (Postfix) with ESMTPS id 0E90D3C1493 for ; Fri, 27 Feb 2015 13:54:01 +0100 (CET) Received: from exhub.admin.ch (sb00104a.adb.intra.admin.ch [10.135.88.104]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail03.admin.ch (mailhost) with ESMTPS id EC6E6400A085 for ; Fri, 27 Feb 2015 13:54:00 +0100 (CET) Received: from SB00113A.adb.intra.admin.ch ([169.254.10.211]) by SB00104A.adb.intra.admin.ch ([10.135.87.104]) with mapi id 14.03.0224.002; Fri, 27 Feb 2015 13:54:00 +0100 From: To: Subject: AW: 64bit problem? Thread-Topic: 64bit problem? Thread-Index: AdBRwLQXY42f1w2ESZOdppUlhxUT8wAAakzwAAHXtQAAAtu5gAAhDC9QAAGi1JAAAHdtAAAKMMMw Date: Fri, 27 Feb 2015 12:54:00 +0000 Message-ID: References: <015d01d051d2$1eade800$5c09b800$@gmail.com> <019f01d0526a$272ce8d0$7586ba70$@gmail.com> In-Reply-To: <019f01d0526a$272ce8d0$7586ba70$@gmail.com> Accept-Language: de-CH, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.135.87.13] Content-Type: multipart/alternative; boundary="_000_CA00B50FE6BB0A4C9EB2B03F909CCFF130D191C3SB00113Aadbintr_" MIME-Version: 1.0 X-TM-AS-MML: disable X-Virus-Checked: Checked by ClamAV on apache.org --_000_CA00B50FE6BB0A4C9EB2B03F909CCFF130D191C3SB00113Aadbintr_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable It seem so confusing to me. If there was a security problem loading the mod= ules, I would suspect that my modules where not listed as available with PS I:\wa_analyse\SIS_METASTAT\Files> get-module -listavailable Directory: C:\Windows\system32\WindowsPowerShell\v1.0\Modules ModuleType Name ExportedCommands ---------- ---- ---------------- Manifest ActiveDirectory {Get-ADRootDSE, New-ADObject= ,... Manifest ADRMS {Update-ADRMS, Uninstall-ADR= M... Manifest AppLocker {Set-AppLockerPolicy, Get-Ap= p... Manifest BestPractices {Get-BpaModel, Invoke-BpaMod= e... Manifest BitsTransfer {Add-BitsFile, Remove-BitsTr= a... Manifest CimCmdlets {Get-CimAssociatedInstance, = G... Manifest GroupPolicy {Backup-GPO, Copy-GPO, Get-G= P... Script ISE {New-IseSnippet, Import-IseS= n... Manifest Microsoft.PowerShell.Diagnostics {Get-WinEvent, Get-Counter, = I... Manifest Microsoft.PowerShell.Host {Start-Transcript, Stop-Tran= s... Manifest Microsoft.PowerShell.Management {Add-Content, Clear-Content,= ... Manifest Microsoft.PowerShell.Security {Get-Acl, Set-Acl, Get-PfxCe= r... Manifest Microsoft.PowerShell.Utility {Format-List, Format-Custom,= ... Manifest Microsoft.WSMan.Management {Disable-WSManCredSSP, Enabl= e... Script PSDiagnostics {Disable-PSTrace, Disable-PS= W... Binary PSScheduledJob {New-JobTrigger, Add-JobTrig= g... Manifest PSWorkflow {New-PSWorkflowExecutionOpti= o... Manifest PSWorkflowUtility Invoke-AsWorkflow Manifest ServerManager {Get-WindowsFeature, Add-Win= d... Manifest TroubleshootingPack {Get-TroubleshootingPack, In= v... Directory: C:\Program Files\Microsoft Monitoring Agent\Agent\PowerShell ModuleType Name ExportedCommands ---------- ---- ---------------- Binary Microsoft.MonitoringAgent.PowerS... {Checkpoint-WebApplicationMo= n... Directory: I:\WA_ANALYSE\AAA_INFA_CORE\Libs ModuleType Name ExportedCommands ---------- ---- ---------------- Script BFS.Powershell.Logging {assert-debug, assert-error,= ... Script BFS.Powershell.PowerCenter {approve-pocallworkflows, ap= p... Script BFS.Powershell.Utility {get-basename, get-dirname, = g... The availability on the workstation looks the same... Ok, I found a book that states that binary modules, i.e. dll, usually canno= t be loaded from network drives for security reasons. But now if it *usuall= y* is not allowed how can I get the exception? I can see that the modules c= an get loaded because they are not binary. It is, however, not investigated= if the happen to load binary modules themselves dynamically. Liebe Gr=FCsse/Cordialement/Cordialit=E0 Thiemo Kellner -- Office f=E9d=E9ral de la statistique Espace de l'Europe 10 2010 Neuch=E2tel / Suisse IT-AB Tel +41 32 71 36516 Von: Dominik Psenner [mailto:dpsenner@gmail.com] Gesendet: Freitag, 27. Februar 2015 09:48 An: 'Log4NET User' Betreff: AW: 64bit problem? It might be a security issue then. For instance, loading a dll from a network share is (from the operating sys= tems point of view) a dangerous operation. When I try to open a zip file on= my computer which is located on a NAS that "lives" outside of the network = domain windows requires me to confirm 3 times a error message dialog at me = stating "Windows cannot open the folder. The compressed zipped folder is in= valid.", but then it opens up just fine. Yes, windows is like that.. Von: Thiemo.Kellner@bfs.admin.ch [mailt= o:Thiemo.Kellner@bfs.admin.ch] Gesendet: Freitag, 27. Februar 2015 08:42 An: log4net-user@logging.apache.org Betreff: AW: 64bit problem? I am affraid, the dll file is there. Following code snipped should make sur= e it is before trying to load the dll if (-not (Test-Path -Path $log4netDllPathString)) { assert-fatal( 'I cannot find the logging library at "' + $log4netDllPathString + '"') exit 1 } # [void][Reflection.Assembly]::LoadFile('I:\WA_ANALYSE\AAA_INFA_CORE\= Libs\log4net-1.2.13\bin\net\4.0\release\log4net.dll') [void][Reflection.Assembly]::LoadFile($log4netDllPathString) and I actually can see the file with C:\Users\s00489>dir I:\WA_ANALYSE\AAA_INFA_CORE\Libs\log4net-1.2.13\bin\net= \4.0\release\log4net.dll Volume in drive I is WA-REF$ Volume Serial Number is 2702-33EF Directory of I:\WA_ANALYSE\AAA_INFA_CORE\Libs\log4net-1.2.13\bin\net\4.0\re= lease 18.11.2013 04:51 301'056 log4net.dll 1 File(s) 301'056 bytes 0 Dir(s) 137'992'851'456 bytes free I cannot put the library elsewhere. Maybe there is an issue because it is a network drive but I would not know = why it would work on my own laptop then. Liebe Gr=FCsse/Cordialement/Cordialit=E0 Thiemo Kellner -- Office f=E9d=E9ral de la statistique Espace de l'Europe 10 2010 Neuch=E2tel / Suisse IT-AB Tel +41 32 71 36516 Von: Radovan Raszka [mailto:raszka@hasam.cz] Gesendet: Freitag, 27. Februar 2015 07:54 An: 'Log4NET User' Betreff: RE: 64bit problem? It looks like powershell can't find where log4net.dll is located. As log4ne= t is platform neutral (compiled as any CPU), I don't think 32 x 64 bit OS i= s issue. Where you have log4net.dll installed? Probably is good idea to put it into = GAC. Or put it into folder where powershell is installed. Key is to find where p= owershell tried to find log4net.dll - is it possible to discover this info? Radovan From: Thiemo.Kellner@bfs.admin.ch [mail= to:Thiemo.Kellner@bfs.admin.ch] Sent: Thursday, February 26, 2015 4:19 PM To: log4net-user@logging.apache.org Subject: AW: 64bit problem? Assuming that on either system the most resent framework gets loaded, on bo= th systems 4.0.30319 is used. However, on the server there are both flavour= s, 32 and 64 bit. I do not know which one is loaded. I forgot to mention that we use log4net 1.2.13, in case this makes a differ= ence. The powershell version on the server is 3, on the laptop it is 4. Liebe Gr=FCsse/Cordialement/Cordialit=E0 Thiemo Kellner -- Office f=E9d=E9ral de la statistique Espace de l'Europe 10 2010 Neuch=E2tel / Suisse IT-AB Tel +41 32 71 36516 Von: Dominik Psenner [mailto:dpsenner@gmail.com] Gesendet: Donnerstag, 26. Februar 2015 15:40 An: 'Log4NET User' Betreff: AW: 64bit problem? To be honest, the error message is rather cryptic to me. What I know is tha= t 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 [mailt= o: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=FCsse/Cordialement/Cordialit=E0 Thiemo Kellner -- Office f=E9d=E9ral de la statistique Espace de l'Europe 10 2010 Neuch=E2tel / Suisse IT-AB Tel +41 32 71 36516 Von: Thiemo.Kellner@bfs.admin.ch [mailt= o:Thiemo.Kellner@bfs.admin.ch] Gesendet: Donnerstag, 26. Februar 2015 13:36 An: 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 'FileSys= tem' 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], WriteErrorEx= cep tion + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExcep= tio n,metadata_join_params-thiemo.ps1 I found http://stackoverflow.com/questions/10249406/powershell-v2-load-a-co= m-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 i= f this might cause the problem. At least I could pin the line of code where= the exception gets thrown: [void][Reflection.Assembly]::LoadFile($log4netD= llPathString) Has anyone an idea? Liebe Gr=FCsse/Cordialement/Cordialit=E0 Thiemo Kellner -- Office f=E9d=E9ral de la statistique Espace de l'Europe 10 2010 Neuch=E2tel / Suisse IT-AB Tel +41 32 71 36516 --_000_CA00B50FE6BB0A4C9EB2B03F909CCFF130D191C3SB00113Aadbintr_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

It seem= so confusing to me. If there was a security problem loading the modules, I= would suspect that my modules where not listed as available with

&n= bsp;

PS I:\wa_analyse\SIS_METASTAT\F= iles> get-module -listavailable

 

 

    Directory: C= :\Windows\system32\WindowsPowerShell\v1.0\Modules

 

 

ModuleType Name  &nbs= p;            &= nbsp;           &nbs= p;    ExportedCommands

---------- ----  &nbs= p;            &= nbsp;           &nbs= p;    ----------------

Manifest   ActiveDire= ctory           &nbs= p;         {Get-ADRootDSE, New-ADOb= ject,...

Manifest   ADRMS   &n= bsp;            = ;            &n= bsp;  {Update-ADRMS, Uninstall-ADRM...

Manifest   AppLocker&= nbsp;            &nb= sp;            =  {Set-AppLockerPolicy, Get-App...

Manifest   BestPracti= ces            =            {Get-BpaModel,= Invoke-BpaMode...

Manifest   BitsTransf= er            &= nbsp;           {Add-Bits= File, Remove-BitsTra...

Manifest   CimCmdlets=             &nb= sp;            = {Get-CimAssociatedInstance, G...

Manifest   GroupPolic= y            &n= bsp;            {Bac= kup-GPO, Copy-GPO, Get-GP...

Script     = ISE            =             &nb= sp;        {New-IseSnippet, Import-IseSn= ...

Manifest   Microsoft.= PowerShell.Diagnostics    {Get-WinEvent, Get-Counter, I...

Manifest   Microsoft.= PowerShell.Host          = {Start-Transcript, Stop-Trans...

Manifest   Microsoft.= PowerShell.Management     {Add-Content, Clear-Content, = ...

Manifest   Microsoft.= PowerShell.Security       {Get-Acl, Set-Acl, = Get-PfxCer...

Manifest   Microsoft.= PowerShell.Utility        {Format-List, = Format-Custom, ...

Manifest   Microsoft.= WSMan.Management          {Dis= able-WSManCredSSP, Enable...

Script     = PSDiagnostics          &n= bsp;            {Dis= able-PSTrace, Disable-PSW...

Binary     = PSScheduledJob          &= nbsp;           {New-JobT= rigger, Add-JobTrigg...

Manifest   PSWorkflow=             &nb= sp;            = {New-PSWorkflowExecutionOptio...

Manifest   PSWorkflow= Utility           &n= bsp;       Invoke-AsWorkflow

Manifest   ServerMana= ger            =            {Get-WindowsFe= ature, Add-Wind...

Manifest   Troublesho= otingPack           =       {Get-TroubleshootingPack, Inv...<= /span>

 

 

    Directory: C= :\Program Files\Microsoft Monitoring Agent\Agent\PowerShell

 

 

ModuleType Name  &nbs= p;            &= nbsp;           &nbs= p;    ExportedCommands

---------- ----  &nbs= p;            &= nbsp;           &nbs= p;    ----------------

Binary     = Microsoft.MonitoringAgent.PowerS... {Checkpoint-WebApplicationMon...

 

 

    Directory: I= :\WA_ANALYSE\AAA_INFA_CORE\Libs

 

 

ModuleType Name  &nbs= p;            &= nbsp;           &nbs= p;    ExportedCommands

---------- ----  &nbs= p;            &= nbsp;           &nbs= p;    ----------------

Script     = BFS.Powershell.Logging         = ;     {assert-debug, assert-error, ...

Script     = BFS.Powershell.PowerCenter        &= nbsp; {approve-pocallworkflows, app...

Script     = BFS.Powershell.Utility         = ;     {get-basename, get-dirname, g...

&n= bsp;

The ava= ilability on the workstation looks the same…

&n= bsp;

Ok, I f= ound a book that states that binary modules, i.e. dll, usually cannot be lo= aded from network drives for security reasons. But now if it *usually* is n= ot allowed how can I get the exception? I can see that the modules can get loaded because they are not binary. It = is, however, not investigated if the happen to load binary modules themselv= es dynamically.

&n= bsp;

Liebe Gr=FCsse/Cordialement/Cordialit=E0=

 

Thiemo Kellner

 

--

Office f=E9d=E9ral de la statistique
Espace de l'Europe 10
2010 Neuch=E2tel / Suisse

IT-AB<= /p>

Tel   &nb= sp; +41 32 71 36516

 

Von: Dominik Psenner [mailto:dpsenner@gmail.com]
Gesendet: Freitag, 27. Februar 2015 09:48
An: 'Log4NET User'
Betreff: AW: 64bit problem?

 

It migh= t be a security issue then.

&n= bsp;

For ins= tance, loading a dll from a network share is (from the operating systems po= int of view) a dangerous operation. When I try to open a zip file on my com= puter which is located on a NAS that “lives” outside of the network domain windows requires me to confirm 3 times a err= or message dialog at me stating “Windows cannot open the folder. The = compressed zipped folder is invalid.”, but then it opens up just fine= .

&n= bsp;

Yes, wi= ndows is like that..

&n= bsp;

Von: Thiemo.Kellner@bfs.admin.ch<= /a> [mailto:Thiemo.Kellner@b= fs.admin.ch]
Gesendet: Freitag, 27. Februar 2015 08:42
An: log4net-user@= logging.apache.org
Betreff: AW: 64bit problem?

 

I am af= fraid, the dll file is there. Following code snipped should make sure it is= before trying to load the dll

 <= /span>

      = if (-not (Test-Path -Path $log4netDllPathString)) {

     &= nbsp;      assert-fatal(

     &= nbsp;            'I = cannot find the logging library at "' +

     &= nbsp;            $lo= g4netDllPathString + '"')

     &= nbsp;      exit 1

      = }

#     =   [void][Reflection.Assembly]::LoadFile('I:\WA_ANALYSE\AAA_INFA_CORE\L= ibs\log4net-1.2.13\bin\net\4.0\release\log4net.dll')

      = [void][Reflection.Assembly]::LoadFile($log4netDllPathString)

 <= /span>

and I a= ctually can see the file with

 <= /span>

C:\Users\s00489>dir I:\WA_AN= ALYSE\AAA_INFA_CORE\Libs\log4net-1.2.13\bin\net\4.0\release\log4net.dll

Volume in drive I is WA-REF$

Volume Serial Number is 2702-33= EF

 

Directory of I:\WA_ANALYSE\AAA_= INFA_CORE\Libs\log4net-1.2.13\bin\net\4.0\release

 

18.11.2013  04:51 &nb= sp;         301'056 log4net.dll

     &= nbsp;         1 File(s)  =       301'056 bytes

     &= nbsp;         0 Dir(s)  137'99= 2'851'456 bytes free

 <= /span>

I canno= t put the library elsewhere.

 <= /span>

Maybe t= here is an issue because it is a network drive but I would not know why it = would work on my own laptop then.

Liebe Gr=FCsse/Cordialement/Cordialit=E0=

 

Thiemo Kellner

 

--

Office f=E9d=E9ral de la statistique
Espace de l'Europe 10
2010 Neuch=E2tel / Suisse

IT-AB<= /p>

Tel   &nb= sp; +41 32 71 36516

 

Von: Radovan Raszka [mailto:raszka@hasam.cz= ]
Gesendet: Freitag, 27. Februar 2015 07:54
An: 'Log4NET User'
Betreff: RE: 64bit problem?

 

It looks l= ike powershell can’t find where log4net.dll is located. As log4net is= platform neutral (compiled as any CPU), I don’t think 32 x 64 bit OS= is issue.

Where you = have log4net.dll installed? Probably is good idea to put it into GAC.

Or put it = into folder where powershell is installed. Key is to find where powershell = tried to find log4net.dll – is it possible to discover this info?

Radovan

 

From:<= /b> Thiemo.Kellner@bfs.admin.ch<= /a> [mailto:Thiemo.Kellner@b= fs.admin.ch]
Sent: Thursday, February 26, 2015 4:19 PM
To: log4net-user@= logging.apache.org
Subject: AW: 64bit problem?

 

Assumin= g that on either system the most resent framework gets loaded, on both syst= ems 4.0.30319 is used. However, on the server there are both flavours, 32 a= nd 64 bit. I do not know which one is loaded.

 <= /span>

I forgo= t to mention that we use log4net 1.2.13, in case this makes a difference. T= he powershell version on the server is 3, on the laptop it is 4.

 <= /span>

Liebe Gr=FCsse/Cordialement/Cordialit=E0=

 

Thiemo Kellner

 

--

Office f=E9d=E9ral de la statistique
Espace de l'Europe 10
2010 Neuch=E2tel / Suisse

IT-AB<= /p>

Tel   &nb= sp; +41 32 71 36516

 

Von: Dominik Psenner [mailto:dpsenner@gm= ail.com]
Gesendet: Donnerstag, 26. Februar 2015 15:40
An: 'Log4NET User'
Betreff: AW: 64bit problem?

 

To be h= onest, the error message is rather cryptic to me. What I know is that log4n= et is not compiled against a specific architecture. If the targeted .NET fr= amework is installed it should work. Have you checked that?

 <= /span>

Von: Thiemo.Kellner@bf= s.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 pr= oblem?

 <= /span>

Liebe Gr=FCsse/Cordialement/Cordialit=E0=

 

Thiemo Kellner

 

--

Office f=E9d=E9ral de la statistique
Espace de l'Europe 10
2010 Neuch=E2tel / Suisse

IT-AB<= /p>

Tel   &nb= sp; +41 32 71 36516

 

Von: Thiemo.Kellner@bfs.admin.ch<= /a> [mailto:Thiemo.Kellner@b= fs.admin.ch]
Gesendet: Donnerstag, 26. Februar 2015 13:36
An: 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 succe= ssfully from a batch file on my laptop but on the server I get<= /o:p>

 

Attempting to perform the Initi= alizeDefaultDrives operation on the 'FileSystem'

provider failed.

I:\WA_ANALYSE\AAA_INFA_CORE\Scr= ipts\metadata_join_params-thiemo.ps1 :

Exception calling "LoadFil= e" with "1" argument(s): "The parameter is<= /o:p>

incorrect. (Exception from HRES= ULT: 0x80070057 (E_INVALIDARG))"

At line:1 char:1

+ I:\WA_ANALYSE\AAA_INFA_CO= RE\Scripts\metadata_join_params-thiemo.ps1

-stat_activi ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~~~

    + Catego= ryInfo          : NotSpecified= : (:) [Write-Error], WriteErrorExcep

   tion

    + FullyQ= ualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio

   n,metadata_join_pa= rams-thiemo.ps1

 

 

I found http://stackoverflow.com/questions/10249406/powershell-v2-load-a-com-intero= p-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 th= is might cause the problem. At least I could pin the line of code where the exception gets thrown: [void][Refle= ction.Assembly]::LoadFile($log4netDllPathString)

 

Has anyone an idea?=

 

Liebe Gr=FCsse/Cordialement/Cordialit=E0

 

Thiemo Kellner

 

--

Offi= ce f=E9d=E9ral de la statistique
Espace de l'Europe 10
2010 Neuch=E2tel / Suisse

IT-AB

Tel     +41 32= 71 36516

 

--_000_CA00B50FE6BB0A4C9EB2B03F909CCFF130D191C3SB00113Aadbintr_--