1. Does IssueView run on Vista?
   
   
2. Will I lose my configuration or data if I go from a Trial License
   or the Personal Edition to a multi-user license?
   
   
3. Can IssueView be used over the Internet?
   
   
4. What new Features have been added to IssueView?
   
   
5. What are the System Requirements for IssueView?
   
   
6. How do I use my Company's logo in Reports?
   
   
7. What databases does IssueView Support?
   
   
8. Which database should I use?
   
   
9. Why do I just get a blue box on the Login.aspx page?
   
   
10. Where can I get the latest Microsoft Access Drivers?
    
    
11. Does each user have to download IssueView?
    
    
12. How can I create an installation CD?
    
    
13. How do I configure IssueView for multiple users with Access?
    
    
14. How do I move IssueView from one SQL Server to another?
    
    
15. Why can't IssueView connect to my SQL Server?
    
    
16. Can I install IssueView on a Named Instance of SQL Server?
    
    
17. How do I upgrade to the latest version?
    
    
18. Can I test an upgrade without affecting my production database?
    
    
19. Why don't I see the new features after a version upgrade?
    
    
20. Why do I have multiple issues with the same ID?
    
    
21. Can I generate Choice List values with a SQL Query?
    
    
22. How can I make the IIS Timeout longer for the Web interface?
    
    
23. How do I configure IIS on Windows 2003 to support IssueView-Web?
    
    
24. Will IssueView work on an IIS Server with Windows SharePoint Services Installed?
    
    
25. How do I upgrade my MSDE 2000 to SQL Server 2005 Express Edition?
    
    
26. How do I load xsl Stylesheets for printing into my database?
    

1. If you launch IssueView and get an error saying "An exception of type 'java/lang/UnsatisfiedLinkError' was not handled.", you'll need to update the Microsoft Java Virtual Machine. You can download the installer from here. Run msjavx86.exe on your machine and it will solve the UnsatisfiedLinkError.   
   
   
2. You may also need to manually register msado15.dll by running RegSvr32 from an elevated command prompt:
   
   
   1. Click the 'Start' button, click 'All Programs', click 'Accessories', right-click 'Command Prompt', and then click 'Run as Administrator'.
      
      If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
      
      
   2. In the Run dialog type the following command:
      
      

      regsvr32 "C:\Program Files\Common Files\System\ado\msado15.dll"
      
      

   3. Press Enter.  You should get a confirmation that DllRegisterServer succeeded.

Q. Will I lose my configuration or data if I go from the Personal Edition to a multi-user license?
A. Absolutely not!  You can upgrade from a Personal Edition License, or Trial License, to a multi-user license without losing a thing.  Just purchase a License code and enter your new license.  None of your settings will be affected.

It's also easy to move your database from a Test, Evaluation, or Development environment into production.  If you are using SQL Server, you simply log in as 'admin', backup the database, and copy the backup file to the new SQL Server.  On the new SQL Server, download RestoreBackup.exe and run it to restore the backup file to the new server.  RestoreBackup is required as it gets the SQL Login IDs mapped correctly.  If you get a 'class not found' error when running RestoreBackup, you'll need to install the latest Microsoft JVM on the new SQL Server.

