[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1481
  • Last Modified:

EMC initialization failure: 'ConsoleInitialize.ps1' not recognized

When trying to launch the EMC, we're getting the following error:

Initialization failed
The following error occurred while configuring Help links:

The tern 'ConsoleInitialization.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

I've looked at many of the EMC failure items listed but none of them address this error. The script exists on the server in the Exchange/Remote Scripts folder but PowerShell is not recognizing it. Anyone have any suggestions as to how we troubleshoot this? Thanks!
0
MehtaJasmin
Asked:
MehtaJasmin
1 Solution
 
EmkadeuCommented:
Did you type: .\ConsoleInitialization.ps1
0
 
MehtaJasminAuthor Commented:
I tried doing that at a powershell prompt and nothing happens. It doesn't return an error but it doesn't appear to do anything.
0
 
Deepu ChowdaryCommented:
Check this once.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
MehtaJasminAuthor Commented:
Thanks for the link but those are all different errors than the one I'm seeing. The exact text of the error I'm getting is above.
0
 
Deepu ChowdaryCommented:
Check this discussion once..
0
 
MehtaJasminAuthor Commented:
been there, done that
0
 
I QasmiCommented:
My concern is that have u set the correct path for the scripts files if not look at this article :

Running a Script Inside the Exchange Management Shell

Those familiar with the Cmd.exe environment know how to run command shell scripts. These scripts are simply text files that have the .bat file name extension. Like batch files, you can create the Shell script files by using a text editor, such as Notepad. You can also use the Windows PowerShell Integrated Scripting Environment (ISE) to write scripts. The Windows PowerShell ISE provides a rich editing experience with debugging support, syntax coloring, selective execution, and more. The Shell script files use the .ps1 file name extension.

The Shell uses a root directory for script files when they are called. By default, the root directory is the <root drive>:\Program Files\Microsoft\Exchange Server\V14\bin directory. You can also verify the current PSHome directory on any computer running the Shell by running $PSHome at a command prompt. Both of these directories are in the PATH environment variable.

If a script file is saved to the root directory, you can call it by using the script name. If the script file is located somewhere other than the current location, the path and script name must be used. If the script file is located in the current location, the script name must be prefixed by the period backslash (.\) characters.

These examples show the command syntax requirements for calling three different scripts. These examples all use the Get-Date cmdlet, from three different locations.

[PS] C:\>Get-Date-Script-A.ps1
Friday, January 20, 2006 3:13:01 PM

The script file Get-Date-Script-A.ps1 is located in the directory specified by $PSHhome and requires only the script name to run.

[PS] C:\>c:\workingfolder\Get-Date-Script-B.ps1
Friday, January 20, 2006 3:13:25 PM
The script file Get-Date-Script-B.ps1 is located in the C:\workingfolder directory so the full path must be supplied to run.

[PS] C:\>.\Get-Date-Script-C.ps1
Friday, January 20, 2006 3:13:40 PM

The script file Get-Date-Script-C.ps1 is located in the current location, C:\. Therefore, it must be prefixed with .\ to run
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now