I had fresh installation of Umbraco 4.7. On that i deployed published site from uSiteBuilder with my custom created document types and master pages. Aafter this i am getting following error:
Umbraco user used by USiteBuilder is not found or login name not unique. Please check your configuration (siteBuilderUserLoginName property)
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.Exception: Umbraco user used by USiteBuilder is not found or login name not unique. Please check your configuration (siteBuilderUserLoginName property)
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:
[Exception: Umbraco user used by USiteBuilder is not found or login name not unique. Please check your configuration (siteBuilderUserLoginName property)]
j.b() +96
l..ctor() +12
k.f() +23
k.g() +64
Vega.USiteBuilder.USiteBuilderHttpModule.BeginRequest(Object sender, EventArgs e) +5
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +148
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75
@Pinal, the problem you have is caused with the fact that you don't have 'admin' umbraco user. The workarround for this (untill we fix the issue) is that you create administrator user whose login name must be 'admin'. Password doesn't matter so you can put anything.
To get the site back, just remove Vega.USiteBuilder.dll from your bin folder and restart the website (it should restart automatically but just to be sure).
About ETA for this fix, we'll try fix it as soon as possible but we don't have planned date yet. For now, workarround is that you always have 'admin' user.
Sorry, I just realized that you have to do one more thing. It should be enough that you remove only Vega.USiteBuilder.dll from your bin folder but you also have to delete "USiteBuilderHttpModule" http module from your web.config. (it'll be added back automatically once you copy Vega.USiteBuidler.dll back to bin folder). Note that "USiteBuilderHttpModule" occurs on two places in the web.config
@Pinal, we just released a new version of uSiteBuilder (1.1) and it now supports setting any user account as uSiteBuilder service account. uSiteBuilder will check if you have a setting called "siteBuilderUserLoginName" under "appSettings" section of your web.config and if so, it will use that user for all insert/update/delete operations in Umbraco; if you don't have that settings set then it will try to use the "admin" account or throw exception if "admin" is not found.
Umbraco user used by USiteBuilder is not found or login name not unique.
I had fresh installation of Umbraco 4.7. On that i deployed published site from uSiteBuilder with my custom created document types and master pages. Aafter this i am getting following error:
Umbraco user used by USiteBuilder is not found or login name not unique. Please check your configuration (siteBuilderUserLoginName property)
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.Exception: Umbraco user used by USiteBuilder is not found or login name not unique. Please check your configuration (siteBuilderUserLoginName property)
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:
@Pinal, the problem you have is caused with the fact that you don't have 'admin' umbraco user. The workarround for this (untill we fix the issue) is that you create administrator user whose login name must be 'admin'. Password doesn't matter so you can put anything.
hummm yes we dont have any user named "admin". Any ETA for this fix and new release?
any way to create user directly in database... or else to bring site up...i will have to rollback all the deployment changes.
To get the site back, just remove Vega.USiteBuilder.dll from your bin folder and restart the website (it should restart automatically but just to be sure).
About ETA for this fix, we'll try fix it as soon as possible but we don't have planned date yet. For now, workarround is that you always have 'admin' user.
thanks... but removing only does not works Vega.USiteBuilder.dll we need to remove all the .dll files dependnet on this file.
Any way thanks.
Sorry, I just realized that you have to do one more thing. It should be enough that you remove only Vega.USiteBuilder.dll from your bin folder but you also have to delete "USiteBuilderHttpModule" http module from your web.config. (it'll be added back automatically once you copy Vega.USiteBuidler.dll back to bin folder). Note that "USiteBuilderHttpModule" occurs on two places in the web.config
@Pinal, we just released a new version of uSiteBuilder (1.1) and it now supports setting any user account as uSiteBuilder service account. uSiteBuilder will check if you have a setting called "siteBuilderUserLoginName" under "appSettings" section of your web.config and if so, it will use that user for all insert/update/delete operations in Umbraco; if you don't have that settings set then it will try to use the "admin" account or throw exception if "admin" is not found.
is working on a reply...