Rank: Member
Joined: 9/24/2003(UTC) Posts: 402
|
Full clean install, reports
Invalid Object Name 'dbo.bvc_WebAppSetting' :smhair:
|
|
|
|
Rank: Member
Joined: 9/24/2003(UTC) Posts: 402
|
It coughs up a lung on both Pro SP2 and 2003 patched, developer and express SQL respectively.
Creates the DB and starts populating the tables but craps out at system tables. Looks like something was missed?
|
|
|
|
Rank: Member
Joined: 5/22/2004(UTC) Posts: 64
|
Same issue here with a local fresh install.
Dan
|
|
|
|
Rank: Member
Joined: 9/24/2003(UTC) Posts: 402
|
Here's the weird thing, downloaded on another remote machine about 648pm installed fine. Cleaned everything out and downloaded again on the local machine, installed fine after I downloaded again about 650pm. I'm going to guess if you try to redownload right now and install it will be fine, the guys must be working on it as we type.
|
|
|
|
Rank: Member
Joined: 5/22/2004(UTC) Posts: 64
|
okie....thx scott. will give it a try
Dan
|
|
|
|
Rank: Member
Joined: 9/24/2003(UTC) Posts: 402
|
Did it work for you this time?
|
|
|
|
Rank: Member
Joined: 5/22/2004(UTC) Posts: 64
|
Well, it completed the installation, but now it tells me that I am exceptionally unhandled :) like I didn't know. Here is the actual message when login:
<H1>Server Error in '/gocyan' Application. <HR width="100%" color=silver SIZE=1> </H1> <H2>Cannot find table 0. </H2> [color=#ffffcc>
[tr ][td ]<CODE>The]1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration> <system.web> <compilation debug="true"/> </system.web> </configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.[/code] [/td][/tr]</TABLE> [1]
<B>Version Information:[/1] Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210 <!-- [IndexOutOfRangeException]: Cannot find table 0. at System.Data.DataTableCollection.get_Item(Int32 index) at BVSoftware.Bvc5.Core.Content.SiteTerms.get_AllTerms() at BVSoftware.Bvc5.Core.Content.SiteTerms.LoadSettings() at BVSoftware.Bvc5.Core.Content.SiteTerms.GetTerm(String termName) at BVSoftware.Bvc5.Core.Membership.UserAccount.ValidateUser(String userName, String password) at BVAdmin_Login.btnLogin_Click(Object sender, ImageClickEventArgs e) at System.Web.UI.WebControls.ImageButton.OnClick(ImageClickEventArgs e) at System.Web.UI.WebControls.ImageButton.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.ImageButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) [HttpUnhandledException]: Exception of type 'System.Web.HttpUnhandledException' was thrown. at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP.bvadmin_login_aspx.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) -->
|
|
|
|
Rank: Member
Joined: 9/24/2003(UTC) Posts: 402
|
Weird. I must have gotten lucky and either got a corrupted download or something similar. Working fine here.
Can you log in at all?
|
|
|
|
Rank: Member
Joined: 5/22/2004(UTC) Posts: 64
|
no luck....i'll try it tomorrow with fresh eyes.
Dan
|
|
|
|
Rank: Member
Joined: 9/24/2003(UTC) Posts: 402
|
I think you'll need to uninstall all bv software and use the site removal tool. Select "remove from list" after it fails in removing the site entirely the first time. Go into IIS and manually remove the application/virtual directory. Now to go the INETPUB directory on C:\ and remove the site if there are any folders leftover. Follow the same course of action in manually removing the DB using SQL Management Studio.
Now reinstall the latest BV software, and create your site. That will probably fix your problem.
|
|
|
|
Rank: Member
Joined: 8/17/2006(UTC) Posts: 681
|
Dan, Check your web.config make sure that your connection string was not overwritten for some reason. Corneliu. |
|
|
|
|
Rank: Member
Joined: 3/1/2006(UTC) Posts: 1,142
|
We didn't ship a web.config in the patches, so no one should be having issues with it being overwritten. The "cannot find table 0" error means that for some reason the web server is unable to connect to the database. Did you install the site with using Integrated authentication (instead of typing in a username and password for SQL) because sometimes this will allow you to install, but then when the site fires up it is running under a different username and no longer has authorization to hit the database. |
Justin Etheredge Senior Software Engineer BVSoftware |
|
|
|
Rank: Member
Joined: 5/22/2004(UTC) Posts: 64
|
Yes, I set it up with Integrated Security and tried several different stores/database names but they all resolve to the same error @ login. I am going to uninstall bvc5 & sql and reinstall because it just smells like something isn't right. I'll repost. Thanks.
Dan
|
|
|
|
Rank: Member
Joined: 3/1/2006(UTC) Posts: 1,142
|
You might want to try using built in sql server authentication. The problem with Integrated Security is that when you install it uses the rights of whatever user you are currently logged in as. When you are running the website is uses (by default) either the aspdotnet system account under IIS 5.0 or in IIS 6.0 it uses the Network System account. These accounts most likely have no rights on your database, so they do not work. |
Justin Etheredge Senior Software Engineer BVSoftware |
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.