Hello,
Sure--but I would be okay (at least for now) just sending a hardcoded message (or one that doesn't need access to any httpContext values) to the assignee. Do you think doing that in IssueManager's SaveOrUpdate() function is the best place?
Hello,
Sure--but I would be okay (at least for now) just sending a hardcoded message (or one that doesn't need access to any httpContext values) to the assignee. Do you think doing that in IssueManager's SaveOrUpdate() function is the best place?
Failed to load resource: the server responded with a status of 500 (Internal Server Error) http://localhost/MyBugNet/Webservices/BugNetServices.asmx/js
Failed to load resource: the server responded with a status of 500 (Internal Server Error) http://localhost/MyBugNet/WebServices/BugNetServices.asmx/GetCategories
It seems my local web services is not working.
Event Log:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 12/6/2012 6:24:21 AM
Event time (UTC): 12/6/2012 11:24:21 AM Event ID: 2dda7de793e94f3f8890127eb41736cc Event sequence: 5 Event occurrence: 1 Event detail code: 0 Application information: Application domain: /LM/W3SVC/1/ROOT/MyBugNet-2-129992666578432920 Trust level: Full Application Virtual Path: /MyBugNet Application Path: C:\inetpub\wwwroot\bugnet\ Machine name: SGAUTHIER7 Process information: Process ID: 5428 Process name: w3wp.exe Account name: IIS APPPOOL\Default Exception information: Exception type: InvalidOperationException Exception message: Request format is unrecognized for URL unexpectedly ending in '/js'. at System.Web.Services.Protocols.WebServiceHandlerFactory.CoreGetHandler(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.WebServiceHandlerFactory.GetHandler(HttpContext context, String verb, String url, String filePath) at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Request information: Request URL: http://localhost/MyBugNet/Webservices/BugNetServices.asmx/js Request path: /MyBugNet/Webservices/BugNetServices.asmx/js User host address: ::1 User: Is authenticated: False Authentication Type: Thread account name: IIS APPPOOL\Default Thread information: Thread ID: 198 Thread account name: IIS APPPOOL\Default Is impersonating: False Stack trace: at System.Web.Services.Protocols.WebServiceHandlerFactory.CoreGetHandler(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.WebServiceHandlerFactory.GetHandler(HttpContext context, String verb, String url, String filePath) at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
I am not sure why you are getting this error but you can try adding this setting to your web.config
<configuration><system.web><webServices><protocols><addname="HttpGet"/><addname="HttpPost"/></protocols></webServices></system.web></configuration>
http://stackoverflow.com/a/654107
Glad you got it working. We did fix some application settings caching issues, but they are only refreshed after you save a setting or recycle the application.
Figured my issue out.
ASP.NET must be re-registered with IIS.
Here is the solution:
http://www.brutaldev.com/post/2011/08/22/Reset-BugNET-admin-password.aspx
Hello,
when I try to run install.aspx i get the following Errors:
00:00:00 - Installing Version: 1.1.213.0
00:00:00 - Installing Membership Provider:
00:00:00 - Executing Script: InstallCommon.sql
Success
00:00:00.3437038 - Executing Script: InstallMembership.sql
Success
00:00:01.1248488 - Executing Script: InstallProfile.sql
Success
00:00:01.3435694 - Executing Script: InstallRoles.sql
Success
00:00:01.8591251 - Installing BugNET Database:
00:00:01.8591251 - Executing Script: BugNET.Schema.SqlDataProvider.sqlError!
File | BugNET.Schema.SqlDataProvider.sql |
Error | In der Datenbank ist bereits ein Objekt mit dem Namen 'BugNet_UserProfiles' vorhanden. |
00:00:01.8747480 - Installing BugNET Default Data:
00:00:01.8747480 - Executing Script: BugNET.Data.SqlDataProvider.sqlError!
File | BugNET.Data.SqlDataProvider.sql |
Error | Verletzung der PRIMARY KEY-Einschränkung "PK_BugNet_Permissions". Ein doppelter Schlüssel kann in das Objekt "dbo.BugNet_Permissions" nicht eingefügt werden. Der doppelte Schlüsselwert ist (1). |
00:00:01.8747480 - Creating Administrator Account
Error: The 'BugNET.Providers.MembershipProviders.ExtendedSqlMembershipProvider' requires a database schema compatible with schema version '1'. However, the current database schema is not compatible with this version. You may need to
either install a compatible schema with aspnet_regsql.exe (available in the framework installation directory), or upgrade the provider to a newer version.
there have been a few tables created, so I think the connection to the Database works.
Any suggestions?
Edit: Tried a few more times and now it seems to work....
I think top priority should be the email notification to new users. There is no reason why an email isn't sent and is a glaring omission in my mind. Especially if the password has been randomly generated or reset.
Points 2 and 3 would be nice to haves in my opinion. Number 1 is essential!
It would be superb to be able to set in the project settings for new issues which values are default. As clems38 mentioned above, the ability to set Status to 'New' by default for new issues.
Hi there,
would like to request instruction to install this bugnet onto Shared hosting.
I am facing issue whereby "permission denied to config folder", when the hosting tech team set full permission, it return loop redirection error.
What version of Windows does the hosting company use as well what hosting company are you using?
At the very min the web.config and Uploads folder needs write permission for BugNET to operate properly.
This also depends on who you’re hosting with as some may configure a special account just for your hosting account that everything runs under. It is hard to give you advice for installing BugNET on a shared hosting account due to the differences each company may implement the hosting.