If you started working with an Access database and want to move to SQL Server we can help.  You'll need to send us your Access database, and we'll convert it to a SQL Server backup file which you can 'restore' to your SQL Server (or MSDE).  The process takes us about an hour, and is free (isn't that nice?).
Top

Q. Can IssueView be used over the Internet?
A. IssueView supports 3 forms of Internet Access. First, there is a browser based interface written in C# for the .NET platform. Second, if you install IssueView with a SQL Server database, users anywhere in the world can launch the IssueView Win32 client and have full access to your database.  Performance is fine, but obviously not as good as you will get accessing it locally on a high speed LAN.

Finally, IssueView also has a WebSupport Customer Support portal which you can implement to provide issue submission and tracking for your customers.  It supports self-registration, e-mail notification, and file attachments.  Customers are given access to a limited subset of the fields and actions in an IssueView Project (normally the default one named 'WebSupport').  Your support personnel can interact with your customers, and Issues submitted via WebSupport can be copied to other projects within your IssueView database.
Top

Q. How do I use my Company's logo in Reports?
A. Our default Report Stylesheets use a file named Logo.gif, which contains our logo. You can replace it with your own logo by updating the file. The file needs to be updated in the database, so all of your users will have access to your logo:

1. Create a .gif file with your logo.  Our logo is 80 pixels wide by 40 pixels high.  You can use a different size, but small works best.  It should be a .gif image, in a file named Logo.gif.  If you wish to use another file type or name, you'll need to edit the xsl stylesheets to reflect your new file's name.
2. Select 'Manage Reports' from the Reports menu.
3. In the Reports dialog, click the Resources button
4. In the Resources dialog, select 'Logo.gif' and click the Modifiy button
5. In the Resource Properties dialog, click the '...' button to select your logo image file from step 1.  
6. Save your changes

Q. What databases does IssueView Support?
A. Microsoft Access 2000, and Microsoft SQL Server 7.0 and above.   The 'Full' installation package (IV40MSDE.exe) includes MSDE, a runtime version of Microsoft's SQL Server, which supports up to 8 concurrent transactions. But given the low-overhead of bug tracking, it can support dozens of users.
Top

Q. Which database should I use?
A. It depends on the load.  If you are the only person accessing the database, then Access is best.  If you have multiple users, SQL Server will perform much better.
Top

Q. Why do I just get a blue box on the Login.aspx page?
A. There are a couple of common reasons for this problem.  First, the IIS Server may not have the .NET framework installed.  You can download the installer, dotnetfx.exe, from our web site.  Run dotnetfx.exe on your IIS Server, and it will install the .NET Framework.  Try loading IssueView and see if it gives you a normal logon page.

The second possibility is that the .NET Frame work isn't properly registered on the IIS Server.  This is a Microsoft problem, and we see it with some frequency.  If the logon controls don't show up once the Framework is installed, you'll need to re-register it:

1. Open a DOS command shell
2. Navigate to C:\Windows\Microsoft.NET\Framework\v1.1.4322
3. Enter the following command: aspnet_regiis.exe -i

If you browse to IssueView after this and don't get a logon page, try Uninstalling "IssueView - Web" from the control panel, then re-installing it.  Sometimes ASP.NET applications don't get properly installed if the Framework isn't installed first.

If none of that works, one last thing to check is the NTFS permissions on the folder.  The ASPNET account needs to have Read and Execute permissions over the folder C:\inetpub\wwwroot\IssueView, and over the file C:\Windows\IMUtil.dll
Top

Q. Where can I get the lastest Microsoft Access Drivers?
A. The best place is Microsoft's Data Access Site.  For your convenience, we've included the latest versions here.  Note that you only need one of these updates if you're using a Microsoft Access database, and you're experiencing problems.  Click on the link for YOUR operating system:

Windows Server 2003

Windows XP

Windows 2000

Windows ME

Windows 9x or NT 4.0 

 Top

Q. Does each user have to download IssueView?
A. No, additional users should NOT download the Setup.   When you perform a Full install, a client setup (NetSetup) is copied to the server, and will automatically configure additional users to connect to your database.   The NetSetup is usually located in \Program Files\IssueView\NetSetup. The folder is usually shared as 'IVSetup'.  Additional users can map a drive to the server, and run the setup.  If you prefer, you can send them a UNC link.   Assuming you installed IssueView on a machine named IVServer, the link would be \\IVServer\IVSetup\Setup.exe

If you've installed the Access version, you'll need to make some additional configuration modifications so user will be able to connect to the database remotely.
Top

Q. How can I create an installation CD?
A. In order to avoid charging you a sales tax, IssueView does NOT ship a CD.  The entire program is available from our download page.  You can create a CD by executing the downloaded Installation package.  The first time it prompts you for an 'Installation Folder', enter a new folder.  When the installation begins, press cancel.  The files in your 'Installation Folder' can then be copied to a CD to create an Installation CD. 
Top

1) Install IssueView on the File Server with an Access Database, and a NetSetup;

2) In File Manager, Share the installation folder which contains im.mdb with the share name 'IssueView'.  This share name will be added to a setup configuration file in the next step.

3) To configure the NetSetup, you'll need to edit Setup.ini in the NetSetup directory.  It will contain a local path, which you'll need to change to a UNC path.  For example, we installed IssueView on our test server, IVTEST02, in C:\Program Files\IssueView.  Then we edited the connection string to support remote connections:

