Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7813235
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 2, 20262026-06-02T04:46:51+00:00 2026-06-02T04:46:51+00:00

I have a powershell script that runs a 32 bit com object so when

  • 0

I have a powershell script that runs a 32 bit com object so when I run it in Powershell 64x it fails but runs fine in 86x

When I run it in a Sql Server Agent job it has the same 64x failure.

Is there a way around this? Like SSIS packages?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-02T04:46:53+00:00Added an answer on June 2, 2026 at 4:46 am

    You can directly invoke the 32-bit version of PowerShell by calling it through the WOW64 path:

    %SystemRoot%\syswow64\WindowsPowerShell\v1.0\powershell.exe
    

    Using the -File command line argument you can pass the name of the script you would like to run.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a complex Powershell script that gets run as part of a SQL
I have a Powershell script that calls sqlcmd to run a sql script that
I have developed a Powershell script that needs to be run automatically daily. This
I have a SQL 2008 job that does database backups using a Powershell script.
I have a powershell script that runs fxcopcmd in the output window. Turns out
I have a PowerShell script that needs to run normally, and also when invoked
I have a powershell script that runs a console .exe application. The console application
I have a PowerShell script that is run automatically when our monitoring service detects
I have a SQL 2005 instance that runs a job that uses a Powershell
I have a Powershell script that is going to be run through an automation

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.