Broadcast Tools ADMS 44.22 Wartungshandbuch PDF herunterladen (Seite 287)

Troubleshooting 287

Reviewing Event Logs Outside of XStudio

Since XStudio event logs are text files, you can use virtually any text editor or text file viewer to review

the information for any of the available event log files, which are stored in the XStudio application folder

using a naming conventions of:

yyyymmdd_XStudio_EventLog.txt (main application event log)

yyyymmdd_InvMgr_EventLog.txt (InvMgr event log)

yyyymmdd_InvMgr_MaintThread_EventLog.txt (InvMgr maintenance thread event log)

yyyymmdd_XEngine_EventLog.dmp (XEngine event log)

The "yyyy" is the year, "mm" is the month and "dd" is the day of the month for which the event log was

created.

A handy alternative to using a standard text editor is our custom Event Log Viewer application, which

provides enhanced features for sorting, grouping and filtering of event log data. Visit our web site for

details on downloading and using this free utility.

6.7 Vista, Windows 7 & WIndows 8 Notes

With the introduction of Windows Vista and subsequently the release of Windows 7 and Windows 8

and other later operating systems, Microsoft added a significant amount of additional security to these

operating systems.

Generally referred to as UAC (User Account Control), the sum of these changes dramatically affect

named users who might be categorized as "standard" or "general" users. Areas that previously had

been quite open, allowing these users to modify, create and delete items like files and registry entries

are now protected as default. Users with standard rights and privileges on these systems are now as a

default prevented from making changes in such areas as the Program Files folder, the Windows folder

and in the Windows registry area known as HKEY_LOCAL_MACHINE.

XStudio does not use the Windows registry during normal operations. The only

information stored in the registry is created when installing XStudio and is used

if you later decide to remove the software from the system.

In addition, Microsoft published numerous guidelines and usage information regarding these changes.

Some of the guidelines would cause applications who require the end-user to be able to modify

preference settings, etc., to place files in several locations on the PC. While these changes do

enhance the overall security of the operating system, having files and information for a specific

application spread all over the system in places not intuitive or easy to find creates a significant support

burden for IT managers and the application vendor.

Over the years, we have chosen to try to keep all of our application's files, including those that store

preferences, files containing run-time information like exception logging and activity detail, and small

database files, in one location for ease in troubleshooting and housekeeping.

For these reasons, our applications are generally placed in a folder other than the Microsoft-

recommended Program Files folder. As a default, these other folders historically have been "wide

open" in the sense that any user could read, write and modify files.

However, depending on how tightly-secured a system is when running Vista or a later operating

system, issues may arise that relate to user rights. The following points may assist you in locating

problems with XStudio when running one of these operating systems and the user reporting issues

does not have administrative privileges.

1. Make sure that user having trouble with XStudio has read, write, modify and delete

privileges in the folder in which XStudio is installed. These privileges might be assigned to

1 2 ... 282 283 284 285 286 287 288 289 290 291 292 ... 361 362

Kommentare zu diesen Handbüchern

Keine Kommentare

Broadcast Tools ADMS 44.22 Wartungshandbuch Seite 287

Kommentare zu diesen Handbüchern