[Connection]
Name=IVTEST02
Type=1
;Database=C:\Program Files\IssueView\im.mdb
Database=\\IVTEST02\IssueView\im.mdb

(The original Database entry is shown here, commented out by placing a semi-colon at the beginning of the line.  You can just delete it from your copy of setup.ini)

Now when additional users install IssueView from the NetSetup on IVTEST02, they will be automatically configured to connect to the Access database via the UNC path to the database.

If you've already installed IssueView on your own machine, just follow the above steps. After the installation is complete, copy your existing database (im.mdb, usually in \Program Files\IssueView) onto the file server, replacing the copy that got installed.  All of your data will be preserved.
Top

Q. Why can't IssueView connect to my SQL Server?
A. There are several reasons why IssueView will have trouble connecting to your SQL Server or MSDE database. Bear in mind that more than one of these problems may occur!

1. The most common problem people encounter is that there is a firewall between you and the SQL Server. You may get a message like this:

   SQL Server does not exist or access denied.

   This can even occur if you install SQL Server on your own machine!  If you have a firewall, make sure TCP and UDP ports 1433 are open.
   
   Another reason for this error is that your SQL Server is not configured to support TCP/IP connections.  If you are using SQL Server 2005 , you can configure your server using the 'SQL Server Surface Area Configuration' tool:
   
   
   1. Click on 'Surface Area Configuration for Services and Connections'
      
   2. In the dialog, click on 'Remote Connections' under the 'Database Engines' node
      
   3. In the options on the right, Check the 'Local and Remote Connections' option, the make sure TCP/IP is one of the supported protocols
      
   
   If you are running SQL Server 2000 or before , you'll need to use the SvrNetCn.exe utility to enable TCP/IP connections. You can find SvrNetCn.exe in your Microsoft SQL Server Binn folder, under Program Files.  When you launch the program you'll see a list of disabled protocols on the left.  If TCP/IP is disabled, select and enable it.
   
   
   
2. If you've just installed IssueView on your own SQL Server, you may get this message when you try to log in:

   Login failed for 'IM_User'. Reason: Not associated with a trusted SQL Server connection.

   This means that your SQL Server is not configured to support SQL Server Login IDs. To correct the problem, open SQL Enterprise Manager and rightClick on the Server. Select 'Properties' from the context menu. On the Security tab, make sure 'SQL Server and Windows' Authentication is checked (rather than 'Windows Only').

   If you don't have SQL Enterprise Manager (e.g., you're using MSDE), you can change this setting in the Windows Registry directly. Open RegEdit and navigate to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer. The REG_DWORD value LoginMode is set to 1 for Integrated Logins, and needs to be set to 2 to support 'SQL Server and Windows' Authentication required by IssueView.

3. One final possibility is that the SQL Server has stopped accepting connections.  This is a known problem with SQL Server, which does not have a reported solution.  It is extremely sporadic.  If none of the above fixes the problem, try rebooting the SQL Server.  You may well be able to connect after the reboot, and may never see the problem again.
   
   

Q. Can I install IssueView on a Named Instance of SQL Server?
A. Using IssueView on a SQL Server named instance is easy.  Just enter the Named instance during the install when you are asked to choose a SQL Server. You need to use the Instance Name syntax for the Database Server name: ServerName\Instance.  Users who use the NetSetup to install the client will be automatically configured to connect to the named instance.  If you set up a connection manually, you'll need to use the ServerName\Instance syntax for specifying the SQL Server

Q. How do I upgrade to the latest version?
A. If you are upgrading to the next major version (e.g., from 4.4 to 5.0), you may need to purchase a License Upgrade.  You can read about this major upgrade in the Upgrade FAQ.

If you are upgrading within a major version (e.g., from 4.0 to 4.4) you can just follow the steps below.

