|
From: "Rob Berendt" <rob@xxxxxxxxx><midrange-l@xxxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
Date: 08/05/2019 12:43 AM<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: ACS problem
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
Glad you found it.
I've found the Windows 10 search box at the bottom left quite
invaluable. I type in the file name, or even the first few
characters, and it often finds it lightning fast.
Frankly, I never use the Start button to start anything but find the
Power button to put it into sleep mode, or restart it.
I want to start Word I just type in Word in the search box. Same
for PowerPoint, Excel, ...
For iACS not only do I have that pinned I can type in acsl in the
search box and pick the appropriate one. In my case I would always
be picking acslaunch_win-64.exe
You can click on the file and pick Open File Location if you want to
find where you stored it (and where you might want to put your update).
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf
Of Bob Cagle
Sent: Tuesday, May 7, 2019 10:28 AM
To: Midrange Systems Technical Discussion
Subject: RE: ACS problem<midrange-l@xxxxxxxxxxxxxxxxxx>
Finally got this fixed this morning. Still not exactly sure what
the issue was, but I don't think it was the ACSconfig.properties file.
I found that there was an IBM\ClientSolutions product directory in
the C:\Users\Public directory. I deleted that and reran the
install_ACS script again. Voila, everything started working again.
Thanks
Bob Cagle
IT Manager
Lynk
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf
Of Steinmetz, Paul via MIDRANGE-L
Sent: Monday, May 6, 2019 4:14 PM
To: 'Midrange Systems Technical Discussion'
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>#################################################################################
Subject: RE: ACS problem
Bob,
Check your ACSconfig.properties file, especially, example 4.
Below is my example.
We deploy from a central file share.
# Example 4 - local configuration on portable media (like USB drive):
# com.ibm.iaccess.AcsBaseDirectory={PRODUCTDIR}/config_directory
# Since the path to the portable media will vary depending on the
system where # it is being used, this setting allows the
configuration to be relative to # the product files. In this
example, the {USER} keyword was intentionally not # specified so the
configuration on the USB drive would be used by the user of # the
USB drive, regardless of the user ID.
#
com.ibm.iaccess.AcsBaseDirectory=C:\Users\Public\Documents\ACS
#
# com.ibm.iaccess.AcsBaseDirectory={PRODUCTDIR}/config_directory/{USER}/
#com.ibm.iaccess.AcsBaseDirectory=C:\Users\Public\Documents\ACS\IBM
\iAccessClient\Emulator
# Automatically Import a Configuration:users:
#
# The following properties may be used to automatically set up a
configuration # for new users or to update a configuration for existing
com.ibm.iaccess.autoimport=\\yyyyyyy.xxxxx.com\ibm_acs_base$questions.
\Current\acs_bak.zip
com.ibm.iaccess.autoimport.version=1
# See the GettingStarted document for more details.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
Behalf Of Bob Cagle
Sent: Monday, May 06, 2019 4:58 PM
To: Midrange Systems Technical Discussion
Subject: ACS problem
Been searching for an answer to this problem all day, but am unable
to find anything.
Key facts: Using latest version of Windows 10. ACS is installed
from an on-prem network file share. Running i7.3.
This morning, a user informs me that ACS is not working. She is
getting the error "MSGGEN036 - There was a problem accessing the
user product directory".
I'm fairly certain this is to related to us moving her files from a
local prem private file share to her Office 365 personal One Drive.
We did that last Thursday, and on Friday when she started ACS batch
session, it wasn't able to find her individual session files. I had
to repoint her batch session to the new location, and after that was
done, she was able to work all day Friday without issue.
But this morning, we can't even get the main GUI to launch. I've
uninstalled, rebooted and reinstalled, multiple times. Tried 32 and
64 bit. Even tried reinstalling from a different network location.
I still get this error.
I'm sure somewhere it's most likely still pointing to the local prem
file share which no longer exists, but I don't know where that
reference is in order to fix/delete it.
Any suggestions?
Thanks
Bob Cagle
IT Manager
Lynk
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
link:
Help support midrange.com by shopping at amazon.com with our affiliate
https://amazon.midrange.comlist
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxxquestions.
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
link:
Help support midrange.com by shopping at amazon.com with our affiliate
https://amazon.midrange.comservice.
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud
______________________________________________________________________
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.