Quantcast
Channel: BugNET Issue Tracker (Moved to GitHub)
Viewing all 2179 articles
Browse latest View live

Updated Wiki: Installing BugNET

$
0
0

Installing BugNET

Requirements
Downloading
Installing Using SQL Server Express
Installing Using SQL Server
Install using the Web Deployment Package
Upgrading
Alternate Installation Tutorial

There are three ways you can install BugNET. You can:
  • Install it using the Web Deployment Package.
  • Download the BugNET .zip file and install it as described in Manually Installing BugNET Using a zip file.
  • Download the BugNET source code and build BugNET from the command line or in Visual Studio.

This topic shows how to install BugNET using the Install and Web Deploy packages.

Requirements

The minimum requirements for running BugNET are the following:
  • ASP.NET 4
  • A web server such as IIS Express 8, 7.5 or IIS 7.x.
  • Microsoft SQL Server 2008 Express or greater.

When installing IIS, make sure you enable the ASP.NET IIS modules. Also make sure that you run BugNET in an integrated pipeline ASP.NET 4 application pool.

Downloading the .zip File

Download the BugNET .zip file from CodePlex. Select the X.X.XXX Install.zip file for the latest build of BugNET as shown in the following illustration:

Install_downloadzip.png

Installing Using SQL Server Express

  1. Extract the contents of the install package to a folder on your computer.
  2. Create a directory in the c:\inetpub\wwwroot\ folder called bugnet (c:\inetpub\wwwroot\bugnet)
  3. Copy the contents of the BugNET folder in the install package to the c:\inetpub\wwwroot\bugnet\ folder
  4. Go to the properties of the following folders / files and click on the Security tab, be sure to add the permissions for the appropriate user (WinXp/2000 uses the local ASPNET account, Win2003/Vista/2008/7 use the local Network Service account). Give this account modify permissions of the following folders (if necessary):
    • Uploads - if using file system based uploads
    • App_Data - This folder is where BugNET stores its database.
  5. Create a virtual directory in IIS for the bugnet folder.
  6. Open up the the web server IIS Console, Start-> Run-> INETMGR
  7. Expand the websites node
  8. Expand the default websites node
  9. Right click on the BugNET folder under the default website, click on Convert to Application, if you don't have that option, choose properties and then add the application.
  10. If you are using IIS 7, configure it to run in integrated mode, and configure the application pool to run the .NET Framework version 4.
  11. Browse to the website using http://localhost/BugNet/Install/Install.aspx. The installation process will now start.

When the installation is complete, you may log in with the admin user account.

Username: admin
Password: password

Installing Using SQL Server

  1. Extract the contents of the install package to a folder on your computer.
  2. Create a directory in the c:\inetpub\wwwroot\ folder called bugnet (c:\inetpub\wwwroot\bugnet)
  3. Copy the contents of the BugNET folder in the install package to the c:\inetpub\wwwroot\bugnet\ folder
  4. Go to the properties of the c:\inetpub\wwwroot\bugnet\ folder, click on the Security tab, be sure to add the permissions for the appropriate user (WinXp/2000 uses the local ASPNET account, Win2003/Vista/2008/7 use the local Network Service account). Give this account modify permissions on (if necessary):
    • Uploads - if using file system based uploads
  5. Create a virtual directory in IIS for the bugnet folder.
  6. Open up the the web server IIS Console, start-> run-> INETMGR
  7. Expand the websites node
  8. Expand the default websites node
  9. Right click on the BugNET folder under the default website, click on Convert to Application, if you don't have that option, choose properties and then add the application.
  10. Configure the database server.
    1. Load the SQL Server Management tool
    2. Expand the Server/Security node
    3. Create a blank SQL Database (e.g db name 'BugNet') on your sql server using a case insensitive collation.
    4. Configure the SQL User Security/Account to allow IIS and ASP.NET access to the database in SQL.

To Use Integrated Security - Windows Authentication (Recommended)

  1. Verify that NT Authority\Network Service is listed, if not add a new account and search for the local NETWORK SERVICE user (if using Windows XP/2000 use the local ASPNET account)
  2. Right click on the NT Authority\Network Service account and choose properties.
  3. Choose the User Mapping section on the left. Select your database on the right, and then down below choose the db_owner option, click OK
  4. Edit the Web.config file with a text editor of your choice. Find the BugNET connection string setting and change the connectionString.
