| By product |
| Other |
|
Troubleshooting Troubleshooting and known issues with ApexSQL Tools "Invalid Activation Code" message appears during Automatic and Manual activation APPLIES TO All ApexSQL Products SUMMARY This article explains what to do when "Invalid Activation Code" message appears during both Automatic and Manual activation RESOLUTION 1) Go to Manual activation (Website login is required) 2) Select ApexSQL product in the Product list 3) Enter the Activation Key and Hardware ID an click Submit 4) The Activation code will be displayed. Click Get Reg key file 5) Save the file on the machine where ApexSQL product that should be activated is installed 6) Double click the saved reg file and, when prompted, allow the file to be added to the registry 7) A message notifying you about successful key adding to the registry will be displayed LAST UPDATED December 02, 2011 Labels: Activation ..."Activation Key invalid for this Product" message occurs APPLIES TO All ApexSQL Products SUMMARY This article explains what to do when "Activation Key invalid for this Product" message occurs. CAUSE The Activation key is valid but it is being used to activate the wrong product. RESOLUTION Make sure you are using the correct key for the specific product you are trying to activate. If the product is correct, contact support@apexsql.com and explain the problem LAST UPDATED December 02, 2011 Labels: Activation ..."Activation Limit Exceeded" message occurs APPLIES TO All ApexSQL Products SUMMARY This article explains what to do when "Activation Limit Exceeded" message occurs. CAUSE The number of successful activations has exceeded the limit allowed for this activation key. RESOLUTION Contact sales@apexsql.com, provide your full name, email, HardwareID and Activation Key in question. If possible, provide the number of activations with this Activation Key and the reasons behind each of them (installing on the test machine, machine replacement, etc.) LAST UPDATED December 02, 2011 Labels: Activation ..."Activation Key doesn't exist" message occurs APPLIES TO All ApexSQL products SUMMARY This article explains what to do when "Activation Key doesn't exist" message occurs. CAUSE This occurs when the activation key isn’t valid or may be missing from our server. RESOLUTION Contact sales@apexsql.com, provide your full name, email, HardwareID and any other order-related information and explain the situation LAST UPDATED December 02, 2011 Labels: Activation ...Despite successfull activation, activation form keeps showing up like the product is not activated APPLIES TO All ApexSQL Products SUMMARY This article explains what to do when the product is successfully activated but the application activation form keeps showing up indicating the product is not activated. RESOLUTION 1) Go to Manual activation (Website login is required) 2) Select ApexSQL product in the Product list 3) Enter the Activation Key and Hardware ID an click Submit 4) The Activation code will be displayed. Click Get Reg key file 5) Save the file on the machine where ApexSQL product that should be activated is installed 6) Double click the saved reg file and, when prompted, allow the file to be added to the registry 7) A message notifying you about successful key adding to the registry will be displayed LAST UPDATED December 02, 2011 Labels: Activation ..."Invalid Regkey" message appears when trying to activate APPLIES TO All ApexSQL Products SUMMARY This article explains what to do when "Invalid Regkey" message occurs. CAUSE This occurs with the older versions of the products that do not point to the new activation server where the Activation Key is stored. RESOLUTION Download a new version of the software or use Manual activation LAST UPDATED December 02, 2011 Labels: Activation ...What to do when ApexSQL product fails on startup silently Summary This article describes what to do when ApexSQL product fails at startup silently Symptoms When attempting to start ApexSQL product it fails silently Resolution 1. If your application was activated previously please perform the following steps: a. Start the Windows Registry editor: Start | Run | regedit b. Locate a key that corresponds to your application under HKEY_CURRENT_USER | Software| ApexSQL c. Delete the entire key d. Start the application and reactivate it 2. If you installed your program over an older version, at start up new version tries to load the old profiles and, depending on the product and version, it may cause this type of behavior. To work around this problem, please uninstall the application. Delete the installation folder to clean out of all profiles and xml files then re-install. Last updated December 26, 2011 Labels: General ...What to do when ApexSQL installer fails at start up with message "The setup file is corrupted" or "The setup files are corrupted" Summary This article describes what to do when ApexSQL installer fails at start up with message "The setup file is corrupted" or "The setup files are corrupted" and .Net is installed Symptoms While attempting to open ApexSQL installer the next message appears:  Cause The most common reason for this is that the downloadable installation file wasn't completely downloaded Resolution To solve this issue please try re-downloading the installer. If problem persist please contact support@apexsql.com for a workaround Last updated December 26, 2011 Labels: General ...What to do when ApexSQL product starts with .Net exception and .Net is installed Summary This article describes what to do when encountering .Net exception on product startup and .Net is installed Symptoms Product starts with .Net exception:  Cause This message appears when .Net framework 1.1 is installed, but a newer version is required to run the product Resolution To solve this issue please check system requirements for your product and install a newer version of .Net framework (do not uninstall .Net framework 1.1) Last update December 26, 2011 Labels: General ...What to do when ApexSQL product starts with general Windows GPF exception Summary This article describes what to do when encountering general Windows GPF exception on product startup Symptoms Product starts with Windows GPF exception:  Cause The message shows up when there is no .Net run-time library installed Last update December 26, 2011 Labels: General ...What to do when ApexSQL product starts with Visual Studio JIT debugger exception Summary This article describes what to do when encountering Visual Studio JIT debugger exception on product startup Symptoms Product starts with Visual Studio JIT debugger exception:  Cause This exception occurs when product application files are damaged or the installation process failed Resolution Uninstall the product, delete the installation folder and its contents, then re-install the product Last update December 26, 2011 Labels: General ...Connection to SQL server failed
APPLIES TO All ApexSQL products SUMMARY This article explains what should be done when application fails to log in showing the "SQL Server does not exists" message RESOLUTION The possible workarounds for this case are as follows: 1) For SQL Developer and SQL Enteprise servers named as MACHINE_NAME\MSSQLSERVER
2) For SQL Express servers please put "\SQLEXPRESS" at the end of server name LAST REVIEW 05 December, 2011 Labels: General ...What happens if the account used to start or install a product doesn't have enough privileges? APPLIES TO All ApexSQL products; Windows 7 x32/x64 and below; Windows Server 2008 R2 x32/x64 and below SUMMARY This article shows what happens if the account used to start ApexSQL product installation doesn't have the minimum permissions required to successfully install and use ApexSQL products DESCRIPTION - INSTALLING In order to install ApexSQL products, the account used to start the installation has to have administrative privileges If User Account Control (UAC) doesn’t exist or is disabled, and the installation is started from a non-administrative account the following error is shown:  On the other hand, if UAC is enabled and the installation is started from a non-administrative account you are prompted to enter credentials for an administrative account, as shown:  NOTE: You have to start the installation from an administrative account/supply administrative credentials. The installation will fail, even if started from a power user account/power user credentials are supplied. There is an exception to this behavior, when Group Policy is used to deploy the application to target computers in an Active Directory domain; however that scenario is beyond the scope of this article - USAGE Most of the ApexSQL installation files are copied to the location specified during the installation process. By default, that location is %ProgramFiles%\ApexSQL\ on 32 bit, or %ProgramFiles(x86)%\ApexSQL\ on 64 bit systems. In the remainder of the text we will use ApexSQL Edit as a sample product; however the text applies to all ApexSQL products ApexSQL products store application specific settings in the installation folder. Let us consider the following scenarios: • ApexSQL Edit is installed in %ProgramFiles%\ApexSQL\ or %ProgramFiles(x86)%\ApexSQL\ and UAC is nonexistent or disabled. The minimum required permissions are:  • ApexSQL Edit is installed in %ProgramFiles%\ApexSQL\ApexSQL2008 or %ProgramFiles(x86)%\ApexSQL\ApexSQLEdit2008 and UAC is enabled In this case the output is automatically redirected to the VirtualStore\Program Files\ApexSQL folder, located in %AppDataLocal%. The minimum required permissions are:  • ApexSQL Edit is installed in a custom location. The minimum required permissions are:  If the user account doesn’t have the Write permission on that folder, the following error is displayed  and the application will fail to start Besides the folder the ApexSQL product is installed to, additional files and folders are necessary for the product to run properly. %AppDataLocal%\ApexSQL\Common stores information on the used SQL servers (DisplayedServers.xml and LocatedServers.xml) and information relevant to the updating process. Product specific settings are stored in the %AppDataLocal%\ApexSQL\%ProductName% folders. ApexSQL Log and ApexSQL Recover store their logs in %AppDataLocal%\ApexSQL\%ProductName%\Logs. Therefore, the minimum permissions required over the %AppDataLocal%\ApexSQL folder are:  In case the user account has less permissions than shown, or can’t access the files in %AppDataLocal%\ApexSQL for any other reason, some of the ApexSQL products won’t work under that account and will throw the appropriate exception. Normally, the user has Full Control on his %AppData% folder, however, in scenarios when the company policy is to redirect the %AppData% folder to a server, instead of keeping it on the local machine, and when the network server or the domain controller is unavailable or when certain restrictive Group or Security Policies are applied, knowing the permissions sets listed above can be beneficial LAST UPDATED November 24, 2011 Labels: General ...Insufficient execute permissions dialog shown when working with the Connection monitor
APPLIES TO
ApexSQL Log SUMMARY This article explains what to do when the following message appears "Insufficient permissions to execute server-side components. Please make sure SQL login used has EXECUTE permission on ApexSQL Log extended procedures (xp_ApexSQLLog)" SYMPTOMS Insufficient permissions to execute server-side components message shows up when user is connecting to the Connection monitor manager 
CAUSE Besides the client application, ApexSQL Log installs several extended stored procedures to SQL Server master database. Only a user with enough privileges granted on the master database and these procedures can access Connection monitor manager and view and change its settings RESOLUTION SQL login used to access the Connection monitor manager must have at least db_datareader and db_securityadmin database roles and be granted EXECUTE permission on both xp_ApexSqlLogConnectionMonitor_State and xp_ApexSQLLog extended stored procedures. It also needs to have VIEW ANY DEFINITION set upon the master database LAST UPDATED November 28, 2011 Labels: ApexSQL Log ...How to solve missing schema issue in scripts for databases with SQL Server 2000 compatibility APPLIES TO ApexSQL Script SUMMARY This article describes how to create correct scripts with ApexSQL Script for objects that contain schemas other than dbo SYMPTOMS As schemas are first introduced in SQL Server 2005, they are not scripted nor shown in Object Filter for databases with SQL Server 2000compatibility  Schemas also don’t show up as dependent objects in the Script Wizard  RESOLUTION To fix this problem, change the database compatibility level from SQL Server 2000 to SQL Server 2005 and up SEE ALSO ALTER DATABASE Compatibility Level (Transact-SQL) LAST REVIEW November 30, 2011 Labels: ApexSQL Script ...System.TypeInitialization Exception thrown when starting application Applies to ApexSQL Refactor Summary This article explains what to do when the application crashes at start with the following message "System.TypeInitializationException" Symptoms When starting the application, the following exception is thrown Type: System.TypeInitializationException Message: The type initializer for 'ApexSql.Common.Activation.DllActivationManager`1' threw an exception Source: ApexSql.Common.Activation Cause Execution of ApexSql.Common.ActivationBroker.exe is blocked by an antivirus program. The reason is that multiple dots in the file name are identified as suspicious and potentially dangerous Resolution Reinstall the application following these steps 1. Uninstall the product 2. Download ApexSQL Refactor installation 3. Disable the antivirus software 4. Start the installer as administrator 5. Install the product into the folder which is located outside Program Files 6. Enable the antivirus software after installation Last updated December 21, 2011 Labels: ApexSQL Refactor ...System.OutOfMemory exception is thrown
APPLIES TO ApexSQL Diff, ApexSQL Log, ApexSQL Doc SUMMARY This article explains what to do when the System.OutOfMemory exception is thrown SYMPTOMS System.OutOfMemory exception is thrown. It usually happens when working with large databases, backups or script folders containing large number of objects, generating huge scripts or putting application under strain in general. CAUSE The exception is caused by the .NET framework architecture and the way it allocates memory. Due to the nature of the .NET framework, this cannot be completely removed, however it can be worked around. RESOLUTION Use Command Line Interface that these ApexSQL products contain. Using CLI puts less strain on the machine resources. You can either save your project using GUI and then execute it via CLI, or you can specify all the parameters using CLI entirely. To make your project using GUI and execute it via CLI: 1) Make your project using GUI and save it 2) Open Command Prompt 3) Navigate to the ApexSQL product installation path (e.g. cd C:\Program Files\ApexSQL\ApexSQLDiff\ or cd C:\Program Files\ApexSQL\ApexSQLLog\) 4) Type: a) for ApexSQL Diff ApexSQLDiff.com /project:<project path>\<project name> (e.g. ApexSQLDiff.com /project:C:\Users\ApexUser\Documents\ApexSQL\ApexSQLDiff \project.axds) The script file named “sync.sql” will be created in the ApexSQL Diff installation folder. b) for ApexSQL Log ApexSQLLog.com /project:<project path>\<project name> /undo:<filename> (e.g. ApexSQLLog.com /project:C:\Users\ApexUser\Documents\ApexSQL\ApexSQLDiff \project.axlp /undo:undoscript.sql) The script file named “undoscript.sql” will be created in the ApexSQL Log installation folder. Instead of using CLI in ApexSQL Log, you can output the results into a file and thus avoid showing them in the Main grid. LAST REVIEW December 01, 2011 Labels: ApexSQL Diff, ApexSQL Doc, ApexSQL Log ...How to determine if ApexSQL Log CLI has stopped working APPLIES TO ApexSQL Log SUMMARY This article explains how to determine if ApexSQL Log CLI has stopped working SYMPTOMS The application running is undetermined. There are no new output lines in the console CAUSE Analyzing huge transaction logs can cause ApexSQL Log to become non-responsive RESOLUTION To check if the ApexSQL Log is still running, do the following: 1. Open Windows Task Manager 2. Select Processes tab and open Select Columns dialog 3. Select I/O Read Bytes 4. Click OK and check this value for ApexSQLLog.exe value  If the value of I/O Read Bytes keeps changing - ApexSQL Log is still analyzing transaction log sources Also check the size of the output file created by ApexSQL Log. If its size is increasing - ApexSQL Log is still running POSTED BY ApexSQL Team LAST UPDATED November 25, 2011 Labels: ApexSQL Log ...Insufficient credentials exception is thrown when attempting to install the server-side components APPLIES TO ApexSQL Log SUMMARY This article explains what to do when the "Insufficient credentials" exception is thrown SYMPTOMS Exception is thrown during the installation of the server-side components CAUSE Insufficient user permissions to install the server-side components RESOLUTION Make sure that the computer user account used to run the installation • Is a member of the Windows administrators group on the machine the installation has been started on • Has Windows administrative privileges on the machine on which the SQL Server is installed • Is a member of the fixed sysadmin SQL Server role Try to install the server-side components again SEE ALSO ApexSQL Log installation manual LAST REVIEW November 25, 2011 Labels: ApexSQL Log ...The specified path is too long error Applies to All ApexSQL products Summary This article shows how to solve the issue when "The specified path is too long" error is encountered during product update Description In case when the ApexSQL product used is not in the current version, Automatically check for updates on Application Start-up option is checked, all the files necessary for upgrade are downloaded, upon starting product update the following error message will occur: The fully qualified file name must be shorter than 260 characters and the path name shorter than 248 characters. Cause This is a known Windows limitation. The installation folder path length and the length of the file name should not exceed the given number of characters. Resolution During the product installation, the installation folder must be chosen. If a folder with a short path is chosen, this error won't appear. It is not possible to change the installation folder during the automatic update. To work around this problem, please download ApexSQL Installer Just install the ApexSQL product into a new folder. In Vista and Windows 7, this can be worked around by using mklink.exe for directory junctions and symbolic links. Last updated December 26, 2011 Labels: General ... |
