Tuesday, September 30, 2014

Openings For " Application Packaging " Tech M For the Location Chennai & Hyd ...For Schedule 09922688837( Kunal ) 

Monday, September 29, 2014

Checking return code from VBScript Custom Action


Recently I had the need to run a Custom Action in an older InstallShield Basic MSI project (version 10.5). The Custom Action would verify that a required application product was already installed – and at the correct version level. If either check failed, the Custom Action should return a negative return code and cause the installation to be cancelled.
I did not want to create the Custom Action using InstallScript since that version had the InstallScript Script Engine delivered as a separate MSI (ISScriptEngine.msi), and I wanted no additional MSI requirements. I decided on using VBScript for the Custom Action – but indicated earlier, I needed the VBScript function to return a value that can be used to abort the installation. I have used VBScript often in the past to retrieve CustomActionData and perform activities, but never had to need to issue a return code. Always I would create a VBScript Custom Action with the VBScript embedded in the Custom Action – but I could never could get this script technique to work.
Finally I created a VBScript Custom Action – but stored the VBScript in a .VBS script file.
Here is a snapshot of the Custom Action:
Note that I entered “CheckAgentVersion” in the Script Function line. Here is an extract of the VBScript:
Function  CheckAgentVersion
    Dim    sAgentVersion
       Const  cAgentBaseVersion = "11.01.0001.0000"
   
 
      'MsgBox "Running AgentLP CheckAgentVersion Custom Action"
       LogInfo "======== Running AgentLP CheckAgentVersion Custom Action =========="
       Set objShell = CreateObject("WScript.Shell")

       sAgentVersion = Session.Property("AGENT_VERSION")
       If sAgentVersion = "NOT FOUND" Then
        LogInfo "Agent was not installed!" 
        MsgBox "WARNING:  Agent was not installed!  Screen Capture Language Pack will abort!" 
        CheckAgentVersion = -1 
    Else 
           LogInfo "Agent was installed - and version is: " & sAgentVersion   
           If Eval("sAgentVersion > cAgentBaseVersion") then
            LogInfo "Agent installed is proper version!"   
              CheckAgentVersion = 0 
            LogInfo "======== Exiting AgentLP CheckAgentVersion with return code of " & nReturn
            Exit Function 
        Else
              LogInfo "Agent installed is not the proper version!" 
            MsgBox "WARNING:  Agent installed is not the most current version, so Language Pack will abort!      
            CheckAgentVersion = -1                   
            LogInfo "======== Exiting AgentLP CheckAgentVersion with return code of " & nReturn   
            Exit Function
        End If     
    End If     
End Function

Function LogInfo(msg)
   dim rec
   Set rec = Session.Installer.CreateRecord(1)
   rec.StringData(0) = msg
   LogInfo = Session.Message(&H04000000, rec)
   'LogInfo is a VBScript function copyrighted (@2011) by Ian Linsdell
End Function

By setting the return code to the function name, it will be correctly interrogated by the Custom Action. Granted, you should never pop up a message dialog unless you query the “UserUI” property to see if they are running full dialogs (i.e., not silently). But this should give you a heads up on how to accomplish this.
Also a couple of notes about the VBScript function:
  1. A co-worker Ian Linsdell wrote the slick sub-function that allows you to write directly into the MSI log file. If you use this function, please continue to keep his copyrighted comment!
  2. The MSI Property “AGENT_VERSION” is a result of a System Search entry that looks for the registry entry that confirms the Agent was installed. Obviously if the installation was not found, the default value of “NOT FOUND” would be in the MSI Property.
Regards
Hello…

Good Evening…

Hope you are doing well….

As you got great opportunity to work with KPIT (Thru Synova), Please find the attached JD with the below details….


Client – KPIT (Work location - HP, Electronic City)
Mode – Thru Synova at KPIT
Exp   - 4-7Years
Notice Period – Max 15Days
Interview – F2F This Saturday


Requirement: Application Packaging.




If you are really Interested please send me your Updated CV ASAP with the below details….

Name                        :
Total Exp                  :
Relevant Exp            :
Current Organization:
CTC                           :
Expected CTC           :
Notice Period            :




Thanks & Regards,
Sapna K
CBSI India Private Limited (SYNOVA)
Vakil Square,Bannerghatta Road,
Bangalore  
India|US | Brazil | China I Hong Kong  I Singapore
HI All,
Application Packaging openings in Bangalore

For KPIT interview sedule( Client "HP" )call to +912030213131
This is Manisha Rai from Modern Ballistis Solutions 

Experiene - 3-5 yrs 
Location- Banglore 
Skill - application packaging and app v 

Note - Apply only those candidates who an join in 20-25 days and able to attend the face to face interview 


Warm Regards, 
Manisha Rai 
Technical Recruiter 
Modern Ballistic Solutions 
:8470041402. | Email  : manisha.rai@m-b-solutions.com 
Duties and Responsibilities

