Running the c#.NET gives error: Ora-01017: invalid username/password;logon denied. The program was working well before I created a second database.
121698
Try to connect to both databases with sqlplus or some other utility to check if everything is OK with the listener discovering both of your database. \nIf everything is OK than maybe your program is trying to connect the wrong database.\nYou don't say if your second database is also oracle9i if this  is not true than you must check documentation for compatibility problems.
178278
for windows 98, find logo.sys, logow.sys,logon.sys just open with image editor.\nfor windows xp, find ntoskrnl.exe, open with resource hacker (you can find it using google). for xp's logon find logonui.com and open it using resource hacker.
364399
Hai Shaam,\n     I assume that you are successful in obtaining aconnection to the \nOracle Table, If not please code as necessary like\ntry{\nClass.forName("sun.jdbc.odbc.JdbcOdbcDriver")\nConnection con=DriverManager.getConnection("jdbc:odbc:<dsnname>", "<userid>","<password>");\nStatement stm = con.createStatement();\nResultSet rs = stm.executeQuery(<sql query>);\n// you will get each value by using\n//rs.getString(<index>) then store it in an array\n//display it to output,\n//if you need to display it in an output table in java\n//you can use JTable in the swing library.\n}\ncatch(Exception e){}\n\nfor further details you can contact me\n\nemail:ananthasivanvk@gmail.com\ncell:+919995403653
139480
check your connections, check your login info TWICE, and if that does not work, click "forgot my password"
226691
It's one of two things, just like the message says.  \n\nCheck first to see if the client can SEE the SQL server.  Assuming no firewalls in the way, you should be able to ping the SQL server.  If you can't ping it, you will have to either adjust the way the client finds the SQL server (you could use an IP address, add the reference into the workstation host file, use a fully qualified machine name that can be resolved, or maybe the probelm is just that you aren't pointed at the domains DNS servers (and are looking outside instead).  \n\nIf the connectivity is there, you're probably dealing with a permissions problem.  Assuming you're using mixed mode authentication, if the client is trying to log into the SQL server using the windows user name and password, you may not have set the permissions correctly to allow the user to access the database/server.  Test this by logging in with a user name where you KNOW it works on the problem station and see if the issue goes away.
234157
Be sure that the IP or Server name is correct;\nBe sure that the Login and password are correct;\nBe sure that the server has the MSSQL service running.
503086
The initial error, 80004005 is often related to how you are connecting to your database. I have added a link below which can tell you some of the problems (I know it refers to access, but much of the information there is still useful).\n\nIf you can connect to your database just fine using other queries, then how you are calling your procedure is the problem. So remove that code just to make sure that everything else is working fine, then focus on the procedure call itself.\n\nIf this is a stored procedure, are you using a command object? Are the parameters correct? Did you create the parameters correctly and are they the right type? Does your stored procedure on the machine run fine (not through asp, run it on the server)\n\nThe second error is more likely because of the first, your call to the procedure is causing it to hang and when you stop IIS it gives you basically a problem with dllhost.exe (that is what asp uses to run code).\n\nSo check out some of the links below and hopefully this can narrow your problem down further. \n\nIn short, test to make sure that ASP is connecting to your database correctly.\n\nGood luck!
368306
I use the following code to fetch the remote user name from Windows NT Authentication.  This works great if your web site can support NT Authentication.\n\nstrUserName = Request.ServerVariables("REMOTE_USER")\nstrUserName = Mid(strUserName, InStr(strUserName, "&#92;") + 1, Len(strUserName))\n\nThen whenever a user accesses the database, I can record the change and use the strUserName variable.  This will not work with anonymous access.
181377
You can use the System.Data.OleDb namespace, which is supported in the .NET Compact Framework 2.0:\n\nhttp://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemdataoledboledbconnectionclasstopic.asp\n\nTo use that, you'll need the OLE DB provider from Oracle:\n\nhttp://www.oracle.com/technology/software/tech/windows/ole_db/index.html\n\nPersonally, I'd use the .NET Framework 1.1, which includes the System.Data.OracleClient namespace:\n\nhttp://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemdataoracleclient.asp\n\nThe only problem there being, eventually that framework won't be supported by Microsoft any more.
123733
The most common reason that this connection attempt failed is that this DSN or ODBC data source attempted to make a connection using the TCP/IP sockets Net-Library, which is Dbmssocn.dll. Because the SQL Server is not listening for incoming connections for TCP/IP sockets clients, the connection fails. From ISQL/w, the second error message stated above would be returned. The OS Error is 10061, and the function call that failed was ConnectionOpen(connect()). By default, SQL Server will listen for incoming connections made by Named Pipes clients. Named Pipes is the default IPC mechanism for clients to connect to a SQL Server version 4.2, 6.0, and 6.5 server. The Named Pipes DLL is Dbnmpntw.dll, and it should be located in the Windows&#92;System or Winnt&#92;System32 directory. The TCP/IP sockets netlib DLL is Dbmssocn.dll, and also should be in the Windows&#92;System or Winnt&#92;System32 directory.The most common resolution to this problem is to configure the client computer to connect using Named Pipes.\nIf the Microsoft Data Access Components (MDAC) ODBC drivers have been installed on the computer, you can make this change in the second step of the Create New Data Source wizard.\nYou can download MDAC drivers from http://tinyurl.com/8xxm\nTo configure the client, start the Create New Data Source wizard, click the Client Configuration button, and perform the following steps, based on the version of the SQL Server ODBC driver you are using:\nFor SQL Server ODBC Driver version 3.50\n1.Click the Net Library tab and use the drop down list box to set the default network (Net Library) to Named Pipes.\n2.On the Advanced tab, remove any advanced entries that reference the server you are connecting to.\n3.Click Done.\nFor SQL Server ODBC Driver version 3.70\n1.In the Network Libraries section of the Edit Network Library Configuration dialog box, select Named Pipes.\n2.Click OK.\nIf you do not have the MDAC ODBC drivers installed, you can use the SQL Server Client Configuration Utility tool to set the default Net-Library to Named Pipes. You can install the client utilities from the SQL Server CD from the i386 directory.
289652
When accessing a resource on a Windows 2003 server from another host, your current credentials (username & password) are sent over the network.  If both computers are on a workgroup, then your userid (with the same password) needs to be created on both computers.\n\nNext, you need to make sure that you have assigned the appropriate permissions.  Since you received an "Access Denied" error, it appears that you did not set up the appropriate permissions.  You will not only need to configure the Share permissions, but also take a look at the Security (NTFS) permissions [assuming that the drive is formatted with NTFS].  \n\nMaybe the link below can clarify it for you.
408167
UPGRADE your client access edition to the one that is on the AS/400 system...I usually uninstall Client Access and start fresh. You can map a drive to &#92;&#92;YourAS400NameorIPAddress &#92;QIBM&#92; (no spaces...i needed spaced because this site truncates links)\n(You will need to authenticate using As400Name&#92;UserID then Password, \n\nthen drill down to &#92;ProdData&#92;CA400&#92; Express&#92;Install&#92;Image (again, no spaces...damn yahoo) and run the SETUP.EXE.  This will prompt you for a particular setup....use custom and you can specify ONLY the Client Access ODBC driver if you wish................I have found that using an older driver will cause problems.\n\nIf that don't work....\nI believe that the amount of libraries in your ODBC connection is too many.  Limit this library to your production library and see if this resolves your issue.\n\nGood luck
366575
I've had similar problems actually and it turned out to be a logon problem.\n\nCheck that your users actually use a network ID set in their accounts. I know this sounds stupid, but windows explorer has to have your login aswell as windows itself in order to connect to the printer properly. Sounds dumb I know.\n\nGet the troubled users to try connected to shared directories/files on the network. If they CAN connect, then you have a printer issue (try re-installing the driver, make sure spooler is running). If they cannot, they you need to setup the network login - IE A username/password for the server2003 machine (a limited user account - not your admin account).\n\nI am kinda clutching at straws here but it does indeed sound very similar to the problem I had recently (which had me hitting my PC and printer).\n\nGood luck\n\nJ
105056
u need not configure sql server.\n\nregister the driver\ncracre connection\ncreate statemet from it.\nstart writign ur jdbc stuff.\n\nyou can also try jdbc obdc bridge
113820
simple error one of your file names has an invalid character
292620
Try:\nI'm assuming MS Access 2000 and not MS SQL Server 2000?\n\nSELECT *\nFROM [ProdServers]\nORDER BY [Server Name/OS/DNS Alias]
170427
C#.NET needs a .NET Framework to run your application. May be you just need to download and install .NET Framework, \n\nThere are 2 version rigth now, 1.1 and 2.0, by default, try to install the 1.1 to WIN2K and see what happens, but i think this can solve your problem.