LINKS
General
Apex SQL Audit
Apex SQL Clean
Apex SQL Code
Apex SQL Diff
Apex SQL Data Diff
Apex SQL Doc
Apex SQL Edit
Apex SQL Enforce
Apex SQL Log
Apex SQL Recover
Apex SQL Report
Apex SQL Script
Troubleshooting Home
Apex SQL Audit
Apex SQL Clean
Apex SQL Code
Apex SQL Diff
Apex SQL Data Diff
Apex SQL Doc
Apex SQL Edit
Apex SQL Enforce
Apex SQL Log
Apex SQL Recover
Apex SQL Report
Apex SQL Script
Troubleshooting Home
MOST RECENT
What should I do when I encounter a problem in ApexSQL Log?
CreateService() failed: The specified service has been marked for deletion. (error code = 1072)
Got an error when trying to analyze database on x64 platform
Server Side components cannot be installed on a remote server
Access is denied message appears on ApexSqlServerHelper calling
Blank result is shown for transaction log
Very Large APEXSQL_LOG_LOGIN table.
Recovery Wizard reports that the server is still in trial mode even if the server was activated
Server-side components installation and privileges
I restored db backup and can't see anything after it was analyzed
SITE FEED
Support Forum
The fastest and most effective to get answers to your questions quickly. Click Here for more info.
FAQs 
Quick answers to common questions. Click Here for more info.
Troubleshooting
Known issues and basic troubleshooting techniques for problems or unexpected behaviors. Click Here for more info.
Knowledgebase
Technical tips, How-to articles, and other tutorials about ApexSQL Tools. Click Here for more info.
Online Documentation
All of our help files for download or convenient viewing online. Click Here for more info.
Videos
Watch product demos, training videos, or tutorials of our products' main features. We frequently upload new videos so check often for updates. Click Here for more info.
|
Troubleshooting Troubleshooting and Known issues with Apex SQL Tools What should I do when I encounter a problem in ApexSQL Log? Please send us application log files for analyze. 1) They are located here for ApexSQL Log 2005.10.0502 and older versions -WindowsXP: <ApexSQL Log installation folder>\Logs -Vista: C:\Users\<your login>\Local\VirtualStore\Program Files (x86)\ApexSQL\ApexSQLLog\Logs 2) For version 2005.11.0533 and up, C:\Documents and Settings\<your login>\Application Data\ApexSQL\ApexSQLLog\Logs. Please also send us server-side components logs. They are located in the LOG folder of SQL Server installation folder (e.g. C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG) and start with ApexSql*. LAST REVIEW 24 June 2008 Labels: ApexSQL Log ...'Cannot access .trn file' message appears on attempt to audit type of log other than the Online Transaction Log This error message states that your .trn files are most probably locked either by SQL Server or some application. To get rid of this error message you should ensure that no applications lock these files. But if you would like to know what processes block your file you can use the Handle application described here. After the program installation you can view all locking processes list by typing in the following: handle "BFW_backup_200805281902.trn" Where the argument represents the .trn file name. LAST REVIEW 24 June 2008 Labels: ApexSQL Log ...CreateService() failed: The specified service has been marked for deletion. (error code = 1072) This error message indicates that ApexSQL Log server-side components were removed, when they were in use. Please restart SQL Server to solve the problem. LAST REVIEW 24 June 2008 Labels: ApexSQL Log ...Copy file for ApexSqlServerXprocs.dll failed: The system cannot find the path specified. (error code = 3) Please try the following approach: 1. Login to server 2. Run ApexSQL Log installation directly on it 3. Select 'Server-Side Components' installation only 4. Finish install process LAST REVIEW 24 June 2008 Labels: ApexSQL Log ...Got an error when trying to analyze database on x64 platform Got the following error when trying to analyze database on x64 platform: Server-Side components are not correctly installed: %1 is not a valid Win32 application The problem you experienced with occurs when 32-bit server-side components were installed on 64-bit platform. Please check the size of ‘ApexSqlConnectionMonitor.exe’ and ‘ApexSqlServerHelper.exe’ files in the BINN folder of the SQL Server installation with ‘ApexSqlConnectionMonitorx64.exe’ and ‘ApexSqlServerHelperx64.exe’ located in the ApexSQL Log installation folder. If they are different please re-install server-side components by running installation directly on server and selecting server-side components installation only, otherwise please send us the server-side components log files to log_team@apexsql.com They are located in the LOG folder of the SQL Server installation one (e.g. C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG). LAST REVIEW 24 June 2008 Labels: ApexSQL Log ...I am trying to recover data of a drop table and it always says to me that it does not find any and it does not recover either the schema of the table You need to try the following approach: 1.Do an immediate full db backup (The log file is automatically truncated by SQL Server if you are in SIMPLE recovery mode *or* if you are in FULL recovery mode but haven’t yet done full db backup), the more post-incident db activity mean less chances of recovery. 2.Run Recovery Wizard with appropriate options selected. 3.Send us the application log files to log_team@apexsql.com They are located in the Logs folder of ApexSQL Log installation one. LAST REVIEW 24 June 2008 Labels: ApexSQL Log ...When I audit transaction log from another server, ApexSQL Log shows invalid data for NT user name, application name and client host Why is that? What can I do to fix it? NT user name, application name and client host data is not found in transaction log. Instead, ApexSQL Log captures that data through its Connection Monitor and then later during auditing process this is matched with transaction log data. When database is moved from one server to another then ApexSQL Log cannot find the correct captured login data and invalid data (or none at all) is shown. One way to handle this without any change in the software would be following this procedure: 1. Copy the set of your transaction log backups that you will be auditing to the auditing server. 2. BCP data from msdb.dbo.APEXSQL_LOG_LOGIN table on the production server and copy the resulting file to the auditing server. Make sure that you use format which doesn't take out SERVER_NAME column values: bcp "SELECT SPID, LOGIN_TIME, LOGIN_NAME, CLIENT_HOST, APPLICATION_NAME FROM msdb.dbo.APEXSQL_LOG_LOGIN" queryout ProductionServerLogins.Bulk -T 3. Truncate msdb.dbo.APEXSQL_LOG_LOGIN table on the auditing server and then use BCP to upload login data from production server. bcp msdb.dbo.APEXSQL_LOG_LOGIN in ProductionServerLogins.Bulk -T 4. Run ApexSQL Log auditing process on the auditing server with the set of the transaction log backups you copied in step 1. Since msdb.dbo.APEXSQL_LOG_LOGIN now contains login data from the production server, you should see correct login data shown in the application. LAST REVIEW 24 June 2008 Labels: ApexSQL Log ...Server Side components cannot be installed on a remote server SYMPTOMS Server-Side components cannot be installed on a remote server. SOLUTION You need to download and install the Visual C++ 2005 SP1 runtime components directly on the server and then install the server-side components after. Server side components installation requires Visual C++ 2005 SP1 runtime components, which cannot be installed remotely. These runtime components are available here. If you are running an x64 or IA64 server, you would still need to install the x86 version of the Visual C++ components. LAST REVIEW 24 June 2008 Labels: ApexSQL Log ...Access is denied message appears on ApexSqlServerHelper calling Got the "Call to xproc xp_ApexSQLLog(1) Failed..." error message before audit of the transaction log is started  CAUSE It’s caused by lack of permissions on the part of the account that is running SQL Server process/service. RESOLUTION To fix the problem, please do the following:
LAST REVIEW 20 August 2007 Labels: ApexSQL Log ...Blank result is shown for transaction log I am opening a log using AlexSQL Log application and it is not showing anything as if Tran. log backup file is empty. SYMPTOMS The following error symptoms are indicates that result will be empty:
RESOLUTION Here it is the steps to solve the problem with 'Access is denied' message:
LAST REVIEW 10 August 2007 Labels: ApexSQL Log ...Very Large APEXSQL_LOG_LOGIN table. I discovered that our sql server 2005 msdb sytem database has grown to 15gigs. Almost the entire size of the database is the APEXSQL_LOG_LOGIN table at about 12gigs. Any idea as to why this has grown so large or how I can purge the information in it without breaking Apex SQL Log? CAUSE The heart of the issue is that ApexSQL Log Connection Monitor inserts one new row into msdb.dbo.APEXSQL_LOG_LOGIN database for each new login. So this table grows directly in proportion to the number of logins made to the server. We don't clean up this login information automatically as it belongs to users. RESOLUTION The easiest way to fix this would be to stop Connection Monitor, truncate the table and then start again Connection Monitor. The consequences of this are that ApexSQL won't show application name and client host name for all transactions prior to restart of Connection Monitor (as this is the information that we read from the said table.) NT user name information should still be shown correctly since SQL Server 2005 allows us (in general case) to output that information without Connection Monitor data. To achieve the above you would need to run the following script: EXEC MASTER.DBO.xp_ApexSqlConnectionMonitor_Stop USE MSDB TRUNCATE TABLE APEXSQL_LOG_LOGIN EXEC MASTER.DBO.xp_ApexSqlConnectionMonitor_Stop Another solution would be to just delete rows from the table before a certain date (e.g. DELETE FROM msdb.dbo.APEXSQL_LOG_LOGIN WHERE LOGIN_TIME < 'date') However, considering just how large is the table, will make msdb transaction log grow. Instead you could delete rows piecemeal - day by day until you reach the cut-off date you selected. LAST REVIEW 17 January 2008 Labels: ApexSQL Log ...Recovery Wizard reports that the server is still in trial mode even if the server was activated ApexSQL Log was activated on the server and the activate server dialog shows it as activated. However, Recovery Wizard reports that the server is still in trial mode and won't recover more than every 10th row. How can Ii be fixed? CAUSE This is a rare problem that happens only on a small percentage of servers RESOLUTION In order to fix the problem all you need to do is restart SQL Server service. LAST REVIEW 08 August 2007 Labels: ApexSQL Log ...Is it possible to read the Text for this transaction from the log? Seems that Text fields are represented by a fixed length. Seems that any Text fields are represented by a fixed length hexadecimal string. Is it possible to read the Text for this transaction from the log? CAUSE The hexadecimal string shown is the pointer to actual text. This is what SQL Server writes to log when it logs the INSERT/UPDATE/DELETE operation. There are other operations that might log changes to text fields depending on the configuration of SQL Server. RESOLUTION Unfortunately, the current version of ApexSQL Log cannot analyze these other operations although we plan on adding it in the future. LAST REVIEW 08 August 2007 Labels: ApexSQL Log ...Driver entry point not found. Inhf.sys device driver could not locate the entry point error appears under NT server with SQL2k "Driver entry point not found. Inhf.sys device driver could not locate the entry point" error message appears under NT server with SQL 2000 CAUSE The problem is that Live Log works only on Win2000/XP/2003 RESOLUTION You can still use ApexSQL Log with an NT server, however, by using transaction log backups or detached log files instead of online log files. LAST REVIEW 08 August 2007 Labels: ApexSQL Log ...Server-side components installation and privileges 'Access is denied' message appears during Server-side components installation. CAUSE User, under which server-side components are installed haven't sysadmin privileges on the server and haven't write permission to Binn folder of the SQL Server RESOLUTION Here it is the ways to install server-side components and privileges and permission that are required to complete installation:
MORE INFORMATION Here it is the list of Server-Side components:
LAST REVIEW 26 July 2007 Labels: ApexSQL Log ...I restored db backup and can't see anything after it was analyzed I restored db backup and can't see anything after it was analyzed SUMMARY Backup file of a database whose transaction log will be analyzed is selected. The database is in full recovery mode and was created from a backup of a sql 2005 express edition. The log wizard sees the database and default filters are selected. SYMPTOMS The Project Wizard processing and runs quickly for selected backup but when it stops there are no rows to view CAUSE The problem is that full database backup doesn't include the entire transaction log. Instead SQL Server only includes the transactions that were uncommitted at the start of the backup plus all the transactions that ran during the backup. During backup restoration process SQL Server then inflates the transaction log file to its original size and copies into it the part of the transaction log that it did backup - the rest of the file is just zeroed. RESOLUTION You need to create transaction log backup on the original server and then analyze it with ApexSQL Log pointing to the restored database. LAST REVIEW 25 July 2007 Labels: ApexSQL Log ...Messages on server activating Once one has tried to activate a server, it appears the next message “Server The problem is that the About box displays: This product is licensed to: USER: Not connected to a server Activation Key: Not connected to a server Actually this may not be a problem at all as the fields in About box are populated only when you are connected to a server (that’s why it says “Not connected to a server”). Just connect to the server you activated and then open again About box – you should see license information. This happens because ApexSQL Log is licensed per server so the client (which can be distributed freely) can show the license information only when it’s connected to a server. Finally, to be sure you can look at your activation key using Windows RegEdit utility (note that server activation is under the account running SQL Server service). Look for the entry in HKEY_USERS and then Software\ApexSQL\ApexSQL Log. You should then see the server name and the instance name and then finally the entries for the activation. Labels: ApexSQL Log ...Welcome to the ApexSQL Troubleshooting and Known Issues Welcome to the ApexSQL Troubleshooting and Known Issues. This is an online resource to help you find solutions to known issues with Apex SQL tools. Labels: ApexSQL Audit, ApexSQL Clean, ApexSQL Code, ApexSQL Diff, ApexSQL Diff (Data), ApexSQL Doc, ApexSQL Edit, ApexSQL Enforce, ApexSQL Law, ApexSQL Log, ApexSQL Script, General ... |
© 2008 Apex SQL Tools All Rights Reserved | 1.919.968.8444 | Contact Us | Terms of Use | Privacy Policy