I'm having trouble getting off the ground with the Web application walkthrough "Walkthrough: Creating a Web Application Using Visual C# or Visual Basic" in VS.NET Pro 2002 [Academic] documentation. After a bit of fishing around, and consulting the MS Knowledge Base, I got the pubs database installed. I also got the connection to work well enough that the dataset would fill in the IDE.
The problem is that when I try to run the web form, either from the IDE debug menu, or by accessing the .aspx file on localhost using Firefox, I get the error: SELECT permission denied on object 'titles', database 'pubs', owner 'dbo'. showing in the browser. My understanding is that this page is running as ASPNET, and I did already carry out the recommended commands to enable access: C:>osql -E -S MY-MACHINE-NAMEVSDOTNET -Q "sp_grantlogin 'MY-MACHINE-NAMEASPNET'" C:>osql -E -S MY-MACHINE-NAMEVSDOTNET -d Pubs -Q "sp_grantdbaccess 'MY-MACHINE-NAMEASPNET'" both of which commands returned successfully. Any suggestions as to what else I should do to get the necessary permissions to actually display the data in my browser? Does the IIS user account need permission also?
Thanks for any insight into this vexing problem. I must say that along the way, I have had some fun exploring the osql comand-line tool. Using the -E switch, I have been able to run select and upgrade queries, but this is all pretty much fishing in the dark. I would like to get back to actually working with the walthroughs in the Visual Studio documentation.
I've been struggling to figure out how to set the "Log on as" login for a SQL Server agent that isn't a member of the Administrators group.
Is this even possible? No matter what policy settings I assign the the user, I get an access denied error when I try to start the SQL Server Agent service. If that user is part of the administrators group, there are no errors.
I have no problems with other services and "log on as" logins...
I am running MSDE with Sage Taxation Suite v10. However when I try to start MSDE with SQL Server Service Manager, it will not start, it tries to start, but then stops.
Why might this be happening and is there a possible fix for this problem.
Yes I have the dreaded "SQL Server does not exist or access denied." error when trying to connect to an MSDE database. I've tried many solutions found across the net. I installed the latest sp3a version of MSDE, granted the ASPNET worker process access to my database, opened port 1433 in the Windows XP firewall. I'm running Windows XP SP2.
The funny thing is that I can successfully connect using an ODBC DSN connection (OdbcConnection). No problems at all. This works.
<code> Dim strDSNString As String = "DSN=mike" Dim objConn As New OdbcConnection(strDSNString) Dim objCmd As New OdbcCommand("select * from table1", objConn) Dim objReader As OdbcDataReader
Hi all, I'm getting this error message when I try to connect my MSDE database from other machine using enterprise manager application. Both of the machines are WinXP SP2. I found some solution such as using 'SQLServer Network Utility' but didn't work out for me. I even can not connect my database on my computer using TCP/IP. When I connect with name, it worked fine. I already enable both TCP/IP and Named pipe protocol on the MSDE machine. If someone has solution on that please let me know.
My SQL2K was running fine. Yesterday, I decided to install SP3a. During the installation, it failed when apply sp3_serv_repl.sql. And I can't start SQL server anymore. The error is :
FRunCM : Process <> generated Fatal Exception C0000005 Exception Access Violation - SQLServer is terminating this process.
No matter what I did, I couldn't start the service again. SO I decided to uninstall SQL2K and install again. Installation is ok, no problem. But, again the SQLServer service cannot start up. The same error appeared. Besides, there is also the error about :
Supersocket Error 1355.
I have tried all the suggestions that I can find in the net but nothing seems to work.
Please advise what should I do. Thank you very much.
The log for our SQL 2000 database shows constant "starting up database dbname" entires. Is there a option that causes the databases to constantly be starting or is this a new feature of SQL 2000.
Am very new to MS SQL adminstration Can anybody help me out how to work on Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Release A just for the practice.
The activity which am going to workout on MSDE is below.
How to install SQL(on XP) How the layout will be(like if i insall MSDE what are all Application will be and how they depends on each other) How to create/delete tables if so, how can we do it either by GUI or CUI
The log for our SQL 2000 database shows constant "starting up database dbname" entires. Is there a option that causes the databases to constantly be starting or is this a new feature of SQL 2000.
Please feel free to redirect me if this has been previously addressed. I've read through the FAQ post and searched the forums, and as yet haven't found anything relevant on Google so I'm hoping you folks can help.
I am using SQL Server 2005 Express Edition on a fully patched Windows 2000 Server, and for some reason the database just will not start up when the machine starts or reboots. The service starts fine if I go start it by hand though. This is obnoxious because it prevents me from running fully automated updates to the box since that reboots it at least once a week on "patch Tuesday".
Here are what my related services and their startup types look like:
SQL Server (MSSQLSERVER) Automatic SQL Server Active Directory Helper Disabled SQL Server Browser Disabled SQL Server VSS Writer Manual
This is a production machine so I'd prefer not to run any services I don't have to. All this database needs to do is sit there and get hit by a local Cold Fusion instance that talks to it by TCP/IP. Any administration on it I tend to do locally with Management Studio Express by remotely logging into the server on it's internal IP.
The really weird thing is, I have these services configured exactly the same on development environments I've created in Windows XP and Windows 2003 Server Standard Edition. This seems to be specific to Windows 2000 Server, and I just can't figure it out...
Will any application developed against SQL Server 2000 Developer Edition work on an identical platform with only MSDE 2000 installed? I understand there's a concurrency limit with MSDE 2000 of around 25 (and there's no GUI) but apart from that, are there any aspects of SQL Server 2000 functionality (from the .NET applicaiton code's point of view) that are "disabled" in MSDE 2000?
Trying to transfer databases from MSDE to SQL. When I use SQLEnterprise Manager - DTS - import or export, it works for the firstdatabase, but then fails for the others. I select the to and fromdatabases using DTS - Import - 'MS OLE DB Provider for SQL Server',then select 'Copy objects and data between SQL Servers'. It failswith the generic error message: 'Copy objects failed', nothingfurther. I tried to just copy data, and it doesn't work totally. Ontwo databases, it said that it copied everything, but when I go inunder Enterprise manager, some of the tables are incomplete, i.e. nodata, table shows up in the list, but if you try to look at it, itsays that it is missing or empty. Also, one table was not evencopied. In the other two cases, I get errors, does not copy alltables. I get errors, like insert fails, but the column it referencesfor the table does not even exist in that table. Any suggestionswould be appreciated.
I am creating an install program and I'm wondering if there is a difference between SQL Server 2000 and MSDE 2000? Do they have different entries in the Registry?
From the documentation that I've read it seems as if they are one and the same.
However, if someone knows how to differentiate between them in the Registry it would be greatly appreciated.
When our rep distribution services time-out (several times a day) some dba's just restart the service while others restart the rep job which starts the service. Are there any differences between these two methods? Does restarting the service inherit any changes made to the job's attributes?
Is there anyone could help me, I'm moving our database from old machine to a new one and Iused DTS to move it the new box. Somehow it was moved but I'm still having probelm with my front-end application when I'm trying to open it the error is something like this.
"3704-Operation is not allowed when the object is closed. an error occurred in Cal_General.CheckDBVSN.Global Error: -2147217911 -SELECT permission denied on object 'Global_config', Database 'dbase1', owner "App1. underlying Errors: Error #-217217911 SELECT permission denied on object 'Global_config' database 'calsql1', owner "App1'. (Source MIcrosoft OLE Provider for SQL Server) (SQL State: 42000) (NativeError:229) No Help file available."
I am about to setup an application server. This app will generate reports and instead of just having a HTML page up, I am considering running dotnetnuke type portal to offer the userbase a better interface for the reports, info, announcement, etc.
Server isn't too bad (2x1.7Ghz Xeon I think, 2GIG RAM) type of setup (may be little more or less). App doesn't require as much resources, but we are planning for the future )
While I have some resource to play with, I also need to make sure I don't load much that may impact the application performance. In my experience, SQL Server 2000 will take a lot of resources even when not used as much. So I am considering MSDE.
I am curious however, WHAT ARE THE MAIN DIFFERENCES BETWEEN SQL 2000 Server Vs MSDE 2000 ?
Beside no Client tool and mostly command line specific command, what else there to convince that I should go for server vs desktop engine?
Now our company has Enterprise license for SQL, so I am not worried about the cost (well a little maybe), but mostly wondering about performance.
If you think of any reason why I go to SQL Server 2000 over MSDE, please let me. Otherwise, I think MSDE in this case is the appropriate RDBMS to go for.
I cannot connect to the remote SQL Server 2000 running on this machine that has just been upgraded to the W2003 server. Everything worked perfectly before the upgrade on W2000. All the logins, firewall setting stayed the same. Can ping the machine. But when trying to register/link, or connect thru ODBC, I got the error SQL server does not exist or access denied. We don't have SQL server SP3 installed.
We have SQL 2000 (SP2) , Our SQL server agent showing green light as started from EM , It is succussfully restarting from NT Services too . But When I open the properties of the jobs from EM its gives error message SQL DMO error " SQl Agent is starting , try later " . And in EM Next run Date & Time not available .
MDDB database is accessable & in Log file its recovered fully
