Installscript - Deleting sites from IIS uninstallation - installshield

I am using Installshield 2012 Spring Edition. I have created a setup project. While uninstallation, I need to delete the files from IIS and stop the services automatically. I have tried using some installscript codes. But, I am getting this error:
"error 2762: cannot write script record transaction not started"
Can anyone tell me, is there any other method to do this operation.
Thanks in advance.
Regards,
Naren.

When are you sequencing your custom action? Also what type is your custom action?
If you are trying to execute a deferred custom action then it needs to be sequenced between InstallInitialize and InstallFinalize.
Could you provide a snippet of your install script?

Related

SharePoint 2019 Installation problem in SharePoint Workflow Manager

I am facing issue "Downloaded file failed system verification and may have been tampered with" while installing new Work flow manager. I have tried through Web Platform Installer and also tried by offline webpicmd but still issue is there.
I am attaching screen shot below:
Please check this link https://fixingsharepoint.blogspot.com/2021/02/download-file-failed-signature.html. I found solution in it.
All you have todo is get the Workflow_Manager.msi file and from powershell prompt (in the same directory you have Workflow_Manager.msi file) and try this
./Workflow_Manager.msi IACCEPTEULA=yes WEBPI=1

Error connecting to NetSuite Sandbox from within Eclipse

I am using Eclipse 2020-06 with NetSuite 2020.1 IDE, and getting the following error when attempting to deploy a simple SuiteScript project with just one User Event Script.
Some background on successful tasks:
Within Eclipse, I have added a domain of XXXXXX-sb1.suitetalk.api.netsuite.com
When adding my account to this domain within Eclipse, the username/password is accepted
The Eclipse IDE then allows me to manage authentication type for each
role assigned to my account in NetSuite.
I have left each role's Authentication Type as "User Credentials"
On the NetSuite server, I have followed the instructions for installing the SuiteCloud Development Framework (https://4583703-sb1.app.netsuite.com/app/help/helpcenter.nl?fid=chapter_4702629975.html)
Some comments on my Eclipse Environment:
This is a brand new Eclipse download with only NetSuite IDE added
There is only one project in the Eclipse workspace, and that SuitScript project contains just a single auto-generated script with no modifications/references
I've repeated this step multiple times with different projects, and always get the same error message referencing the same application id of "22804373-084A-49DC-8622-4DECD6ED07E7"
So this clearly seems to be a server-side issue.
My questions:
This applicationId is clearly derived from the NetSuite server, any ideas where it is coming from?
Other ideas?
Thanks in advance,
Randy
Try an Account Customization project instead of a SuiteApp which requires an application id

Problems Using NET Framework to access Windows Registry

i'm using vb.net 2010, .net framework 3.5 and the procedure and the exception I get, are as follows:
I've been reading about manifest, and this and that, but what it seems to me is that i'm still missing something, will anybody kindly give me any suggestions?
Thanks in advance!
You need to be elevated to modify this key. The process that performs these registry modifications needs to run as admin.
Use the requireAdministrator option in the manifest. Or start the process using the runas verb.

Wix Webapplication: How do I add an extension without replacing all existing mappings?

I'm trying to add a .plan extension to our IIS 6.0 website through WiX. I'm using
<iis:WebApplicationExtension CheckPath="no" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST,DEBUG" Extension="plan"/>
Although this is replacing all of the existing application extensions, which is not the behaviour that we want. Is there a way to simply add .plan? We would like to avoid using the Wildcard if possible as we're not sure how it will affect the rest of the site. I don't think that APPCMD is available on our 2003 server either.
Any suggestions would be greatly appreciated :)
Unfortunately we didn't find a way to do this cleanly using the iis:WebApplicationExtension in WiX.
We found this post http://blogs.msdn.com/b/david.wang/archive/2004/12/02/273681.aspx that provides a VBScript for adding ScriptMaps. We edited the script to only execute the HandleListOps function (with the relevant params) so that we didn't get any issues with WScript. We then call this from a CustomAction in WiX, with the vbs file added as a Binary file.
We're aware that running vbscript custom actions from within an installer isn't ideal, but luckily we're not distributing the application externally and is only going to be used on an internal website, so the target server environment is reasonably well known.

How to debug custom c# action that executes sql

I am running custom action that suppose to execute some function in provided dll.
this function connects to sql db and do some select with return, but i cannot see the return value.
How can i debug this function in dll, or check if it is really executed.
I've use C++ custom action DLLs, so I'm not entirely sure how a C# custom action DLL differs. However, I usually use the method Ondrej mentioned: logging to the MSI log file and/or message boxes that pause the custom action execution so I can attach to the process via Visual Studio.
Are you familiar with how that is done?
InstallShield has native SQL script handling for most of your needs. This will automatically give you a lot of logging in the MSI log file. However returning result sets is one thing it doesn't do.
The best thing to do is write your managed C# custom action using Windows Installer XML (WiX) Deployment Tools Foundation (DTF). This builds custom actions that appear as C++ custom actions to the Windows Installer and is fully compatible with InstallShield.
Inside of a DTF custom action you can use session.Log() to record useful debugging information in the Windows Installer log file. You can also attach a debugger to the custom action and step through it if you want. See the following for more information:
Deployment Tools Foundation (DTF) Managed Custom Actions

Resources