0

We have a problem when scripting PowerDesigner on Windows Server 2012. We don't have problems on Windows 10 and Windows 7 (we tried it on several machines).

We are starting PowerDesigner from PowerShell like this:

$PowerDesigner = New-Object -com powerdesigner.application
Add-Type -path “C:\Program Files (x86)\Sybase\PowerDesigner 16\Interop.PdCommon.dll”
Add-Type -path “C:\Program Files (x86)\Sybase\PowerDesigner 16\Add-ins\Microsoft SQL Server 2005 Analysis Service\Interop.PdPDM.dll”

On Windows Server 2012 R2 all properties of the $PowerDesigner object are set to $null. If we try to set a property to some other value we get an error. For example, the statement

$PowerDesigner.InteractiveMode = 1

fails with the following error:

Exception setting "InteractiveMode": "Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED))"

The PowerDesigner version is 16.1.0.3637.

pdUser
  • 1
  • 1
  • Have you tested with 32- or 64-bit versions of Windows 10/7? – pascal Jun 12 '18 at 08:31
  • In the same direction, do you have a 64-bit version of PowerDesigner? I found this mention of problems with using a 32-bit COM object, in a 64-bit environment... https://techtalk.gfi.com/32bit-object-64bit-environment/ – pascal Jun 12 '18 at 08:33
  • I have tested with 64-bit version of Windows 10/7. – pdUser Jun 12 '18 at 09:07
  • Are you running the script interactively, or from a service? I've seen [this question](https://stackoverflow.com/questions/14425803/office-automation-interop-on-windows-server-2012) about background service "station"... – pascal Jun 12 '18 at 09:56
  • I am running the script interactively. – pdUser Jun 12 '18 at 11:06

0 Answers0