<connectionStrings><clear/><addname="BugNET"connectionString="server=MyServer;database=BugNet;Trusted_Connection=True"providerName="System.Data.SqlClient"/></connectionStrings>

To Use SQL User Security (requires mixed mode authentication to be enabled in SQL Server)

  1. Right click on Server/Security and choose New Login
  2. Define new SQL Server authentication login information, username/password.
  3. From the User Mapping section choose the new BugNET database and configure the db_owner role membership. Click OK.
  4. Edit the Web.config file with a text editor of your choice. Find the BugNET connection string setting and change the connectionString.
<connectionStrings><clear/><addname="BugNET"connectionString="server=MyServer;database=BugNet;uid=BugNet;pwd=BugNet"providerName="System.Data.SqlClient"/></connectionStrings>

Browse to the website using http://localhost/BugNet/Install/Install.aspx. The installation process will now start.

InstallationComplete.png

When completed, you may log in with the admin user account.

Username: admin
Password: password

Upgrading

Verify that your application pool in IIS is running under .NET 4.5.
  1. Backup live database & files
  2. Put App_Offline.html in live BugNET directory.
  3. Download new distribution to local machine
  4. Use WinMerge or equivalent to compare new and old web.configs. Copy across the connection string to the new one.
  5. Start BugNET, hit the home page to verify that it compiles

The database is automatically upgraded when you hit the home page. You should see a log of what's been done plus a "success" message after a few minutes.

Alternate Installation Tutorial

http://www.dotnetcamp.com/post/2012/10/20/How-to-install-BugNet.aspx

Updated Wiki: Installing BugNET

$
0
0

Installing BugNET

Requirements
Downloading
Installing Using SQL Server Express
Installing Using SQL Server
Install using the Web Deployment Package
Upgrading
Alternate Installation Tutorial

There are three ways you can install BugNET. You can:
  • Install it using the Web Deployment Package.
  • Download the BugNET .zip file and install it as described in Manually Installing BugNET Using a zip file.
  • Download the BugNET source code and build BugNET from the command line or in Visual Studio.

This topic shows how to install BugNET using the Install and Web Deploy packages.

Requirements

The minimum requirements for running BugNET are the following:
  • ASP.NET 4
  • A web server such as IIS Express 8, 7.5 or IIS 7.x.
  • Microsoft SQL Server 2008 Express or greater.

When installing IIS, make sure you enable the ASP.NET IIS modules. Also make sure that you run BugNET in an integrated pipeline ASP.NET 4 application pool.

Downloading the .zip File

Download the BugNET .zip file from CodePlex. Select the X.X.XXX Install.zip file for the latest build of BugNET as shown in the following illustration:

Install_downloadzip.png

Installing Using SQL Server Express

  1. Extract the contents of the install package to a folder on your computer.
  2. Create a directory in the c:\inetpub\wwwroot\ folder called bugnet (c:\inetpub\wwwroot\bugnet)
  3. Copy the contents of the BugNET folder in the install package to the c:\inetpub\wwwroot\bugnet\ folder
  4. Go to the properties of the following folders / files and click on the Security tab, be sure to add the permissions for the appropriate user (WinXp/2000 uses the local ASPNET account, Win2003/Vista/2008/7 use the local Network Service account). Give this account modify permissions of the following folders (if necessary):
    • Uploads - if using file system based uploads
    • App_Data - This folder is where BugNET stores its database.
  5. Create a virtual directory in IIS for the bugnet folder.
  6. Open up the the web server IIS Console, Start-> Run-> INETMGR
  7. Expand the websites node
  8. Expand the default websites node
  9. Right click on the BugNET folder under the default website, click on Convert to Application, if you don't have that option, choose properties and then add the application.
  10. If you are using IIS 7, configure it to run in integrated mode, and configure the application pool to run the .NET Framework version 4.
  11. Browse to the website using http://localhost/BugNet/Install/Install.aspx. The installation process will now start.

When the installation is complete, you may log in with the admin user account.

Username: admin
Password: password

