ASP.NET 会员资格;有东西正在调用 dbo.aspnet_CheckSchemaVersion
我正在使用 ASP.NET 会员资格。我在一个共享托管站点上运行它,在那里我有一个数据库模式,我可以运行它。 在服务器上生成数据库的脚本中,我将架构从“dbo”更改为其他架构;关于表、视图和 SP。 一切都很好,除了会员之外一切都很好;我可以联系数据库并提取记录。
但是,成员身份登录失败并显示消息:“找不到存储过程‘dbo.aspnet_CheckSchemaVersion’。” 这当然在我的数据库中称为“DBxx.aspnet_CheckSchemaVersion”。 这是从哪里调用的以及如何让它调用正确的模式?
I'm using ASP.NET Membership. I'm running it on a shared hosting site where I have an db schema I run things off.
In the scripts to generate the DB on the server I changed the schema from 'dbo' to this other schema; on the tables, views and SP's.
Thing work fine, with everything except the Membership; I'm able to contact the DB and pull up records.
However, the Membership-login fails with the message: "Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'."
This of course is called 'DBxx.aspnet_CheckSchemaVersion' in my database.
Where is this being called from and how can I make it call the correct schema?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
它在 System.Web.Util.SecUtility 中被调用并且是硬编码的。除非你想重新发明轮子您需要重新配置您的数据库。我已经做到了。这不是脑部手术,而是大量的工作,而且隔离数据库的兴趣不符合我的书中的条件。
It is being called in System.Web.Util.SecUtility and it is hardcoded. Unless you want to re-invent the wheel you need to re-provision your database. I have done it. Is not brain surgery but is a lot of work and the interest of segregating a database does not qualify in my book.