Oil & Gas Information Systems :: The Petroleum Industry's Most Advanced Accounting Software for Windows
All that sets you apart from your competition is the information to which you have access.

SQL Report Library

Frequently Asked Questions

What SQL Engines do you support?
The OGWin SQL Export supports Microsoft SQL Server versions 2000 and greater.
Wasn't Microsoft SQL Server 7.0 supported in the past?
The 1.7 version of the SQL Export is still compatible with SQL Server 7.0. The 1.8 version of the export and the upcoming SQL Native product utilize features present in versions 2000 and above.
What about the MSDE or SQL Server Express?
OGWin supports MSDE 2000 and SQL Server Express editions of Microsoft SQL Server so long as your database requirements match the limitations of these versions. We reccomend SQL Server 2005 Express Edition.
SQL Server Express Edition?
SQL Server Express Edition is a free edition of SQL Server. SSEE has some limitations, but meets the needs of many OGWin clients. In addition to the features of the old MSDE, graphical query tools are available. More information can be found at: http://www.microsoft.com/sql/editions/express/default.mspx
MSDE, What's That?
The MSDE has been replaced by SQL Server 2005 Express Edition. MSDE 2000 is no longer available for download, but it still supported by OGWin.
« Back to SQL Report Library

Troubleshooting

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 OSQL. If a Microsoft utility cannot connect, it is likely that OGWin is not the cause of the issue.
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 OGWin database and the Export Log to Support for analysis.
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 OGWin database and should only be performed after consulting Support. Always create a backup of your OGWin database before performing a Final LIA.
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.
Problem: The Transaction Log is oversized and no export is currently active.
Solution:

Perform the following steps to shrink the Transaction Log:

  1. Ensure there are no users in the SQL Database
  2. Open Query Analyzer and connect to the database in question.
  3. Issue the query “DBCC SHRINKFILE(MyDatabase_Log,1,TRUNCATEONLY)
  4. Check the size of the Transaction Log
Problem: I receive messages in the Export Log about insufficient rights to a particular object or task.
Cause: 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).
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 2005 Express Edition.
Problem: I cannot connect to SQL Server Express Edition over a network.
Cause:

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.

« Back to SQL Report Library
site design by DwarfMondo