Installing Using SQL Server

  1. Extract the contents of the install package to a folder on your computer.
  2. Create a directory in the c:\inetpub\wwwroot\ folder called bugnet (c:\inetpub\wwwroot\bugnet)
  3. Copy the contents of the BugNET folder in the install package to the c:\inetpub\wwwroot\bugnet\ folder
  4. Go to the properties of the c:\inetpub\wwwroot\bugnet\ folder, click on the Security tab, be sure to add the permissions for the appropriate user (WinXp/2000 uses the local ASPNET account, Win2003/Vista/2008/7 use the local Network Service account). Give this account modify permissions on (if necessary):
    • Uploads - if using file system based uploads
  5. Create a virtual directory in IIS for the bugnet folder.
  6. Open up the the web server IIS Console, start-> run-> INETMGR
  7. Expand the websites node
  8. Expand the default websites node
  9. Right click on the BugNET folder under the default website, click on Convert to Application, if you don't have that option, choose properties and then add the application.
  10. Configure the database server.
    1. Load the SQL Server Management tool
    2. Expand the Server/Security node
    3. Create a blank SQL Database (e.g db name 'BugNet') on your sql server using a case insensitive collation.
    4. Configure the SQL User Security/Account to allow IIS and ASP.NET access to the database in SQL.

To Use Integrated Security - Windows Authentication (Recommended)

  1. Verify that NT Authority\Network Service is listed, if not add a new account and search for the local NETWORK SERVICE user (if using Windows XP/2000 use the local ASPNET account)
  2. Right click on the NT Authority\Network Service account and choose properties.
  3. Choose the User Mapping section on the left. Select your database on the right, and then down below choose the db_owner option, click OK
  4. Edit the Web.config file with a text editor of your choice. Find the BugNET connection string setting and change the connectionString.
<connectionStrings><clear/><addname="BugNET"connectionString="server=MyServer;database=BugNet;Trusted_Connection=True"providerName="System.Data.SqlClient"/></connectionStrings>

To Use SQL User Security (requires mixed mode authentication to be enabled in SQL Server)

  1. Right click on Server/Security and choose New Login
  2. Define new SQL Server authentication login information, username/password.
  3. From the User Mapping section choose the new BugNET database and configure the db_owner role membership. Click OK.
  4. Edit the Web.config file with a text editor of your choice. Find the BugNET connection string setting and change the connectionString.
<connectionStrings><clear/><addname="BugNET"connectionString="server=MyServer;database=BugNet;uid=BugNet;pwd=BugNet"providerName="System.Data.SqlClient"/></connectionStrings>

Browse to the website using http://localhost/BugNet/Install/Install.aspx. The installation process will now start.

InstallationComplete.png

When completed, you may log in with the admin user account.

Username: admin
Password: password

Alternate Installation Tutorial

http://www.dotnetcamp.com/post/2012/10/20/How-to-install-BugNet.aspx

Updated Wiki: Installing BugNET

$
0
0

Installing BugNET

Requirements
Downloading
Installing Using SQL Server Express
Installing Using SQL Server
Install using the Web Deployment Package
Upgrading
Alternate Installation Tutorial

There are three ways you can install BugNET. You can:
  • Install it using the Web Deployment Package.
  • Download the BugNET .zip file and install it as described in Manually Installing BugNET Using a zip file.
  • Download the BugNET source code and build BugNET from the command line or in Visual Studio.

This topic shows how to install BugNET using the Install and Web Deploy packages.

Requirements

The minimum requirements for running BugNET are the following:
  • ASP.NET 4
  • A web server such as IIS Express 8, 7.5 or IIS 7.x.
  • Microsoft SQL Server 2008 Express or greater.

When installing IIS, make sure you enable the ASP.NET IIS modules. Also make sure that you run BugNET in an integrated pipeline ASP.NET 4 application pool.

Downloading the .zip File

Download the BugNET .zip file from CodePlex. Select the X.X.XXX Install.zip file for the latest build of BugNET as shown in the following illustration:

Install_downloadzip.png

