Software Deployment

First step is try registering the file manually:
regsvr32 filename.dll

Not all dll files can be registered...

it the dll is not getting registered manually by regsvr32 then it means the dll cant be registered. and to ensure the error free installation of the dll you need to ensure that the dll is not marked for registring in your package.
to ensure that you go to selfreg table and make sure that the dll file has no entry in this table.

Hi,

why are you "snapshotting" SAP??

SAP has nice Tools to customize the SAPGUI and then deploy it with whatever Tool (sapsetup.exe /p "customfile")

Anyways, if you set the ""Enhanced File and registry Key association" switch during your snapshot, the following might occur:

This feature registers every self-registering .DLL found in the capture. If you have a self-registering .DLL that you know is not set to be registered during the installation, then you might not want to use this feature because it could cause the repackaged installation to not function properly.

if your dll is one of them, just delete that row out of the selfreg table

regards
Martin

I would like to use the SAPadmin tool but I need to deploy the application using group policy. Therefore the package has to be an .MSI.

Unless SAPadmin tool can also deploy over the network. Is that possible?

Thanks in advance.

Configure your SAP GUI installation using SAPadmin then create a MSI wrapper to execute the sapsetup.exe installation.

Thanks for all your help. I have created the package now using SAPadmin. Here is command the launch my package;

\\server\Netinst\SapSetup.exe /p:"sap 4.6 d" /install /noDialog /silent

Now my only question is how do I create a MSI wrapper using WPS? I have used the ones that Microsoft created but I have never created one myself. Your help is greatly appreciated.

Thanks.

You could call a vbscript with function Wrapper, ex. bellow
(Place the msi in the same location as SapSetup.exe)

Function Wrapper()
Dim WSHShell : Set WSHShell = Nothing
Set WSHShell = CreateObject("WScript.Shell")

Dim InstallCmd : InstallCmd = Session.Property("SOURCEDIR") & "SapSetup.exe /p:""sap 4.6 d"" /install /noDialog /silent"

'Run command and wait for the process to End
HandleError = WSHShell.Run("""" & InstallCmd & """", 1, True)
If HandleError <> 0 Then
Wrapper = 3

Exit Function
End If

Wrapper = 0

Exit Function
End Function

Hi WiseGuyinNewYork,
have you got a look at WIWW to do the wrapping job? See:
http://itninja.com/link/timbuktu-pro5
Regards, Nick

I am sorry but this SAP installation is giving me lots of headache.

As I mentioned above, I have created the package using SAPadmin, but when I run it from the command prompt, it starts and errors out with the message "script named "sap 4.6 d" not found or execution permission missing, Installation aborted."
Although I can see the package in the sapsetup.exe.

I can run the setup directly from sapsetup.exe but not when I run it using a path. Which I need to do in order to wrap it in MSI. BTW I am learning so much from you all.

Can anyone tell me what I am doing wrong.

Thanks in advance.

Hi WiseGuyinNewYork,
Sounds like a path error to me.
Have you tried with the path like this?
\\server\Netinst\SapSetup.exe /p:"\\server\Netinst\sap 4.6 d" /install /noDialog /silent
or:
SapSetup.exe /p:"sap 4.6 d" /install /noDialog /silent
Is one of these working?

Regards, Nick

hi..

When installing my application it's throwing error like " An error occurred while registering the file 'c:\program files\Common files\Microsoft Shared\DAO\DAO350.DLL"



Running "Regsvr32" in cmd as an admin, its sucessful in registering the dll but while installing same application afer un-installing, it's throwing same error.



I want a permanent change in the aplication so that when re-install it should not through the same error.

All DLL files required for the application to run is present in source file as a " .CAB" format so how can i proceed to avoid throwing same error.

I am using windows 7-32 bit

I'm pretty sure there's a merge module for DAO 3.5. You should use this.

can u please say in brief.... i am not getting it.

have a read here and download the merge module in this thread, then include it in your package (under 'merge modules' or 'redistributables')

PJ

Before any of that, read and digest Phil Wilson's The Definitive Guide To Windows Instaler. You will struggle with packaging without knowing the fundamentals. To even contemplate messing with a package without knowing what a merge module is...well, I edited out what I was going to write...