Activities of "terry bentley"

I upgraded this past week to ASP.Net Zero v1.2 and when I create a user I am getting the following error

System.Data.SqlClient.SqlException: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception: The wait operation timed out

If I comment out the two lines await _notificationSubscriptionManager.SubscribeToAllAvailableNotificationsAsync(user.ToUserIdentifier()); await _appNotifier.WelcomeToTheApplicationAsync(user); in CreateUserAsync (UserAppService.cs) the user is created without a problem.

I am assuming there must be a deadlock in the database but I am not seeing any deadlocks in the SQL Profiler although I do see a reference to exec sp_executesql N'DELETE [dbo].[AbpNotifications] WHERE ([Id] = @0)',N'@0 uniqueidentifier',@0='1F3986A1-72E3-4CF2-A761-670629B6EF43' just before the first rollback.

This is a bit confusing as this is the notification record that is being added in the main transaction that has not been committed yet.

Any Ideas? Thanks... Terry

Since upgrading to ASP.Zero 1.2.0 I am seeing three square boxes in Internet Explorer where there should be ellipsis and even a box where there is a <br /> on the html page. If I remove the "Open Sans" font from the tag using the "F12 Developer tool" the element shows correctly. Is there a workaround for this or have I missed copying one or more files across?

This problem does not occur for Microsoft Edge, Chrome, or Firefox.

Thanks... Terry

Side note: even though I have an ASP.Net license clicking the New Topic button in the Premium Forum does nothing (no error or anything)

If I enter an incorrect password for a valid username I get an error "There is no entity User with id: nn!" where nn is the user id with the username entered. If I enter an invalid username I get the expected invalid login error.

I have only noticed this since upgrading to Abp 1.2