Installing Using SQL Server Express

  1. Extract the contents of the install package to a folder on your computer.
  2. Create a directory in the c:\inetpub\wwwroot\ folder called bugnet (c:\inetpub\wwwroot\bugnet)
  3. Copy the contents of the BugNET folder in the install package to the c:\inetpub\wwwroot\bugnet\ folder
  4. Go to the properties of the following folders / files and click on the Security tab, be sure to add the permissions for the appropriate user (WinXp/2000 uses the local ASPNET account, Win2003/Vista/2008/7 use the local Network Service account). Give this account modify permissions of the following folders (if necessary):
    • Uploads - if using file system based uploads
    • App_Data - This folder is where BugNET stores its database.
  5. Create a virtual directory in IIS for the bugnet folder.
  6. Open up the the web server IIS Console, Start-> Run-> INETMGR
  7. Expand the websites node
  8. Expand the default websites node
  9. Right click on the BugNET folder under the default website, click on Convert to Application, if you don't have that option, choose properties and then add the application.
  10. If you are using IIS 7, configure it to run in integrated mode, and configure the application pool to run the .NET Framework version 4.
  11. Browse to the website using http://localhost/BugNet/Install/Install.aspx. The installation process will now start.

When the installation is complete, you may log in with the admin user account.

Username: admin
Password: password

Installing Using SQL Server

  1. Extract the contents of the install package to a folder on your computer.
  2. Create a directory in the c:\inetpub\wwwroot\ folder called bugnet (c:\inetpub\wwwroot\bugnet)
  3. Copy the contents of the BugNET folder in the install package to the c:\inetpub\wwwroot\bugnet\ folder
  4. Go to the properties of the c:\inetpub\wwwroot\bugnet\ folder, click on the Security tab, be sure to add the permissions for the appropriate user (WinXp/2000 uses the local ASPNET account, Win2003/Vista/2008/7 use the local Network Service account). Give this account modify permissions on (if necessary):
    • Uploads - if using file system based uploads
  5. Create a virtual directory in IIS for the bugnet folder.
  6. Open up the the web server IIS Console, start-> run-> INETMGR
  7. Expand the websites node
  8. Expand the default websites node
  9. Right click on the BugNET folder under the default website, click on Convert to Application, if you don't have that option, choose properties and then add the application.
  10. Configure the database server.
    1. Load the SQL Server Management tool
    2. Expand the Server/Security node
    3. Create a blank SQL Database (e.g db name 'BugNet') on your sql server using a case insensitive collation.
    4. Configure the SQL User Security/Account to allow IIS and ASP.NET access to the database in SQL.

To Use Integrated Security - Windows Authentication (Recommended)

  1. Verify that NT Authority\Network Service is listed, if not add a new account and search for the local NETWORK SERVICE user (if using Windows XP/2000 use the local ASPNET account)
  2. Right click on the NT Authority\Network Service account and choose properties.
  3. Choose the User Mapping section on the left. Select your database on the right, and then down below choose the db_owner option, click OK
  4. Edit the Web.config file with a text editor of your choice. Find the BugNET connection string setting and change the connectionString.
<connectionStrings><clear/><addname="BugNET"connectionString="server=MyServer;database=BugNet;Trusted_Connection=True"providerName="System.Data.SqlClient"/></connectionStrings>

To Use SQL User Security (requires mixed mode authentication to be enabled in SQL Server)

  1. Right click on Server/Security and choose New Login
  2. Define new SQL Server authentication login information, username/password.
  3. From the User Mapping section choose the new BugNET database and configure the db_owner role membership. Click OK.
  4. Edit the Web.config file with a text editor of your choice. Find the BugNET connection string setting and change the connectionString.
<connectionStrings><clear/><addname="BugNET"connectionString="server=MyServer;database=BugNet;uid=BugNet;pwd=BugNet"providerName="System.Data.SqlClient"/></connectionStrings>

Browse to the website using http://localhost/BugNet/Install/Install.aspx. The installation process will now start.

InstallationComplete.png

When completed, you may log in with the admin user account.

Username: admin
Password: password


Upgrading

Verify that your application pool in IIS is running under .NET 4.5.
  1. Backup live database & files
  2. Put App_Offline.html in live BugNET directory.
  3. Download new distribution to local machine
  4. Use WinMerge or equivalent to compare new and old web.configs. Copy across the connection string to the new one.
  5. Start BugNET, hit the home page to verify that it compiles

The database is automatically upgraded when you hit the home page. You should see a log of what's been done plus a "success" message after a few minutes.

