|
Jesse joined
IMR in 1997 as a quality assurance analyst. He served as the QA lead for
several releases of Alchemy, including Alchemy Digital Dashboard and every
release of AWS through R6SP3. In 2000 he joined Technical Support, taking
calls, training internal and external customers on Alchemy and AWS, and
providing onsite support as required. He was named the Technical Support
Manager in April 2002. Prior to joining IMR, Jesse served in the United
States Marine Corps for seven years as a Spanish interpreter and drill
instructor.
Jesse serves on the AIIM Rocky
Mountain Chapter Board and the KMCI Denver Chapter Board. He also sits
on the CompTIA CDIA+ Cornerstone Committee, the AIIM XML and Metadata
working group, the ARMA Email Management Task Force, the ARMA 2003 conference
committee, and the ASQ Denver Software Forum 2002 planning committee.
He will also be speaking at Xplor 2002 on "XML and Metadata: A Standards-Based
Approach".
In 2001, Jesse participated
in the rewrite of the CompTIA CDIA+ test as a subject matter expert. He
has been awarded the AIIM Master of Information Technologies designation
and is an ASQ Certified Software Quality Engineer.
Jesse is married, with no
children. He and his wife live in Denver with their three dogs, one cat,
and a horse. He completed his B.A. in Political Science in 2001 at the
Metropolitan State College of Denver and is pursuing his MBA at Regis
University. In his spare time Jesse is a gourmet cook and chocolatier.
Tips
& Tricks
Running
Check Fix on a database in 7.3 Premium
The database cannot
be under Server control when you run the Albatch /check /fix integrity
check. However, the Server service must be running in order to get
a license. Therefore, you must 'Remove' the database from Server control
rather than 'Stopping the Service' to run Check Fix on a Premium database.
Database
Folder
We recently discovered
an anomaly with AWS and single-user Alchemy Build.
The AWS User only needs READ permission to the database.
However, with single-user Alchemy Build, if the database has just READ
permission for the AWS User account, and an AWS user accesses the database
before the Build user, the database will open read-only in Alchemy Build.
If the database has READ/WRITE permissions, Alchemy Build is unaffected.
If the database is placed
under the control of Alchemy Server in an Alchemy Premium environment,
then AWS needs only READ permission to the database.
AWS,
Alchemy Server, and Permissions
In order to configure
AWS and get it to successfully run with Alchemy, the proper folder and
file permissions need to be set up. There are at least
two folders on the server where AWS is installed that the administrator
will need to adjust permission (three folders if the databases reside
on the AWS server, as well). The type of error generated,
or specific behaviors will indicate where permissions are not set correctly.
AlchemyWebServer
Folder
The AWS User account
or the group to which it belongs must have READ and WRITE access to the
PtTemp folder below \inetpub\wwwroot\alchemywebserver.
The PtTemp directory is where the individual user sessions are created
when a user accesses AWS. Within the individual session
folder, AWS converts the document coming from the Alchemy database to
a format that can be displayed within the user’s browser.
When the AWS User account
does not have READ and WRITE access to this folder, the user will click
the database link, and AWS will appear to hang (lock up).
On the AWS server, IIS will also hang, and the administrator will be forced
to either reboot the server or use the iisreset command.
Restarting the IIS service through the Services snap-in usually will not
work.
Alchemy generates the
following error code in the AlchemyWebServer log: E06D7363.
AWS
Log Files
The AWS User account
also needs WRITE access to the \winnt\system32\logfiles folder.
There are two logs that AWS writes to: AlchemyWebServer
and W3SVC.
If the AWS User account
doesn’t have WRITE permission to write the logs, AWS will fail when
the first user attempts to access a database after midnight.
If security is an issue,
and the AWS administrator does not want the AWS User account to have write
access to the system folder, the PtServer.ini can be used to define an
alternate location for the logs.
Comments or questions regarding this newsletter can be sent to
Support@IMRGold.com. Please type "Newsletter" on the subject line.
Alchemy Training:
Alchemy Training Schedule
|
