did you look at the log file that's mentioned? is there anything useful in there ?
can you run the same command manually from the server logged in as the user bsa maps your role to ?
1) The Log file contains the same lines mentioned above ,it is strange but it references itself.
2) We ran the installation manually from the command line as a user (dcitpatrol) with Admininstrator privileges on the Windows 2012 Server and it worked fine.
We looked at log directory (on the agent side Windows 2012 server) and we found the following ERROR:
This is the additional error we found:
11/28/16 17:17:37.799 DEBUG bldeploy - [ejecutar instalador] chdir to PkgDir: 'C:\temp\stage\1f99510ec47e3069b42b8b1279cd669c\'
11/28/16 17:17:37.799 DEBUG bldeploy - [ejecutar instalador] exeFullPath = (null), CmdLine = "C:\temp\stage\1f99510ec47e3069b42b8b1279cd669c\bldeploycmd.7.bat", workingDir = NULL
11/28/16 17:17:37.799 ERROR bldeploy - vwvhehypp002 4676 BladeLogicRSCD (Not_available): (Not_available): Failed to initialize com. Error code 262
"2) We ran the installation manually from the command line as a user (dcitpatrol) with Admininstrator privileges on the Windows 2012 Server and it worked fine."
-> is that the user you are mapped to in bsa ?
can you attach the entire bldeploy log ?
Here is the bldeploy log.
Solution Engineer DCA
Direct +52 188.8.131.52.00
Mobile +521 55.4588.5719
Blvd. Manuel Avila Camacho No 36 piso 23
Col. Lomas de Chapultepec C.P 11000 Mèxico D.F
Fecha: lunes, 28 de noviembre de 2016, 6:34 p.m.
Para: Antonio Godos <Antonio_Godos@bmc.com>
Asunto: Re: - Unable to create new control file.
BMC Communities <https://communities.bmc.com/?et=watches.email.thread>
Unable to create new control file.
reply from Bill Robinson<https://communities.bmc.com/people/brobinson?et=watches.email.thread> in Server Automation - View the full discussion<https://communities.bmc.com/message/664849?et=watches.email.thread#664849>
Based on this bldeploy log, the details we need are stored in: C:\Program Files (x86)\BMC Software\log\2016_11_28_18_34_56_install\RunSilentInstall log
Please attach the whole of that log file.
The information that the log contains is the same as the mentioned before, but anyway here it's attached.
We are working with Antonio Godos trying to solve this.
Thanks a lot for your help.
RunSilentInstall.log 269 bytes
Do you know where patrol normally creates the control file (when it works)?
Unable to create new control file. Windows error: 123
Windows Error 123:
The filename, directory name, or volume label syntax is incorrect.
1 of 1 people found this helpful
The problem was solved using the following:
Using the old fashion method to build the Patrol image, from the Patrol installer Wizard we created the image for PatrolAgent, as we know the final image is a ZIP file, let´s say image.zip.
Then we used the following command to uncompress and execute it
czip.exe -ux image.zip C:\patrol
The C:\patrol is the destination installation path
So at the end the Agent ran ok on the same Windows 2012 Server that was failing before,
Probably there is something different between the TrueSight image generation method and the old fashion method .
Thanks a lot for the help.
I was running into this (almost) exact same issue. I was trying to create a batch script to use via a Control-M job to upgrade Patrol Agents. The error message was exactly the same and I was using an install package created via BPPM CMA 9.6. Today I created a silent install the old-fashioned way (download the products you need, download the Installation utility, unzip them, create a silent install, distribute via tool of choice...), referenced that in my script, and it now works like a charm. Which is really a shame considering creating install packages became much easier using the CMA repository. I'd be interested to know the root cause of this.
I should note that I had no problem installing/upgrading agents using a CMA install package outside of our batch template script. I assume something is similar between blade logic deployment configuration and our batch template which causes the CMA install package to have issues finding the install.ctl file.
I opened a case on this and thought the answer might be useful. After extracting the CMA install package, in the "bmc_products\Install\instbin" folder you can find an "install.exe". In my case, we copied/pasted that executable two directories back in the "bmc_products" folder. In my script, we then executed the install as follows: install.exe -install install.ctl -userlog "C:\Program Files\BMC Software\log". I think the log location specified in the -userlog switch is arbitrary. When we specified the command as such instead of "RunSilentInstall.exe" in my script, the installation completed successfully with no "Unable to create new control file. Windows error: 123" error. I'm not familiar with BL, but I'd imagine if you did the same steps and specified the install command like I did, you might also have success and avoid having to manually create silent images the old way.