Alternate Installation Tutorial

http://www.dotnetcamp.com/post/2012/10/20/How-to-install-BugNet.aspx

Updated Wiki: Installing BugNET

$
0
0

Installing BugNET

Requirements
Downloading
Installing Using SQL Server Express
Installing Using SQL Server
Install using the Web Deployment Package
Upgrading
Alternate Installation Tutorial

There are three ways you can install BugNET. You can:
  • Install it using the Web Deployment Package.
  • Download the BugNET .zip file and install it as described in Manually Installing BugNET Using a zip file.
  • Download the BugNET source code and build BugNET from the command line or in Visual Studio.

This topic shows how to install BugNET using the Install and Web Deploy packages.

Requirements

The minimum requirements for running BugNET are the following:
  • ASP.NET 4
  • A web server such as IIS Express 8, 7.5 or IIS 7.x.
  • Microsoft SQL Server 2008 Express or greater.

When installing IIS, make sure you enable the ASP.NET IIS modules. Also make sure that you run BugNET in an integrated pipeline ASP.NET 4 application pool.

Downloading the .zip File

Download the BugNET .zip file from CodePlex. Select the X.X.XXX Install.zip file for the latest build of BugNET as shown in the following illustration:

Install_downloadzip.png

Installing Using SQL Server Express

  1. Extract the contents of the install package to a folder on your computer.
  2. Create a directory in the c:\inetpub\wwwroot\ folder called bugnet (c:\inetpub\wwwroot\bugnet)
  3. Copy the contents of the BugNET folder in the install package to the c:\inetpub\wwwroot\bugnet\ folder
  4. Go to the properties of the following folders / files and click on the Security tab, be sure to add the permissions for the appropriate user (WinXp/2000 uses the local ASPNET account, Win2003/Vista/2008/7 use the local Network Service account). Give this account modify permissions of the following folders (if necessary):
    • Uploads - if using file system based uploads
    • App_Data - This folder is where BugNET stores its database.
  5. Create a virtual directory in IIS for the bugnet folder.
  6. Open up the the web server IIS Console, Start-> Run-> INETMGR
  7. Expand the websites node
  8. Expand the default websites node
  9. Right click on the BugNET folder under the default website, click on Convert to Application, if you don't have that option, choose properties and then add the application.
  10. If you are using IIS 7, configure it to run in integrated mode, and configure the application pool to run the .NET Framework version 4.
  11. Browse to the website using http://localhost/BugNet/Install/Install.aspx. The installation process will now start.

When the installation is complete, you may log in with the admin user account.

Username: admin
Password: password

Installing Using SQL Server

  1. Extract the contents of the install package to a folder on your computer.
  2. Create a directory in the c:\inetpub\wwwroot\ folder called bugnet (c:\inetpub\wwwroot\bugnet)
  3. Copy the contents of the BugNET folder in the install package to the c:\inetpub\wwwroot\bugnet\ folder
  4. Go to the properties of the c:\inetpub\wwwroot\bugnet\ folder, click on the Security tab, be sure to add the permissions for the appropriate user (WinXp/2000 uses the local ASPNET account, Win2003/Vista/2008/7 use the local Network Service account). Give this account modify permissions on (if necessary):
    • Uploads - if using file system based uploads
  5. Create a virtual directory in IIS for the bugnet folder.
  6. Open up the the web server IIS Console, start-> run-> INETMGR
  7. Expand the websites node
  8. Expand the default websites node
  9. Right click on the BugNET folder under the default website, click on Convert to Application, if you don't have that option, choose properties and then add the application.
  10. Configure the database server.
    1. Load the SQL Server Management tool
    2. Expand the Server/Security node
    3. Create a blank SQL Database (e.g db name 'BugNet') on your sql server using a case insensitive collation.
    4. Configure the SQL User Security/Account to allow IIS and ASP.NET access to the database in SQL.

To Use Integrated Security - Windows Authentication (Recommended)

  1. Verify that NT Authority\Network Service is listed, if not add a new account and search for the local NETWORK SERVICE user (if using Windows XP/2000 use the local ASPNET account)
  2. Right click on the NT Authority\Network Service account and choose properties.
  3. Choose the User Mapping section on the left. Select your database on the right, and then down below choose the db_owner option, click OK
  4. Edit the Web.config file with a text editor of your choice. Find the BugNET connection string setting and change the connectionString.
