I just ran the NuGet package manager console command to update ALL my ABP NuGet packages.
get-project -all | get-package | ?{ $_.Id -like 'Abp*' } | update-package
After the NuGet updates, I built the solution and I am getting the errors in just two "typescript" files. I am not at all familiar with typescript.
Build Errors: [https://drive.google.com/file/d/0BzbrPy41GhA4UGpnT0NSODJJVDg/view?usp=sharing])
Can you please tell me how to resolve these errors? Thanks!
Thanks very much! Apologies for taking your time on this issue!
Sometimes one cannot see the forest due to the trees! :lol:
I have emailed you the solution. Thanks!
The tenant DB was created I just don't see the tenant entry in the tenant table or index page of tenants. In the new tenant DB, it does seem to have updated all the tables with data. I dont see the permissions or roles created. At this point I don't know how many steps in the tenant creation process are not completed?
public async Task<int> CreateWithAdminUserAsync(string tenancyName, string name, string adminPassword, string adminEmailAddress, string connectionString, bool isActive, int? editionId, bool shouldChangePasswordOnNextLogin, bool sendActivationEmail)
{
int newTenantId;
long newAdminId;
using (var uow = _unitOfWorkManager.Begin(TransactionScopeOption.RequiresNew))
When you say remove transaction from create tenant methods. Are you referring to the "UOW" using stmt above? If yes, this is used in quite a few places in ABP solution. Will I have to remove this everywhere?
I tried to setup a new tenant on my hosted application. I used the create tenant UI to setup the new tenant. The DB was created and all the tables were created in the new DB instance. However the process did not complete normally. The ABP app reported the error message below in the logs.
System.Data.Entity.Core.EntityException: The underlying provider failed on Open. ---> System.Transactions.TransactionManagerCommunicationException: Network access for Distributed Transaction Manager (MSDTC) has been disabled. Please enable DTC for network access in the security configuration for MSDTC using the Component Services Administrative tool. ---> System.Runtime.InteropServices.COMException: The transaction manager has disabled its support for remote/network transactions. (Exception from HRESULT: 0x8004D024)
I spoke with my hosting support team about this error and if this feature can be enabled. They replied with below.
Unfortunately, MSDTC is not a supported feature on our hosting platform. You can probably find very few shared hosting providers supporting this feature. You should consider using SQL server's native transaction support.
Is there any other method for me to create the tenant?
Ok issue is resolved now!
The hosting team provided me with updated SMTP host name. Plus I had to remove the domain name from the ABP settings page to make it work. But emails are now going out. Thanks!
There are no references to "GetAddresses" method in the logs.txt file.
The hosting provider actually setup a simple ASPX page(within my domain) with the C# code below and it works just fine. This sends emails to any address.
protected void sendEmailButton_Click(object sender, EventArgs e)
{
MailMessage newMessage = new MailMessage();
newMessage.From = new MailAddress(fromTextBox.Text);
newMessage.To.Add(toTextBox.Text);
newMessage.Subject = subjectTextBox.Text;
newMessage.Body = messageBodyTextBox.Text;
SmtpClient smtp = new SmtpClient("mail.mydomain.com", 25);
NetworkCredential Credentials = new NetworkCredential("[email protected]", "xxxxx");
smtp.Credentials = Credentials;
smtp.Send(newMessage);
messageStatusLabel.Text = "Email sent";
}
Here you go... [https://drive.google.com/file/d/0BzbrPy41GhA4d18xSmJZQlJkRUk/view?usp=sharing])
It does not appear to even make the call to the address method?
I have deployed my ABP application to my hosting providers site. I have updated the email settings as needed for my hosting provider. The test email is working fine for email addresses on my domain. However, when I try to send out emails to any other domain, I keep getting the error below.
System.Net.Mail.SmtpFailedRecipientException: Mailbox unavailable. The server response was: Authentication is required for relay
at System.Net.Mail.SendMailAsyncResult.End(IAsyncResult result)
at System.Net.Mail.SmtpTransport.EndSendMail(IAsyncResult result)
at System.Net.Mail.SmtpClient.SendMailCallback(IAsyncResult result)
--- 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.Net.Mail.Smtp.SmtpEmailSender.d__3.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.Net.Mail.EmailSenderBase.d__6.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.Net.Mail.EmailSenderBase.d__4.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.Net.Mail.EmailSenderBase.d__2.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 Configuration.Host.HostSettingsAppService.d__21.Mo...
I opened a ticket with my hosting provider's support team. They have replied with the below response.
Yes, I know it works from your domain name because that is sent internally. I tested that, and it works fine. In order to relay out, you need to authenticate (i.e. supply username and password), or our mail servers won't relay it out (we don't allow unauthenticated users to send messages out because of spammers which get our mail servers blacklisted). I could probably place a test script in your account to prove to you that it's working, but that's not the problem. The problem is that your CMS (ASPNetZero) is not authenticating correctly, but I don't know where the code is to send email so I can't verify that's the problem.
I searched on the forum for other postings on the issue and found some of the email code. However I could not find the code where the credentials are getting used. Can you help me resolve this issue? Thanks!