Re: [AD] QM Release Notification (3.4-7)

32 views
Skip to first unread message

Kevin Powick

unread,
Sep 13, 2016, 3:35:40 PM9/13/16
to OpenQM, mvd...@googlegroups.com
I had a similar problem back in March, so this is not a new situation with QM 3.4.-7, it's a Windows permissions issue.

The QM docs state that each user logging into QM launches a new QM.exe process on the server, which runs with the permissions of that user account.  So, for starters, this means that anyone wishing to log into QM requires the Windows Local Security Policy of the server hosting QM to allow "Log on Locally".

Your "work around" is the correct approach.  Just create a new Windows user group called "QM Users", with the appropriate permissions, and add the users necessary to that group.  

--
Kevin Powick


On Tuesday, 13 September 2016 14:14:21 UTC-4, Jose Gabino Arocas wrote:
Hi Martin,


Yes it helps, the error in windows is "0xc000015b" ("The user has not been granted the requested logon type at this computer") and the LogonType is "2" wich is interactive logon. And the users of group "domain users" don't have permissions to "interactive logon" only to "network access". I test with another system (W Standard) and QM 3.4.6 and the login with a "domain user" in QM is with the "Logon Type 3", which is Network logon. I think there is a difference between 3.4.6 and 3.4.7 or 3.4.7 on Essentials. Now, the workaround is to add users like "Printer operator" which is less than "administrator" and they have permissions to "interactive logon" waiting for a definitive solution.

El martes, 23 de agosto de 2016, 10:46:52 (UTC+2), Martin Phillips escribió:
This is an automated email. Do not reply to it.

Release 3.4-7 of the QM Multivalue Database is now available for download from www.openqm-zumasys.com/downloads or www.openqm.com/downloads.htm.


Ladybridge Systems

===== RELEASE CONTENTS =====

This release introduces a pure Java version of the QMClient API, removing the need for the Java Native Interface which required different versions for each supported platform. The old JNI versions will continue to be supported for at least one year.

The COPY command has been extended to allow record ids to be forced to either upper or lower case when copying items from a directory file on a case insensitive file system to a case sensitive file.

When using the CREATE.FILE command to create an element of a multi-file, the INHERIT.MFILE.PATH mode of the OPTION command can be used to make the default location of the new subfile the same as the default subfile.

The RPL.STATUS command can be used to display a summary of the replication system status.

The SED editor now has a SCROLL1 option to control scrolling from page to page.

The SED editor can take a sequence of edit commands from the data queue.

The SELECT.DIR command can be used to build a select list containing the names of files or subdirectories in a specified directory.

The TERM command now supports setting the default printer page dimensions.

For improved compatibilty with other multivalue products, the query processor COL.HDR.SPACE keyword inserts a blank line under the column headings in a tabular report.

The OPEN.FAIL.ZERO.FVAR setting of the $MODE compiler directive causes a failed open to set the file variable to zero instead of unassigned.

The QMBasic SADD(), SCMP(), SDIV(), SMUL() and SSUB() functions have been extended to support non-integer values.
Reply all
Reply to author
Forward
0 new messages