I have a windows VM and there is already Mule EE server setup using the amc setup command and able to see the server on Runtime Manager as Running.
Now when i install another Mule EE on the same Windows VM (different folder) , when i say mule.install it says
"Unable to Install MULE EE Service The Specified Service already exists (0x411)"
Anything to consider for installing multiple server on same Windows VM ?
The problem is not that you are installing to another directory, but that both instances are trying to use the same Windows Service name. The default is mule.
Before trying to install the second instance you have to edit the conf/wrapper.conf configuration file and change the service name it will try to use:
wrapper.ntservice.name=mule2
Reference: https://help.mulesoft.com/s/article/How-can-I-create-a-uniquely-named-Windows-service-for-each-Mule-instance
Related
I am testing the azure file share with SSIS hosted on Azure VM. However, I am facing an issue while running the job.
Package execution through Visual Studio is successful
Package execution through catalog also is successful
Package execution through the Job is FAILING with the error The File Name "\.windows.net<FolderName>\file.csv" specified in the connection was not valid
I tried running the job with the proxy account having access to the Azure share folder (Same account used to run the package), however it failed with the same error.
Both UNC and as a mapped drive was tested.
Any suggestion or advice on this will be highly appreciated.
Thanks in advance.
Try giving read/write permissions (For the Azure share folder) to the SQL Database Engine Service account NT SERVICE\MSSQL$<Instance Name> and NT SERVICE\SQLSERVERAGENT (Where <Instance Name> should be replaced by the installed instance name):
Configure File System Permissions for Database Engine Access
Also, feel free to read more about SQL Server service accounts in the following documentation:
Configure Windows Service Accounts and Permissions
I'm running an MS Access database with VBA code that has libraries for Microsoft Office 2010. Currently, there are users that are upgrading their machine to Windows 10 running Access 2016.
When the database is opened on a new machine running Access 2016 the libraries for the Outlook changes to 16.0.
When I try to open the file in the old Access 2010 environment, I run into this error:
Missing msoutl.olb.
Is there a way to make the database backwards compatible?
It sounds like the users share the same frontend hosted in a network folder.
If not done already, split the database to have a single shared backend database file. Then, to avoid your issue, distribute a separate copy of the frontend to each user's workstation.
On the workstation, let the user launch the frontend using a shortcut that runs a script to always keep the frontend current. This method is described in detail in my article:
Deploy and update a Microsoft Access application with one click
in my alfresco-global.properties file it says:
db.url=jdbc:postgresql://localhost:5432/${db.name}
I want to know how to access this database in the browser?
The default PostgreSQL client application is psql. If you can't install this or if you want to use a GUI client, the PostgreSQL community maintains a list of GUI clients.
Every client either asks you for credentials or will present you a form where you can enter them.
The JDBC URL from your question is
jdbc:postgresql://localhost:5432/${db.name}
My guess is that db.name is equal to alfresco. So the complete JDBC URL would be
jdbc:postgresql://localhost:5432/alfresco
If you have installed Alfresco only your local computer, this would be the JDBC URL to use with a client that uses JDBC. If you have installed Alfresco on a different computer, you would have to replace localhost with the host name of this computer.
To connect to alfresco data base you can use any Postgresql client, by the way, alfresco install pgAdmin client.
To use this client you shoud open {alfresco_install_directory}/postgresql/bin/pgAdmin3, add new server and type database credentials(host, port ...) from alfresco-global.properties.
Edit
This is an example of configuration, you can find all what you need in alfresco-global.properties.
In case you have made the default installation(postgresql), you cant.
If you have switched the database to mysql you could use something like php admin or similar. Hope it helps.
I am trying to upload a File onto the Sharepoint using a File System Task. When I run the package manually, it succeeds.
However, after I deploy it and run via SQL Agent Job I get the following error:
"The network path was not found"
Can you please help?
When you run it locally you are using your windows credentials to authenticate through to the sharepoint site. A sql job will not use your windows credentials. You can setup a proxy account, but make sure it has permissions to the sharepoint site as well.
I'm starting out on creating PowerShell scripts for my company. I'm new the the platform and I plan on creating scripts for AD tasks
If im creating scripts for AD should I be able to run the script on any machine in the domain or does the script have to be run on a machine that is the active directory server?
I don't mind running the script on the server but for testing and creating I would rather run it on my desktop for development and testing
any incite on this?
Assuming you're using the activedirectory powershell module, then the only requirement is that the machine you're running the script on has this module installed.
This module is a windows feature "Remote Server Administration Tools > Role Administration Tools > AD DS and AD LDS Tool > Active Directory Module for Windows Powershell."
On a server OS, this can be simply added as a feature through Server Manager
On a client OS, you will first need to install the Remote Server Administration Tools (RSAT) from Microsoft download centre. Once that is installed, you then install the feature through "Turn Windows Features on or off"
Additionally, if your script has a dependency on this module, you can also place the following line at the top of your script
#Requires -Module activedirectory
Then if you try to run this script on a machine without the activedirectory module, it'll produce an error saying the module is missing. It'll also cause the activedirectory module to be imported if it's not already been imported which is useful on powershell. Refer to about_Requires for more information on the #Requires statement