<connectionStrings><clear/><addname="BugNET"connectionString="server=MyServer;database=BugNet;Trusted_Connection=True"providerName="System.Data.SqlClient"/></connectionStrings>

To Use SQL User Security (requires mixed mode authentication to be enabled in SQL Server)

  1. Right click on Server/Security and choose New Login
  2. Define new SQL Server authentication login information, username/password.
  3. From the User Mapping section choose the new BugNET database and configure the db_owner role membership. Click OK.
  4. Edit the Web.config file with a text editor of your choice. Find the BugNET connection string setting and change the connectionString.
<connectionStrings><clear/><addname="BugNET"connectionString="server=MyServer;database=BugNet;uid=BugNet;pwd=BugNet"providerName="System.Data.SqlClient"/></connectionStrings>

Browse to the website using http://localhost/BugNet/Install/Install.aspx. The installation process will now start.

InstallationComplete.png

When completed, you may log in with the admin user account.

Username: admin
Password: password

Install using the Web Deployment Package

To install BugNET via the web deployment package please refer to the following instructions on how to Import a Package through IIS Manager

Upgrading

Verify that your application pool in IIS is running under .NET 4.5.
  1. Backup live database & files
  2. Put App_Offline.html in live BugNET directory.
  3. Download new distribution to local machine
  4. Use WinMerge or equivalent to compare new and old web.configs. Copy across the connection string to the new one.
  5. Start BugNET, hit the home page to verify that it compiles

The database is automatically upgraded when you hit the home page. You should see a log of what's been done plus a "success" message after a few minutes.

Alternate Installation Tutorial

http://www.dotnetcamp.com/post/2012/10/20/How-to-install-BugNet.aspx

New Post: Upgrading

New Post: Upgrading

$
0
0
Thanks for fixing that error, I can see the upgrade section now.

New Post: Error upgrading 315 to 327 Procedure BugNet_Project_GetAllProjects

$
0
0
I've kept the version 315 database, extracted all files from the .ZIP and replaced the connectionstring. After running /install/install.aspx and returning to Default.aspx I get:

"Procedure BugNet_Project_GetAllProjects has no parameters and arguments were supplied.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Procedure BugNet_Project_GetAllProjects has no parameters and arguments were supplied.

Source Error:


