Hi, if any one could helpme here,
I am trying to connect to one oof my databases in SQL 2000 server through ASP using similasr coode:
<% @.LANGUAGE = VBSCRIPT %>
<% Option Explicit %>
<html>
<head>
<title>testing our connection</title>
</head>
<body>
<%
Dim adOpenForwardOnly, adLockReadOnly, adCmdTable
adOpenForwardOnly = 0
adLockReadOnly = 1
adCmdTable = 2
Dim objConn, objRS
Set objConn = Server.CreateObject("ADODB.Connection")
Set objRS = Server.CreateObject("ADODB.Recordset")
' the following connection string is for connecting to a local SQL Server 2000 database
objConn.Open "Provider=SQLOLEDB.1;Persist Security Info=False;" & _
"User ID=sa;Password=tdmes102;Initial Catalog=CustomerProfile;" & _
"Data Source=dani;" & _
"Initial File Name=D:\DB\TDMECustomer_Data.MDF"
' the following connection string is for connecting to a remote SQL Server 2000 database
objRS.Open "CustomerProfile", objConn, adOpenForwardOnly, adLockReadOnly, adCmdTable
While Not objRS.EOF
Response.Write objRS("Principal") & "<BR>"
objRS.MoveNext
Wend
objRS.Close
objConn.Close
Set objRS = Nothing
Set objConn = Nothing
%>
</body>
</html>
I have tried several diferent ways and I keep getting this foollowing messages the same in the log file.
I tried relocating the database,reinstalling SQL , sp2.
HTTP error:
FCB::Open failed: Could not open device D:\DB\TDMECustomer_Data.MDF for virtual device number (VDN) 0.
SQL log file:
udopen: Operating system error 32(The process cannot access the file because it is being used by another process.) during the creation/opening of physical device D:\DB\TDMECustomer_Data.MDF.
2002-07-15 09:46:59.11 spid51 FCB::Open failed: Could not open device D:\DB\TDMECustomer_Data.MDF for virtual device number (VDN) 0.You don't supply an Initial File Name, maybe something you use for Access but not for SQL Server. At our site we don't even use the Data Source parameter, we add a Server parameter instead.
Here is a website that has connection examples
ConnectionString (http://www.connectionstrings.com/index.htm)
Example
Standard Security:
"Provider=sqloledb;Data Source=Aron1;Initial Catalog=pubs;User Id=sa;Password=asdasd;")
Trusted Connection:
"Provider=sqloledb;Data Source=Aron1;Initial Catalog=pubs;Integrated Security=SSPI;"
Provider=SQLOLEDB.1;Persist Security Info=False;" & _
"User ID=sa;Password=tdmes102;Initial Catalog=CustomerProfile;" & _
"Data Source=dani;
Showing posts with label virtual. Show all posts
Showing posts with label virtual. Show all posts
Wednesday, March 21, 2012
Friday, February 24, 2012
Failure to install - XOLEHLP.dll not found
Hello,
I'm trying to install CTP3 of katmai on Windows Server 2004 running inside Virtual PC.
It installs the setup files OK. Straight after that I get an error message box saying "The application has failed to start because XOLEHLP.DLL was not found. Re-installing the application may fix this problem"
Clicking OK gives me another message box with the message "TITLE: Microsoft SQL Server code name Katmai Setup
Failed to load SqlSpars.dll
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=10.0.1019.17&EvtSrc=setup.rll&EvtID=50005&EvtType=setup%5csqlsetupactions.cpp%40InvokeSqlSetupDllAction%40sqls%3a%3aInvokeSqlSetupDllAction%3a%3aperform%400x57
BUTTONS:
OK
"
The link doesn't give me anything useful.
Then I get the familiar 'Send Error Report' dialog. I DID send the error report.
I'm stumped. Anyone got any ideas?
Thanks
Jamie
Moving over to the new Katmai forums|||Jamie,I assume you tried to instell it on a Win 2003 box (not 2004) :-)
Anyway, that box (or rather VM in your case), how was it created in the first place? Have you done any funky stuff with MSDTC, as xolehlp.dll is a helper file for the DTC. Also, the Katmai installation, was it from the iso or a "normal" installation?
Niels
|||
Hey there Niels,
You're right. Win2k3. DOH!!!
Interesting your comments about DTC - I'll have a play around with that. I certainly haven't done any changes on the box - its as vanilla as it gets. Standard OS install. I'm using the katmai executable - i.e. not the .iso
This is all at home and I am now at work. I'll have another play around later this evening.
Thanks
Jamie
|||OK, try the ISO and see if it helps.Niels
Failure to install - XOLEHLP.dll not found
Hello,
I'm trying to install CTP3 of katmai on Windows Server 2004 running inside Virtual PC.
It installs the setup files OK. Straight after that I get an error message box saying "The application has failed to start because XOLEHLP.DLL was not found. Re-installing the application may fix this problem"
Clicking OK gives me another message box with the message "TITLE: Microsoft SQL Server code name Katmai Setup
Failed to load SqlSpars.dll
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=10.0.1019.17&EvtSrc=setup.rll&EvtID=50005&EvtType=setup%5csqlsetupactions.cpp%40InvokeSqlSetupDllAction%40sqls%3a%3aInvokeSqlSetupDllAction%3a%3aperform%400x57
BUTTONS:
OK
"
The link doesn't give me anything useful.
Then I get the familiar 'Send Error Report' dialog. I DID send the error report.
I'm stumped. Anyone got any ideas?
Thanks
Jamie
Moving over to the new Katmai forums|||Jamie,I assume you tried to instell it on a Win 2003 box (not 2004) :-)
Anyway, that box (or rather VM in your case), how was it created in the first place? Have you done any funky stuff with MSDTC, as xolehlp.dll is a helper file for the DTC. Also, the Katmai installation, was it from the iso or a "normal" installation?
Niels
|||
Hey there Niels,
You're right. Win2k3. DOH!!!
Interesting your comments about DTC - I'll have a play around with that. I certainly haven't done any changes on the box - its as vanilla as it gets. Standard OS install. I'm using the katmai executable - i.e. not the .iso
This is all at home and I am now at work. I'll have another play around later this evening.
Thanks
Jamie
|||OK, try the ISO and see if it helps.Niels
Sunday, February 19, 2012
Failure Audit on domain controller account
I have SQL 2005 installed in a virtual (ESX) environment with a separate DC. Every minute or so an event shows up in the Application Event Log that says:
Type: Failure Audit
User: dgtest\dc1$
Computer: sql1
Source: MSSQLSERVER
Category: (4)
Event ID: 18456
Description:
Login failed for user 'dgtest\dc1$'. [Client: <ip address>]
Data includes: SQL1 master
Any idea what is causing this and how to fix it?
Thanks,
Mindy
Hi Mindy,
I have the same problem. I am running VS2005, SQL2005 in Win XP SP2. I am trying to install Biztalk Server 2006 and I get this error in the event viewer. Due to this error I cannot configure the Groups in Biztalk Server. Do you have any fix?
Thanks,
Sundar
|||Mindy, does this user exist on your box sql1?|||Has any one found the solution for this problem
|||I found the solution. It happens when you are specifying BizTalk Server Administrators and BizTalk Server Operators group as the local group. In this case the configuration qizard will try to find these user groups on the SQL machine. If the SQL machine is different from the BizTalk machine, it wil generate error.
To resolve this, just make these 2 groups as domain user groups and change these groups settings within the configuration wizard of BizTalk to domain groups.
|||Sorry for the delayed response, I did not receive the thread notifications.
The user is actually the domain controller (dc1), not a regular user.
In my installation, there is no Biztalk, only MOSS.
The configuration of the environment (a test/dev environment) has changed significantly since I first posted, and the issue has gone away. Have other issues now, but they are not important ;-)
Mindy
Failure Audit on domain controller account
I have SQL 2005 installed in a virtual (ESX) environment with a separate DC. Every minute or so an event shows up in the Application Event Log that says:
Type: Failure Audit
User: dgtest\dc1$
Computer: sql1
Source: MSSQLSERVER
Category: (4)
Event ID: 18456
Description:
Login failed for user 'dgtest\dc1$'. [Client: <ip address>]
Data includes: SQL1 master
Any idea what is causing this and how to fix it?
Thanks,
Mindy
Hi Mindy,
I have the same problem. I am running VS2005, SQL2005 in Win XP SP2. I am trying to install Biztalk Server 2006 and I get this error in the event viewer. Due to this error I cannot configure the Groups in Biztalk Server. Do you have any fix?
Thanks,
Sundar
|||Mindy, does this user exist on your box sql1?|||Has any one found the solution for this problem
|||I found the solution. It happens when you are specifying BizTalk Server Administrators and BizTalk Server Operators group as the local group. In this case the configuration qizard will try to find these user groups on the SQL machine. If the SQL machine is different from the BizTalk machine, it wil generate error.
To resolve this, just make these 2 groups as domain user groups and change these groups settings within the configuration wizard of BizTalk to domain groups.
|||Sorry for the delayed response, I did not receive the thread notifications.
The user is actually the domain controller (dc1), not a regular user.
In my installation, there is no Biztalk, only MOSS.
The configuration of the environment (a test/dev environment) has changed significantly since I first posted, and the issue has gone away. Have other issues now, but they are not important ;-)
Mindy
Failure Audit on domain controller account
I have SQL 2005 installed in a virtual (ESX) environment with a separate DC. Every minute or so an event shows up in the Application Event Log that says:
Type: Failure Audit
User: dgtest\dc1$
Computer: sql1
Source: MSSQLSERVER
Category: (4)
Event ID: 18456
Description:
Login failed for user 'dgtest\dc1$'. [Client: <ip address>]
Data includes: SQL1 master
Any idea what is causing this and how to fix it?
Thanks,
Mindy
Hi Mindy,
I have the same problem. I am running VS2005, SQL2005 in Win XP SP2. I am trying to install Biztalk Server 2006 and I get this error in the event viewer. Due to this error I cannot configure the Groups in Biztalk Server. Do you have any fix?
Thanks,
Sundar
|||Mindy, does this user exist on your box sql1?|||Has any one found the solution for this problem
|||I found the solution. It happens when you are specifying BizTalk Server Administrators and BizTalk Server Operators group as the local group. In this case the configuration qizard will try to find these user groups on the SQL machine. If the SQL machine is different from the BizTalk machine, it wil generate error.
To resolve this, just make these 2 groups as domain user groups and change these groups settings within the configuration wizard of BizTalk to domain groups.
|||Sorry for the delayed response, I did not receive the thread notifications.
The user is actually the domain controller (dc1), not a regular user.
In my installation, there is no Biztalk, only MOSS.
The configuration of the environment (a test/dev environment) has changed significantly since I first posted, and the issue has gone away. Have other issues now, but they are not important ;-)
Mindy
Subscribe to:
Posts (Atom)