ACCELERATING ANSWERS TO YOUR QUESTIONS!

1. What is OGwin?

OGwin is a complete accounting package for operators and non-operators. Designed by specialists actively engaged in the oil and gas industry, OGwin is a user-friendly, menu-driven database management system.

2. What is OGsql?

OGsql is the next stage of the OGwin application. It replaces the Pervasive/Btrieve database backend with Microsoft® SQL. This provides many benefits to users: Intuitive 3rd party access to your data, additional transaction protection with rollback/re-start, and increased scalability.

3. What are the minimum requirements needed to run the OGsql program?

Sample Minimum Hardware Requirements

OGSQL is a very robust application that will perform correctly on almost any platform that meets the requirements of the underlying operating system and Microsoft® SQL Server® 2005. OGSQL performance is dependent on many variables such as:

- Size of database
- Number of concurrent users
- Level of OGSQL processing
- User expectations

These combined with external forces such as other applications make it impossible to create a single minimum hardware recommendation. Even with all of these variables, OGSYS recommends the following minimum configuration for an OGSQL installation with a database size of less than 5GB, 10 or less concurrent users and no other significant applications on the server. If your anticipated usage of OGSQL is less or more than the above, please contact us and we will provide a tailored hardware recommendation based on your needs.

Server:
- Dual Core Processor at 2.5GHz
- 3GB RAM
- Physically separate disk volumes for the OS and SQL Database
- 100Base Ethernet network [Certified]
- Windows 2003 Server, fully patched
- Microsoft® SQL Server® 2005 Standard Edition (OGSQL is incompatible with earlier versions)

We also recommend the following minimums on workstations accessing the OGSQL application:

- Dual Core Processor at 2.0 GHz
- 2GB RAM
- 100Base Ethernet [Certified]

Any increase in these specifications will boost performance for OGSQL. There are some specific areas that will provide more benefit than others:

SQL Database located on a RAID volume that combines redundancy and increased performance (i.e. RAID5, RAID1+0 or RAID0+1)

Additional/Faster Processors/Cores at the server. When combined with a sufficient edition of SQL Server, OGSQL will experience a significant performance boost in multi-tasking scenarios.

GigE (1000Base) network.

Additional memory on the server. When combined with a 64bit server operating system and a sufficient edition of SQL Server®, the additional RAM will reduce pressure on the disk system.

As any SQL DBA will tell you, there are myriad techniques to boost performance of a SQL based application. In our experience, the above list has provided the most noticeable performance increases with the least amount of complicated database configuration changes.

4. What databases do you support?

OGwin
The OGwin product requires the Pervasive/Btrieve database engine. The version of this engine must meet the requirements of your particular environment. For example, if you have Windows® Vista, Windows® 7 or Server 2008, you will require Pervasive v10 or later.

OGsql
The OGsql product requires Microsoft® SQL Server version 2005 or greater. All editions of Microsoft® SQL Server are supported, subject to licensing and performance concerns.

5. What versions of Windows® do you support?

For the Server component (if used): Windows® 2003 or greater, all editions. For the Workstation component: Windows® XP Professional*, Windows® Vista* (Business and Ultimate), Windows® 7* (Professional and Ultimate editions in 32 bit or 64 bit configurations). Please note: Home versions of the Windows® operating system are NOT supported.

The OGWIN application is 32-bit in nature. While compatible with 64-bit Windows® Operating Systems, OGWIN will operate under WOW64.

6. I am Running a 64 bit Configuration of Windows® 7, does OGsys suggest any
configuration changes to the Windows® 7 Enviroment?

There are 2 Recommended Changes:

• Disable the Windows® Firewall for your enviroment (I.E. Public, Home, Domain, etc.), or
• Modify the Exceptions List to allow traffic: For OGWIN - Ports 3351 (Betrive). For OGSsql - Ports 1433, and 1434 (MS SQL Server®).

7. Are you Macintosh® compatible?

Currently Macintosh® is not supported.

Clarification: While it may be possible to run OGsql under Macintosh® hardware (i.e. using Bootcamp, Parallels, or some other virtualization technology) it is not supported by OGsys.

8. Do I need a server to run OGsys?

It depends.

For multi-user environments (OGsys accessible from more than one machine), a server is required. For single station users (OGsys installed on only one machine), a server is optional.

9. What type of training do you offer?

Our primary training is offered in live, instructor-led classes at our corporate office (at no charge to clients in a current support agreement). Our services team is happy to come to you. Personalized training onsite at your offices is offered for an additional fee. To further accommodate your training needs, we can schedule online classes focusing on specific features upon request. Email training@ogsys.com for the latest training schedule or to request online or onsite training.

10. What if new employees need OGsys training?

All of your OGsys users can attend as much training as needed if you are in a current support agreement. This training is free at our Fort Worth office.

11. Is English the only language you support?

OGsys application screens are only in English. However, custom reports can be made for reporting in other languages.

12. What SQL Database Engines do you support?

The OGSQL application supports Microsoft® SQL Server® versions 2005 or greater.

13. Are SQL Server® Express editions supported?

OGSQL supports Microsoft® SQL Server® 2005 (or greater) Express editions so long as your database requirements match the limitations of these versions. We recommend Microsoft® SQL Server® 2008 Standard Edition.