•    Application packaging, creation of MSI, re-packaging EXE and other installer formats to MSI. 
•    Integrate packages into LANDesk for deployment
•    Maintain and support highly stable packages which conform with our standards. 
•    Perform validity test and schedule deployments to Windows 7 workstations. 
•    Virtualize applications using App-V and deploy and maintain the virtualized instances. 
•    Perform software distribution and patch management to Windows desktops, laptops and Citrix/Terminal servers. 
•    Create and maintain documentation for testing and validation. 
•    Provide post-implementation support, identify root cause and devise strategic solutions to problems. 
•    Work with vendors to analyze and troubleshoot solutions. 
•    Windows Server 2008, 2003 and Windows 7 workstation technical support experiences with advanced knowledge of Windows registry, file and folder security, local/domain user security, and operating system troubleshooting.   


Drop U r Resumes manasa@sprvtec.com 
Job Description 

Job Requirements 
 Qualified applications for the role of Software Packager will need to have the following the following technical and administrative skill: 
 Experience with Application installation and desktop configuration and navigation the registry, Windows file systems, networks 
 Experience with understanding and documenting application requirements and dependencies 
 Distributed environment & enterprise-grade applications 
 Familiarity with working in virtual environment such as VirtualPC, Hyper-V, VMWare, etc. 
 Experience with scripting using a combination of VBScript,WiseScript, InstallAware and/or PowerShell 
 Ability to follow a strict workflow process for QA & User Acceptance testing 
 Experience with SharePoint and web-based issue tracking tools 
 Must be able to read & write in English 
 Ability to work in a team environment & to take direction 
 Experience with virtualizations technologies Microsoft App-V and/or VMWare ThinApp. 
 Compatibility testing for Win7 using AppDNA,Administudio compatibility solver. 
 Excellent troubleshooting skills for App-V,MSI applications. 

Send Resumes to nancy@globalisource.com 

How to disable rollback files in Config.msi folder


Sometime back I came across a question where the SQL Server uninstallation was failing because there was not enough space on the drive to create the .rbf file.
Error 1307. There is not enough disk space to install this file:
C:\Config.Msi\filename.rbf
As evident from the error message, SQL Server installer file was unable to create a Rollback fileon the C drive. These .rbf files gets created depending upon whether the Windows Installer (.msi)file needs to rollback its actions if cancelled in between. By design these files are created in theConfig.msi folder, which is always located on the drive hosting the Operating System (%systemdrive%). There is no option to change the Windows Installer to generate the .rbf file on any other drive.
The only workaround to this issue is to stop the Windows Installer from generating any rollback files. The below steps needs to be followed to stop Windows Installer from creating rollback files.
Navigate to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer\DisableRollback in Registry Editor and create a new DWORD value called DisableRollback and set its value to 1.
After creating this value, the rollback files will not be created for any msi files. Since the post did not get updated after my response, I assume that the issue got resolved because of this workaround.
Hi Folks


Investigating self-repair

Another common question is, “Why does Windows Installer run every time I restart my system/start my application?”
This behavior is part of the resiliency or self-repair feature of Windows Installer. (This question has been answered many times in many places, but not with pictures.) When MSI fails to find a resource it needs, it displays a configuration dialog box similar to the following:
MSI self-repair progress bar
To see details about the missing resource, open the Event Viewer (Control Panel > Administrative Tools); the details are in the Application section.
Event Viewer
The details of the repair are the MsiInstaller entries in the Application section of the event viewer.
events in Application section
Double-clicking the warning event reveals the event properties; the details of the event list the product code, feature name, and component code involved, as well as the missing resource.
event details
(A previous tip hinted at how to get more information about a product or component, given its GUID.)
I’m not aware of a way to disable self-repair, short of disabling advertised shortcuts, extracted COM information, Extension-table file associations, etc.
A follow-up question is how to log self-repair operations, since there’s not an explicit msiexec command to which you can add the /L switch. One uninviting method is to set the system-wide Logging policy, which creates a debug log in the Temp folder for each MSI operation. A somewhat less uninviting option is to set the system-wide Debug policy (to 7), and then useDebugView from Sysinternals to view the “live” debug log.
DebugView MSI logging
Hi Folks ....

U Want to Any Help Regarding Installshield just live chat For any technical R Any thing Else  Please Find Below Url;-



http://www.all-about-software-applications-repackaging.com/search?updated-min=2011-01-01T00:00:00%2B05:30&updated-max=2012-01-01T00:00:00%2B05:30&max-results=29





Regards,
Naresh
+91-9502030090




Daily Pageviews

Blog Archive

Contact Me

Name

Email *

Message *

ABOUT ME

My self NARESH DHUVURU . I'm from Thirupathi. i'm having 4+ years of experience on Application Packaging . . . I HOPE MY BLOG WILL HELP YOU TO SWITCH .........

For queries:- nareshdhuvuru@gmail.com

Facebook - bkn.annur@gmail.com

linkedin - nareshdhuvuru@gmail.com

mail - nareshdhuvuru@gmail.com

Popular Posts