1. Download the latest version from our website
2. Run the installation package, preferably on the same machine where you originally installed
3. The install will prompt you to upgrade your existing database (if necessary)
4. Be sure to install the new NetSetup files
5. If you are upgrading to a newer major version, launch the IssueView client, and enter your new license code
6. If you are currently on version 4.4 or later :
   1. Log in as 'admin' and select 'System Configuration from the Tools menu.
   2. Click the 'Check for Updates' button
   3. Select the latest release from the list, and click OK.  All of your users will be upgraded the next time they log on.
   If you are upgrading from 4.3 or earlier :
   Instruct all of your users to connect to the new NetSetup and run Setup.exe.  The upgrade setup will update their files, without changing their configuration.  It takes less than a minute, and no reboot is required.

It is normally not necessary for all of your users to upgrade simultaneously. We work hard to preserve forwards and backwards compatibility between versions. If there is a version mismatch, some functionality may not be available, but no data will be lost or corrupted.  One exception to this is the upgrade to Version 5.0.  It supports HTML formatting in the text, which can't be displayed by previous versions.
Top

You can check to see if your database needs to be upgraded by logging in with the 'Admin' account. If the client you log in with is newer than the database version, it will prompt you through an upgrade.  It is important that no one be logged into the database other than the admin, to ensure that no tables are in use.  The upgrade process will warn you of this condition, and will not let you upgrade.

If you're sure no one is logged in, you may have some 'stranded' logons from people who turned off their computer without logging out of IssueView.  You can deleted these stranded logons by logging in as 'Admin', and selecting 'System Configuration' from the 'Tools' menu.  Click on the 'Logons' tab and delete the stranded logons.

After you've deleted the stranded logons, log back in as Admin, and you'll be able to upgrade your database.
Top

To set the default to reformat the IDs on a copy, right click on the target project, select 'Properties', and click on the 'ID Format' tab. Check the 'Reformat ID when copying an Issue from another project' option.
Top

Q. How do I configure IIS on Windows 2003 to support IssueView-Web?
A.When you install IIS on Windows 2003, it starts out in highly secure or "lockdown" mode. This means that many of the sophisticated web service features such as Active Server Pages (ASP), ASP.NET, and server-side includes (SSI) are not functional. In this lockdown mode nothing works and only static content can be served. To be able to use these features you can enable them by following these steps:

1. Open IIS Manager by selecting it from Programs->Administrative Tools->Internet Information Services Manager
2. In the left pane of the IIS Manager expand the node for the web server and click Web Service Extensions
3. In the right pane, you will see a list of web service extensions and the status (Prohibited or Allowed) for each
4. You can right click on the extension name and select Allow to enable it individually
5. If you want to allow all extensions for a specific application, you can select the Allow all Web service extensions for a particular application icon in the Tasks section
   
   The image below displays IIS Manager and gives you an idea of the process explained above.

 <system.web> ...

<!-- Set the trust to Full. WSS configures a very restrictive trust policy
that does not allow ASP.NET Web application to run correctly. -->
<trust level="Full" originUrl="" />

<!-- Enable the session module. This can also be enabled on the WSS Web.config,
but is not enabled by default. If you receive the following message:

   Parser ErrorMessage: The module 'Session' is already in the application and cannot be added again.

You can remove the following <httpModules></httpModules> section as session
is already enabled on the virtual server. -->

<httpModules>
<add name= "Session" type= "System.Web.SessionState.SessionStateModule" />< BR> </httpModules>

<!-- Enable session state for all the pages inthe Webapplication. -->
<pages enableSessionState= "true"
enableViewState= "true"
enableViewStateMac= "true"
validateRequest="false" />

</system.web>

Q. How do I load xsl Stylesheets for printing into my database?
A. You may want to add new xsl stylesheets into your database to support custom reports.  A couple of users have complained that the stylesheets didn't get imported when they upgraded from a previous version (hence this FAQ).  Here are instructions for loading the default stylesheets:

1. Download the stylesheets (Resources.zip).  Extract the contents of the .zip file and save them in your Resources folder (usually C:\Program Files\IssueView\Resources)
2. Log into IssueView, and select 'Manage Reports' from the Reports menu.
3. In the Reports dialog, click the Resources button
4. In the Resources dialog, click the New button and select GenericDetails.xsl as the file.  Select 'XSL Stylesheet' as the Resource Type.
5. Click OK to save your changes, and repeat with GenericList.xsl.  It's the same basic process with Logo.gif, except the Resource Type is Image.
6. Close the Resources dialog, and the Reports dialog, then retry your report.