14. Is there a list of the the Pervasive Status Codes?

Yes there is. Please click here to download the Pervasive Status Codes.

Troubleshooting

1. Problem: "Login to server 'xxx' Failed" appears in the Export Log.

Cause: You may not have the correct SQL Server® name or Instance Name. You may have selected the incorrect authentication type for your environment when configuring the export. Contact your system administrator for the correct authentication type for your environment. You may not have sufficient rights to connect to the SQL Server®. Contact your system administrator.

Solution:  Make sure you can connect to the SQL Database with a Microsoft® utility such as Query Analyzer or OGsql. If a Microsoft® utility cannot connect, it is likely that OGsys is not the cause of the issue.

2. Problem: I have contacted Support and run the Final LIA and I still receive "Could Not
Insert Duplicate..." in the Export Log

Solution:: While rare, this error can occur with a clean LIA. Please arrange to send your OGsys database and the Export Log to Support for analysis.

3. Problem: "Could Not Insert Duplicate..." appears in the Export Log.

Solution: Run a Trial Logical Integrity Audit [LIA]. If the audit reveals any errors, please contact Support before running the Final LIA. The Final LIA will irrevocably alter your OGsys database and should only be performed after consulting Support. Always create a backup of your OGsys database before performing a Final LIA.

4. Problem: I receive errors relating to the Transaction Log

Cause: There is insufficient disk space availiable to the SQL Server®. Free some space and re-perform the export.

5. Problem: The Transaction Log is oversized and no export is currently active.

Solution: Perform the following steps to shrink the Transaction Log: Ensure there are no users in the SQL Database Open Query Analyzer and connect to the database in question. Issue the query "DBCC SHRINKFILE(MyDatabase_Log,1,TRUNCATEONLY) Check the size of the Transaction Log

6. Problem: I receive messages in the Export Log about insufficient rights to a particular
object or task.

Solution: These errors are almost always accurate. Please ensure that you have Administrator rights to the database when exporting. The export process Truncates, Drops, Creates and Alters various database objects, Inserts to and Updates tables, Executes Stored Procedures and Issues Database Console Commands (DBCC).

7. Problem: "Incorrect syntax near 'COLLATE'..." appears in the Export Log.

Cause: You are attempting to run the 1.8 version of the export to a version 7.0 SQL Server®.

Solution: Upgrade your SQL Server® to version 2000 or greater. Alternatively, you may use SQL Server® 2008. .

8. Problem: I cannot connect to SQL Server® Express Edition over a network.

Solution: The SQL Server® Browser Service is disabled on the server; enable and start it. No network protocol is enabled. Use SQL Server® Configuration Manager to enable TCP/IP

9. Problem: Running the General Ledger 230 report results in the following error
message, "Conversion from type 'DBNULL' to 'Integer' is not valid."

Cause: One or more total line types have no descriptions for what lines they are supposed to be totaling.

Solution: Look in Line Financial Format Maintenance for the line format code used in the report. You will find that there are one or more total line types (types T0, T1 or T2) that have no descriptions for what lines they are supposed to be totaling. If the line is supposed to be a descriptive line, delete the type T0, T1, or T2 line and insert a TI (title) type line. You must delete the T0, T1, and T2 lines that have no lines to total or enter the information as to what lines they should reference.

10. Problem: Errors in OGsql on Custom Excel Reports. When user tries to open any
of the custom Excel Reports an error is displayed (either below):

Exception: Exception has been thrown by the target of an invocation.

Exception: That assembly does not allow partially trusted callers.

Cause:

1. CASPOL (Code Access Security Policy) is part of the .NET Framework (technology on which the Excel reports rely). This policy dictates what permissions that executing .NET code has on a given workstation.

2. By default, CASPOL is configured to give applications installed on the local machine "FullTrust". Applications installed on the network (like OGsql) are only assigned partial trust. This means that policy must be changed in order for the Excel report to run.

3. There are two major components to determining effective policy for an application: What zone the application is detected as belonging to, and what policy is set for that zone. Examples of Zones are "Local Computer", "Local Intranet", "Internet" and so on.

4. We generally solve this problem by configuring workstations:

a. Such that the OGsql folder, and its children, are classified as part of the Local Intranet Zone
b. Such that the Local Intranet Zone is assigned FullTrust (i.e. you trust things on your own network).

Resolution: When a CASPOL issue occurs, it means that one of the following has likely happened:

A. The operating system is not detecting one or more OGsql files as belonging to the Local Intranet Zone. This can be determined by opening Windows® Explorer, browsing to the folder containing the Excel Modules (using the same UNC or Drive Letter path as used to execute OGsql), and examining the zone information in the status bar. If it doesn't say "Local Intranet", there is a problem.

B. Ensure that the Local Intranet Zone has been assigned FullTrust. This should have been done by the workstation installer for OGsql. It can also be performed by running the AdjNetSecurity.bat batch file. Run the batch file in a command prompt window so you can examine the output for errors. Users must exit OGsql and log back in after running the AdjNetSecurity.bat file successfully from the command prompt.

 

Click here for a full list of MicroKernel Database Engine Status Codes
http://www.ogsys.com/images/uploads/PervasiveStatusCodes.pdf