An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[SqlException (0x80131904): Procedure BugNet_Project_GetAllProjects has no parameters and arguments were supplied.]
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction) +392
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) +815
System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) +4515
System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() +61
System.Data.SqlClient.SqlDataReader.get_MetaData() +138
System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +6738869
System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) +6741487
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource
1 completion, Int32 timeout, Task& task, Boolean asyncWrite) +586
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +107
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +288
System.Data.SqlClient.SqlCommand.ExecuteReader() +302
BugNET.Providers.DataProviders.SqlDataProvider.ExecuteReaderCmd(SqlCommand sqlCmd, GenerateListFromReader1 gcfr, List1& list) +162
BugNET.Providers.DataProviders.SqlDataProvider.GetAllProjects(Nullable`1 activeOnly) +325
BugNET._Default.Page_Load(Object sender, EventArgs e) +471
System.Web.UI.Control.LoadRecursive() +71
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3178"

Any suggestions what I might be doing wrong?

New Post: Error upgrading 315 to 327 Procedure BugNet_Project_GetAllProjects

$
0
0
Did the upgrade script run without errors? There was an update to the GetAllProjects stored procedure that should have been executed during the install.

New Post: Error upgrading 315 to 327 Procedure BugNet_Project_GetAllProjects

$
0
0
After replacing the database with the 315 version the Install page is convinced I'm running code 327 and database 327, so no script is executed. On a previous attempt the script did run, but with an error:

"Msg 3728, Level 16, State 1, Line 2
'PK_BugNet_RelatedIssues' is not a constraint.
Msg 3727, Level 16, State 0, Line 2
Could not drop constraint. See previous errors."

I located the update script and ran it manually, which resulted in the same error, but it's working now.

Thanks for your support!

Created Unassigned: User still has access to project when removed from members [264]

$
0
0
Hello All,

thanks for bugnet, it is great.

I have version 1.6.315.0

Short version: I have a user not mapped to a project, but yet she can see it - how can I fix this.

More detail:
I added a user and made her a member of a project, but then removed her from the project. However, she still has access to it. I added and removed her again to be sure. The add and delete are happening correctly in the db, I can see her user id moving as it should but for some reason, she still can see the project when she should not.

I have searched for every column in the db for userid and tried to find a place that is allowing her to see the project where she is not mapped.

Any advice please ?

Commented Unassigned: User still has access to project when removed from members [264]

$
0
0
Hello All,

thanks for bugnet, it is great.

I have version 1.6.315.0

Short version: I have a user not mapped to a project, but yet she can see it - how can I fix this.

More detail:
I added a user and made her a member of a project, but then removed her from the project. However, she still has access to it. I added and removed her again to be sure. The add and delete are happening correctly in the db, I can see her user id moving as it should but for some reason, she still can see the project when she should not.

I have searched for every column in the db for userid and tried to find a place that is allowing her to see the project where she is not mapped.

Any advice please ?
Comments: Have you also assigned them to a user role as well?

Commented Unassigned: User still has access to project when removed from members [264]

$
0
0
Hello All,

thanks for bugnet, it is great.

I have version 1.6.315.0

Short version: I have a user not mapped to a project, but yet she can see it - how can I fix this.

More detail:
I added a user and made her a member of a project, but then removed her from the project. However, she still has access to it. I added and removed her again to be sure. The add and delete are happening correctly in the db, I can see her user id moving as it should but for some reason, she still can see the project when she should not.

I have searched for every column in the db for userid and tried to find a place that is allowing her to see the project where she is not mapped.

Any advice please ?
Comments: Hello dubeaud, Thank you for your reply. The user is mapped to a role for Project 1 and this works well. The user is NOT mapped to any role for project 2, but still she can work on Project 2. I cannot see why this is? Any advice?

Commented Unassigned: User still has access to project when removed from members [264]

$
0
0
Hello All,

thanks for bugnet, it is great.

I have version 1.6.315.0

Short version: I have a user not mapped to a project, but yet she can see it - how can I fix this.

More detail:
I added a user and made her a member of a project, but then removed her from the project. However, she still has access to it. I added and removed her again to be sure. The add and delete are happening correctly in the db, I can see her user id moving as it should but for some reason, she still can see the project when she should not.

I have searched for every column in the db for userid and tried to find a place that is allowing her to see the project where she is not mapped.

Any advice please ?
Comments: Is the user a project administrator or super user, super users have access to everything in BugNET and project administrators would have access to everything in a project.

Commented Unassigned: User still has access to project when removed from members [264]

$
0
0
Hello All,

thanks for bugnet, it is great.

I have version 1.6.315.0

Short version: I have a user not mapped to a project, but yet she can see it - how can I fix this.

More detail:
I added a user and made her a member of a project, but then removed her from the project. However, she still has access to it. I added and removed her again to be sure. The add and delete are happening correctly in the db, I can see her user id moving as it should but for some reason, she still can see the project when she should not.

I have searched for every column in the db for userid and tried to find a place that is allowing her to see the project where she is not mapped.

Any advice please ?
Comments: Hello dubeaud, Thank you again for your reply. The user had QA mapped for Project 1. The user has nothing mapped for Project 2. I checked this in the GUI and also in the database. I have reviewed the UserId in the ProjectManagerUserId, she is not mapped there. IS that what you refer to as "Project Administrator"

Released: BugNET 1.6.329 (Sep 02, 2014)


Updated Release: BugNET 1.6.329 (Sep 02, 2014)

Released: BugNET 1.6.327 (Aug 23, 2014)

Updated Release: BugNET 1.6.327 (Aug 23, 2014)

New Post: Configuration of Active Directory

$
0
0
You mean, when configured, the user accounts in BugNET will automatically have an account in the AD?

New Post: Columns in the exported Excel are fixed

$
0
0
Is there a way to add/remove columns in the excel before exporting the list of issues? I tried to remove some columns in the tool, but after exporting to excel, the tool always have fixed columns.

I hope the next release will fix this.
Viewing all 2179 articles
Browse latest View live