Here is the stack trace: ERROR 2017-01-03 10:44:00,856 [5 ] Cipher.Web.Controllers.AccountController - There is no such an entity. Entity type: RtTech.Cipher.Authorization.Users.User, id: 36 Abp.Domain.Entities.EntityNotFoundException: There is no such an entity. Entity type: RtTech.Cipher.Authorization.Users.User, id: 36 at Abp.Domain.Repositories.AbpRepositoryBase2.<GetAsync>d__17.MoveNext() in D:\Halil\Github\aspnetboilerplate\src\Abp\Domain\Repositories\AbpRepositoryBase.cs:line 86 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Abp.Threading.InternalAsyncHelper.<AwaitTaskWithPostActionAndFinallyAndGetResult>d__51.MoveNext() in D:\Halil\Github\aspnetboilerplate\src\Abp\Threading\InternalAsyncHelper.cs:line 120 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Abp.Authorization.Users.AbpUserStore2.<GetUserNameFromDatabaseAsync>d__64.MoveNext() in D:\Halil\Github\module-zero\src\Abp.Zero\Authorization\Users\AbpUserStore.cs:line 0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Abp.Authorization.Users.AbpUserManager2.<UpdateAsync>d__41.MoveNext() in D:\Halil\Github\module-zero\src\Abp.Zero\Authorization\Users\AbpUserManager.cs:line 343 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNet.Identity.TaskExtensions.CultureAwaiter1.GetResult() at Microsoft.AspNet.Identity.UserManager2.<AccessFailedAsync>d__157.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Abp.Authorization.AbpLogInManager3.<TryLockOutAsync>d__38.MoveNext() in D:\Halil\Github\module-zero\src\Abp.Zero\Authorization\AbpLoginManager.cs:line 259 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Abp.Authorization.AbpLogInManager3.<LoginAsyncInternal>d__35.MoveNext() in D:\Halil\Github\module-zero\src\Abp.Zero\Authorization\AbpLoginManager.cs:line 182 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Abp.Authorization.AbpLogInManager3.<LoginAsync>d__34.MoveNext() in D:\Halil\Github\module-zero\src\Abp.Zero\Authorization\AbpLoginManager.cs:line 0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Abp.Threading.InternalAsyncHelper.<AwaitTaskWithPostActionAndFinallyAndGetResult>d__51.MoveNext() in D:\Halil\Github\aspnetboilerplate\src\Abp\Threading\InternalAsyncHelper.cs:line 120 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter1.GetResult() at RtTech.Cipher.Web.Controllers.AccountController.<GetLoginResultAsync>d__22.MoveNext() in C:\Users\bentleyt\Source\Repos\cipher\src\RtTech.Cipher.Web\Controllers\AccountController.cs:line 210 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter1.GetResult() at RtTech.Cipher.Web.Controllers.AccountController.<Login>d__19.MoveNext() in C:\Users\bentleyt\Source\Repos\cipher\src\RtTech.Cipher.Web\Controllers\AccountController.cs:line 136 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Abp.Threading.InternalAsyncHelper.<AwaitTaskWithPostActionAndFinallyAndGetResult>d__51.MoveNext() in D:\Halil\Github\aspnetboilerplate\src\Abp\Threading\InternalAsyncHelper.cs:line 120 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Mvc.Async.TaskAsyncActionDescriptor.EndExecute(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<BeginInvokeAsynchronousActionMethod>b__36(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult1.CallEndDelegate(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResultBase1.End() at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3d() at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f() at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f() at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f() at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass33.<BeginInvokeActionMethodWithFilters>b__32(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult1.CallEndDelegate(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResultBase`1.End() at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass21.<>c__DisplayClass2b.

Hi - the problem was occurring with a basic login (not impersonation). It also happened on all browsers I tried.

I found a few more differences in files between what I had and the new version of the Abp and was able to resolve the anti-forgery token error.

Everything seems to now be working.

Thanks... Terry

Sorry - I solve the problem. Never fails that I spend hours trying to resolve the issue myself and then as soon as I post I see the problem.

In this case, I forgot to enter the [DependsOn( typeof(AbpZeroOwinModule),... in the WebModule class

Still having an issue with the following entries in the Log file but will need to work through that (unless someone know the answer)

WARN 2016-12-29 16:15:14,416 [25 ] ity.AntiForgery.AbpMvcAntiForgeryManager - The provided anti-forgery token was meant for a different claims-based user than the current user. WARN 2016-12-29 16:15:14,578 [25 ] rity.AntiForgery.AbpAntiForgeryApiFilter - Empty or invalid anti forgery header token. WARN 2016-12-29 16:15:14,748 [25 ] rity.AntiForgery.AbpAntiForgeryApiFilter - Requested URI: <a class="postlink" href="http://localhost:6234/api/services/app/session/GetCurrentLoginInformation">http://localhost:6234/api/services/app/ ... nformation</a>

I just upgraded the Abp and ASPNet Zero to 1.2.0 after not upgrading for a few months. I think I made all the breaking change adjustments in the code and database but I must have missed something as I am getting the following error when I try to run it IUserTokenProviderAccessor should be instance of OwinUserTokenProviderAccessor!

App_Start\Startup.cs at the line app.RegisterDataProtectionProvider()

Any guidance as to where to look would be appreciated. Terry

I'm also encountering very strange behavior with the abp.timing.convertToUserTimezone in the abp.moment.js (which is the one that is getting executed) I set the user time zone to Pacific time I pass in the current local time using Date.now() which is 1469464471941 momentDate._d : Mon Jul 25 2016 13:34:31 GMT-0300 (Atlantic Daylight Time) - this is correct and the targetDate returned : Mon Jul 25 2016 06:34:31 GMT-0300 (Atlantic Daylight Time) -not correct

The targetDate should be Mon Jul 25 2016 09:34:31 GMT-0700 (Pacific Daylight Time)

There are two errors here. It has not first set the time to UTC before converting it to Pacific so it is out by 3 hours and it has left the "GMT -0300 (Atlantic Daylight Time)"

I have been trying to figure out how to have a user time zone in addition to the current local machine time zone and UTC server time zone. As I was working through the abp moment enhancements I see that there are two different copies of abp.timing.convertToUserTimezone. They are in: Web\Abp\Framework\scripts\libs\abp.moment.js Web\Abp\Framework\scripts\abp.js The first returns a moment date object and the second returns a date. Was this intentional?

I was planning on using the moment.tz.setDefault to change the user time zone. Any ideas if this is the way to go?

Thanks

I was wondering if you had a list of features that you will be adding in the next 6 month? By the way, the ones you have added over the last six months have been great. Excellent job! I would like to set user and role permission at a product level. Only specific roles and users would be able to view, update, delete, ... particular products. If this is something on your "to do list" I will hold off adding it. If not I will get started on it now. Thanks... Terry

Was able to solve the problem. I published the web application to another local workstation and discovered that the "compilation" entry that I added to web.config to fix the first error resulted in a duplicate compilation entry (which was causing the 500 error on Azure) . I fixed this error and everything worked!