OSQL SQL 2000 Named Instances Disappear When SQL Express Computer Added To Network
Aug 16, 2007
We have 10+ MSDE 2000 installations on the same network. Each install has a named instance and the
machines connect to eachother via VB application. We have a couple SQL 2000 Standard boxes and a SQL 2005
box all running on the same network with no issues. The problem we have recently run into is with a SQL
Express box. When the box is on the network OSQL stops finding the MSDE 2000 named instances on the
network and only the SQL Express named instance appears in the list. The second the SQL Express box is removed
from the network the named instances are visible. I monitored the UDP traffic and suspect there is an issue with the response from SQL Express to OSQL. Can't find any issues for this problem only report I found is if MSDE and Express are on the same machine.
SQL Express Response
.Q.ServerName;DDK7P4D1;InstanceName;SQLEXPRESS;IsClustered;No;Version;9.00.1399.06;;
MSDE Response
...ServerName;RED;InstanceName;SECOND;IsClustered;No;Version;8.00.194;tcp;4307;;Ser
verName;RED;InstanceName;THIRD;IsClustered;No;Version;8.00.194;tcp;0;;Server
Name;RED;InstanceName;MSSQLSERVER;IsClustered;No;Version;8.00.194;tcp;4303;;
Any ideas?
Thanks, Kevin.
View 2 Replies
ADVERTISEMENT
Aug 16, 2007
We have 10+ MSDE 2000 installations on the same network. Each install has a named instance and the
machines connect to eachother via VB application. We have a couple SQL 2000 Standard boxes and a SQL 2005
box all running on the same network with no issues. The problem we have recently run into is with a SQL
Express box. When the box is on the network OSQL stops finding the MSDE 2000 named instances on the
network and only the SQL Express named instance appears in the list. The second the SQL Express box is removed
from the network the named instances are visible. I monitored the UDP traffic and suspect there is an issue with the response from SQL Express to OSQL. Can't find any issues for this problem only report I found is if MSDE and Express are on the same machine.
SQL Express Response
.Q.ServerName;DDK7P4D1;InstanceName;SQLEXPRESS;IsClustered;No;Version;9.00.1399.06;;
MSDE Response
...ServerName;RED;InstanceName;SECOND;IsClustered;No;Version;8.00.194;tcp;4307;;Ser
verName;RED;InstanceName;THIRD;IsClustered;No;Version;8.00.194;tcp;0;;Server
Name;RED;InstanceName;MSSQLSERVER;IsClustered;No;Version;8.00.194;tcp;4303;;
Any ideas?
Thanks, Kevin.
View 4 Replies
View Related
Jul 18, 2001
I had a server with SQL Server 7.0
I installed a named instance of SQL Server 2000 and then i passed all my DB
of the 7.0 instance to the 2000 instance.
Then i removed the 7.0 instance, that was the default instance.
So at the moment there is only the 2000 version, but it isn't the default
instance
Can the 2000 instance become the default instance? (So that clients can
connect to it simply through computer name, and not creating an alias)
thanks
Fede
View 1 Replies
View Related
Aug 29, 2006
I have the following problem;
I fully understand that to connect to a named instance of SQL Server you need to use the ServerNameSQLInstanceName. The problem I have is that I have a SQL Server in a different zone. I can connect to the Default instance by IP Address or the ServerName.zone.domain.org. (e.g. MySQLServer.zone1.mydomain.org).
However, the same thing does not work for the Named Instance. It seems to be named instance or nothing.
How can I connect to this named instance across network zones?:S
View 2 Replies
View Related
Jan 9, 2007
We are having all kinds of issues with named instances for SQL 2000.
I am trying to connect to a SQL Server 2000 named instance on a different subnet and get an error. I cannot connect with ODBC or our web app.
I am using the port number for the alias that I created in the SQL Client Utility. We can connect to default instances without a problem, but not the named instances.
The SQL Server is 2000 build 2040 (Service pack 4 with a hot fix.) The server is listening on port 1223. In the ODBC connection I click on the Network Config and create an alias with the named instance such as SQLVSNSQLNI and specify port 1223. I have also tried adding the port to the connection string in the ASP include file (SQLVSNSQLNI,1223). If I do the same thing with a default instance on the network, both the app and ODBC work fine. It is only when I use a named instance.
Very frustrated. Thanks for any help you can provide
View 2 Replies
View Related
Feb 12, 2002
We're moving several Version 7 databases to a SQL Server
2000 box.
How can I grant SQL Server 2000 security for three
"Named Instances"?
Thanks
Benny
View 1 Replies
View Related
May 5, 2006
Hi All,
I've developed an application that connects to a SQL Server 2005 Express database. I created a DSN to connect to the database through ODBC. Currently, I am testing locally and everything works fine.
I would now like to install my application on another workstation and connect remotely to the database located on my development machine.
The client workstation does not have SQL Server 2005 Express installed on it because I would just like my application to connect remotely by creating the DSN and using ODBC. What I'm missing here are the database drivers. The "SQL Natice Client" is not available on this client workstation. How can I deploy the necessary drivers with my installation file so that I may create the required DSN name using the SQL Native Client driver?
Thanks!
View 6 Replies
View Related
Dec 4, 2007
Hi,
We have (after several weeks of testing in all kind of environments) send out a new version of our application to several of our customers. Within days problems where drippin in; After looking for the problem on various customer situations we found a problem which I think is rather disturbing and very odd. I'll describe the situation, on which we finally managed to recreate the problem, here.
In my problem I use the following configuration:
Windows 2003 (standard edition) AD network with 2 domain controllers, multiple Windows XP workstations, some without SQL instances, some with SQL 2000 instances, some with SQL 2005 instances and even one with SQL 7 running.
All run a 32 bit OS.
Tools to reproduce:
ListSQLSvr application (found on SQLDev.net) to enumerate the instances.
Problem description:
--------------------------------------------------
I am running the machine called DEV001, which has SQL 2000 (instancename DRUMIS) and SQL 7.0 (has no instancename so this is the root instance) installed.
In any 'normal' situation all the runnings SQL instances are visible on the network like this:
Code Block
C:>listsqlsvr -X
(local);Clustered:No;Version:7.00.623
ADM002DRUMIS;Clustered:No;Version:8.00.194
DEV001DRUMIS
DEV001DRUMIS;Clustered:No;Version:8.00.194
DEV002DRUMIS;Clustered:No;Version:8.00.194
DEV002EXPRESS;Clustered:No;Version:9.00.3042.00
DEV002EXPRESS
INSADBACKOFFICEDRUMIS;Clustered:No;Version:8.00.194
INSADBACKOFFICEEXACT;Clustered:No;Version:9.00.3042.00
INSADOFFICEWSUS;Clustered:No;Version:8.00.194
SUP001DRUMIS;Clustered:No;Version:8.00.194
When I turn the SQL 2005 Browser service off on the machine called DEV002 the list looks like:
Code Block
C:>listsqlsvr -X
(local);Clustered:No;Version:7.00.623
ADM002DRUMIS;Clustered:No;Version:8.00.194
DEV001DRUMIS;Clustered:No;Version:8.00.194
DEV001DRUMIS
DEV002
DEV002EXPRESS
DEV004DRUMIS;Clustered:No;Version:9.00.3042.00
INSADBACKOFFICEDRUMIS;Clustered:No;Version:8.00.194
INSADBACKOFFICEEXACT;Clustered:No;Version:9.00.3042.00
INSADOFFICEWSUS;Clustered:No;Version:8.00.194
SUP001DRUMIS;Clustered:No;Version:8.00.194
Notice that the browser service might be off on DEV002, you can still see the EXPRESS instance and a new root instance has appeared (though it doesn't exist!)??
After restarting the Browser service all is OK again.
When I turn on Hide Server in the SQL 2000 TCP/IP properties (or turn it on in the registry [HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerDRUMISMSSQLServerSuperSocketNetLibTcp] "TcpHideFlag"=dword:00000001) on the DEV002 computer something real scary is happening..
The list looks as follows:
Code Block
C:listsqlsvr -X
(local)
ADM002
DEV001
DEV002
DEV004
INSADBACKOFFICE
INSADOFFICE
SUP001
When someone has entered a database (for example the backoffice database on INSADBACKOFFICEEXACT) the list looks as follows (for a short moment; 5 secs or so):
Code Block
C:listsqlsvr -X
(local)
ADM002
DEV001
DEV002
DEV004
INSADBACKOFFICEDEVELOP;Clustered:No;Version:8.00.194
INSADBACKOFFICEDRUMIS;Clustered:No;Version:8.00.194
INSADBACKOFFICEEXACT;Clustered:No;Version:9.00.3042.00
INSADOFFICE
SUP001
Notice now that ALL instances are gone and no extended information is available. In the Query Analyser and in the SQL Management Studio when browsing you'll see this as well!
When someone is accessing a database instance it appears for a few seconds again.
Since our installation and applications rely on selecting a existing instance it will fail in the above situations (or at least not showing all available instances).
In my opinion this is a bug somewhere!
Note that even when the SQL Services are stopped on DEV002 (leaving the Browser service running) it still seems to block out ALL instance on the ENTIRE network!
I don't mind that one INSTANCE or even the entire MACHINE is hidden from the network, but ALL instances on ALL machines??
And the SQL Browser issue also worries me a bit since it does not stop the possibily to browse the SQL instances; it removes the SQL2000 instances but adds a root instance which doesn't even exist! Also the extended info is stripped.
Can anyone help me solve this/advise?
Also mind that in any situation there might run a lot of computers with a lot of SQL instances and I cannot tell our customers to find which machine has the SQL TCP/IP properties set to Hide...
It even seems that in some situations SBS 2003 does the hiding automatically on Install? And if so, when and why?
Regards,
Albert van Peppen
Senior System Engineer
Insad Grafisch b.v.
View 31 Replies
View Related
Mar 27, 2008
Greetings,
I have a VB 2003 .NET application that I wrote for a customer that connects to a named instance of SQL 2000. Until recently it has been working fine. Lately the program either pops a timeout failure within a few seconds or a general network error. I've increased the connection timeout settings to 90 seconds but the error still pops within a few seconds. I'm thinking something has changed in the environment that prevents a clean connection to the named instance of SQL server.
How should this issue be troubleshoot to determine the problem and what areas need to be looked at?
Thanks
View 3 Replies
View Related
Mar 20, 2008
I have not seen this ever on my computer until today...
I start CuteFTP or NetObjects Fusion 8 and I get an installer window popping up saying:
"Please wait while Microsoft configures Microsoft SQL desktop engine"
ZoneAlarm warns me that OSQL.exe is trying to connect to my network.
I let it.
Then ZA warns me that OSQL is trying to connect to the internet.
At this point, if I let it, or deny it, the thing installer (which looks to be half way done) reloads itself and starts over with ZA warning that it's trying to connect locally, then to the internet. Over and over this happens.
It wont let either of my program start until it goes through about 5 or 6 cycles of whatever it's trying to do.
Then it just disappears and my program will load.
If I close either CuteFTP of NetObjects and start them back up, the whole OSQL.exe thing starts again.
I have rebooted and it still does this.
The odd thing is some of the IP addresses it's trying to connect to.
72.14.207.104 - Google
96.6.129.187 - Akamai
207.46.248.249 - Microsoft (ok, that's understandable)
I didn't write the IP address, but it tried to get to Hotwired.com too..
How do I fix this? Why is it doing this?
I'm running XP Pro. P-4 3Ghz 1.5Gb RAM
Thanks for any help!
-Rich
View 2 Replies
View Related
Jan 18, 2006
Hello,
Sorry for my question, I know, that there were several topics about sql 2000 vs SQL 2005, I read all them but unfortunately I haven't got the correct answer. I must install my intranet application that uses asp.net 2.0 and SQL 2005 Express to a Windows 2003 server with SQL 2000. It is possible to install SQL 2005 Express beside the 2000 server? It is very important, because I have no possibility to test and that Win2003 server there are a few programs that use SQL 2000. What will happen with the 2000 databases and their programs if I install the 2005 Express to the server? They will work fine with 2000 and my application will work with 2005?
Or instead it should I configure my application to use 2000 capable connentionstrings?
View 3 Replies
View Related
Oct 23, 2007
Ok, I am new to Reporting Services but am facing an issue today.
A developer decided to consolidate two ReportServer databases onto a single 2005 database instance with different names. Fine. But he is trying to get one Reporting Services instance to somehow process both sets of databases. (ie. ReportServer and ReportServer_dev.) My opinion is that he is irrational. I would think that he would need to have two separate instances of Reporting Services (running on one server) with each configured to access one of the two ReportServer databases. Is that correct or am I all wet?
Thanks,
Michael
View 1 Replies
View Related
Feb 14, 2002
Is it possible to rename a named instance?
We have a vendor product that can only handle up to 18 characters for the server name and the instance name (we did not know this when we created the named instance) and of course our combined name is 19 characters, so it trys to pass the 18 charater name and then fails with the following error:
[LOG] Unable to read local eventlog (reason: The data area passed to a system call is too small)
So, can i rename the instance, or do i have to create a new named instance?
Thanks
View 2 Replies
View Related
Jan 18, 2008
This is a slight re-stating from an older thread, which I think warrants some new discussion. The answer has always been that system administrators should have full access to everything on a system, including databases.
Although that is a logical position for internal IT departments it doesn't quite fit the model of systems with outsourced or external system support.
"If you don't trust your DBA, then you need a new DBA. They are in a position of authority for a reason and restricting that authority makes it impossible for them to do the job they are hired to do."
What about scenarios where you have local machine administrators that should NOT be given access to private data in a secured database, even though they need to be able to access and maintain everything else? And unfortunately some regulations are written about access to stored data whether encrypted or not...
In the modern world of Sarbanes-Oxley and PCI-DSS/CISP it is no longer so cut and dried. Especially where companies have software/hardware support contracts with third parties that require administrative access to other aspects of the systems.
So accepting that you might need someone to have administrative level access to the box but they should not be able to view the contents of a database installed on that box, what would you do?
Is there a way to create an adminstrative group that does not allow access to a specific named instance of SQL?
Is there a way to revoke access for one member of the administrators group only?
Thanks,
Ted
View 6 Replies
View Related
Apr 11, 2006
Informatica jobs were erroring out with a sql server driver error
while connecting to a named instance in SQL Server.
The issue was because in sql server named instance, the port was allocated dynamically and Informatica 7.1.4 (provides 4.21 version of Datadirect odbc drivers for SQL server) which dont have support for named instances with dynamic port allocation. This feature is only present from version 5 of the Datadirect odbc drivers for SQL server
To fix this issue, I need to allocate the port for the named instance instead of getting it dynamically.
My questions
1) Whats the impact of doing a port allocation for the named instance on the existing environment.
2) Is there any issues which we can foresee in the applications
3) Things which i need to be aware of
Thanks in advance
sreenath
View 3 Replies
View Related
Dec 4, 2007
Hi everyone,
Is there a way to route a specific IP address to a named instance on a SQL 2k system???
thanks
tony
View 2 Replies
View Related
Dec 11, 2007
We are using a system that has uses four instances. On each client to the server we used the ODBC settings to connect to the different instances. We have since reinstalled the server, and now we are unable to find or 'see' any of the databases, except for locally.
E.g. The first database we install is named Foo, with database Bar. It is set up on port 1433.
The second named instance is Foo2, with database Bar2. It is set up on a dynamic port.
We now try to connect to the database with ODBC. We connect to SERVERFOO, and then select the BAR db. It works fine.
We then try to connect to the database SERVERFoo2, it lets us in, and then all we can select is the BAR db. I don't know what is causing this. We never before had to edit the settings in the client config for the odbc settings (e.g. to set manually to TCP port 1433) and I have checked the sql config manager to ensure that tcpip settings are allowed and will "ListenAll".
What more do we need to do? I think the browser should be installed, but my collegue disagrees.
Any ideas as to why we can only see the database referenced to 1433 port, and why no other port works, when we never had to do that before?
Thanks a bunch in advance,
Regards
Carl
View 2 Replies
View Related
Apr 4, 2007
Using VS05 SP1 Pro SQL Express€¦
In converting a program from VS03/MSDE, long ago I installed SQL 2005 Express with Advanced Services and everything was fine. Windows Update has recently been failing to install SQL 2005 Express with Advanced Services SP2. After no answers from the forums, and logs that were of no help, I decided to uninstall SQL 2005 Express with Advanced Services and reinstall SQL 2005 Express (basic version). As a test run, I did it on a desk top, no problems what so ever.
However, on my laptop, it has been a nightmare.
Question 1) in control panel, add/remove programs, all of SQL 2005 Express with Advanced Services uninstalled fine except one item - I am unable to uninstall MS SQL 2005 Backward Compatibility, getting the error message
A network error occurred while attempting to read from the file
c:windowsinstallersqlserver2005_bc.msi
That file is not on the hard disk.
After installing SQL 2005 Express (the basic version), this problem persists and I cannot uninstall MS SQL 2005 Backward Compatibility for the same reason.
How can I get rid of MS SQL 2005 Backward Compatibility?
Question 2) Windows update still is trying to download and install SQL 2005 Express with Advanced Services SP2, even though I have uninstalled it. How to manually get rid of whatever settings are triggering this?
Thanks!
Bob
View 15 Replies
View Related
Feb 25, 2007
I have a server computer named 'X' and I would like to install 2 instances of SQL Server 2005
1. SQLTEST
2. SQLDEV
During installation. if I select Default instance then it will name my sql server instance X . I don't want that. I want to have essentially 2 named instances to make it clear to the users that they are using a test and dev sql server. Whats the best way to do this? I am open to suggestions if there is a different way to do this.
Is it required to have a default instance? Can I have 2 named instances XSQLDEV and XSQLTEST?
Also, on the SQLTEST I will be installing reporting services. By not having a default instance will it cause issues for the SSRS installation.
Please help!
Thanks.
View 1 Replies
View Related
Aug 12, 2007
I'm struggling a little with this. I hope someone can help.
Ho do i install SQL Server 2005 Express so i can connect to it with "localhost", not "<MACHINE_NAME>/SQLEXPRESS". I cant seem to find any obvious setting in setup.
Could anyone shed any light on this?
Regards,
Anthony
View 3 Replies
View Related
Mar 3, 2007
Hi
Please if any one can answer.I am developing .net vb app sqlexpress database.
In single user work ok.In multiuser from other computer on network I cannot get data.Any form without data workok fine . The error I am getting is as follows.
Application attempted to perform operation not allowed by the security policy.
request for permission of type
'System.data.sqlclientpermission,system.data,
version=2.0.0.0.,culture=Normal, publickeytoken=b77a5c561934e089'
Zaabdullah
View 1 Replies
View Related
Jul 8, 2015
I am using robocopy to copy my sql server backups to a fileshare. This is working great except for named instances.I use Ola Hallegren's backups which create a folder called xxxx$xxxx. Robocopy can't seem to handle the $.
View 9 Replies
View Related
Apr 30, 2008
We've read about a single installation of SSIS applies to all SQL instances on a server. We've also read how by default SQL Server stores SSIS packages in the MSDB database on the default instance and if you want to have packages stored on a named instance you must modify msdtssrvr.ini.xml. Here are our questions.
1 - If msdtssrvr is modified to reference a named instance, such as <ServerName>SQLTESTINST1<ServerName>, when I connect to Integration Services through Management Studio do I still specify the default instance name in the login window? That's the only way we have been able to connect and despite specifying the default instance name, the packages displayed are those of the named instance.
2 - If I am correct that you must always specify the default instance name when connecting to Integration Services, then in order to eliminate confusion regarding what SQL instance's SSIS packages I am viewing under the folder structure I can create SQL Server folders by modifying msdtssrvr.ini.xml. For example:
<?xml version="1.0" encoding="utf-8"?>
<DtsServiceConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown>
<TopLevelFolders>
<Folder xsi:type="SqlServerFolder">
<Name>MSDB</Name>
<ServerName>.</ServerName>
</Folder>
<Folder xsi:type="SqlServerFolder">
<Name>MSDB-INST1</Name>
<ServerName>SQLTESTINST1</ServerName>
</Folder>
<Folder xsi:type="SqlServerFolder">
<Name>MSDB-INST2</Name>
<ServerName>SQLTESTINST2</ServerName>
</Folder>
<Folder xsi:type="FileSystemFolder">
<Name>File System</Name>
<StorePath>..Packages</StorePath>
</Folder>
</TopLevelFolders>
</DtsServiceConfiguration>
I then restart the SSIS service and can now see the following folder structure.
Running Packages
Stored Packages
+ File System
+ MSDB
+ MSDB-INST1
+ MSDB-INST2
If I expand MSDB-INST1 I will only see packages saved on the instance named INST1. The same is true for INST2. If I expand MSDB I will only see packages saved on the default instance.
Does this sound like I am doing things correctly?
Thanks, Dave
View 3 Replies
View Related
Mar 20, 2008
what is default website for named instances in Reporting services?
View 1 Replies
View Related
Jun 4, 2007
Hello,
I am after a bit of advice about running the Upgrade Advisor tool on a server that has more than 1 SQL Server instance. My particular focus is DTS on each server.
I tried running the tool, setting up an XML file per SQL Server (including named instances). An example of the XML is I used is included below):
<Configuration> <Server>SQL01</Server> <Instance>INSTANCE01</Instance> <Components> <DataTransformationServices /> </Components></Configuration>
When the tool runs, folders get created for the relevant named instances, but the DTS runs against the default instance only. In other words, the default instance DTS.xml file gets overwritten several times.
Does anyone know if the Upgrade Advisor tool can handle multiple SQL instances on the same server, particularly in realtion to DTS?
I had thought this might have been a limitation as the options in the Report Viewer are "Server" then "Instance or Component", when I am really after "Server", "Instance" AND "Component".
Any suggestions welcome.
Thanks in advance, Paul
View 1 Replies
View Related
Mar 31, 2008
Hello,
this is my problem:
I installed SQL 2005 Standard Edition first, then MSDE plus its SP4. Both instances are named (MC05WXPPROSQLMC for 2005 and MC05WXPPROUCTO for MSDE). I inadvertently had not allowed the TCP/IP protocol for MSDE during the installation, so I did it manually later, through SVRNETCN.exe which also ships with SQL 2005.
Now:
I CAN connect to the MSDE instance with any SQL2005 tools through shared memory. But I CANNOT connect to it through TCP/IP. I guess that this is because wrong port binding for the SQL2005 instance, MSDE instance and SQL Server Browser, but I'm not sure.
My system is Windows XP Professional.
Please help.
Any hints welcomed,
Pavel
View 5 Replies
View Related
Jan 11, 2007
Hello SQL colleagues,
I need to add 5 new named instances on a SQL Server 2005 Enterpise Edition.
Is there a fast way to do it?
Best Regards,
John
View 3 Replies
View Related
Dec 11, 2007
Hello, I'm trying to list the default and named instances on our domain. When I run SqlBrowseConnect all I get back is a list of our servers, for example:
COMP01
COMP50
I'd like to get all the named instances as well, a list with:
COMP01
COMP01DD
COMP50
When I run "osql -L" I get the full list, but not with SqlBrowseConnect. I have tried to set SQL_COPT_SS_BROWSE_SERVER to (SQLPOINTER)NULL which, according to the docs, "[...] returns information for all servers in the domain." I have also set the SQL_COPT_SS_BROWSE_CONNECT to SQL_MORE_INFO_YES without any luck.
Any ideas on any property I might be missing?
Cheers,
Chris
View 9 Replies
View Related
May 6, 2006
Hello, I tried this and it doesnt work, I just started up the service with -T flag on default instance but I havent been able to start it with -T flag 1400 on named instances.
How can I Know that the directory MSSQL.4 is the MIRROR instance??
C:Archivos de programaMicrosoft SQL ServerMSSQL.4MSSQLBinn>sqlservr.exe -T
1400 MIRROR
I tried LUCHOMIRROR, MSSQLSERVER$MIRROR
and It doesnt work
Thanks
Another question I have, in the documentation it says that mirroring is only for evaluation purposes and not for production environments, what does it suppose to mean? MSFT didnt test the mirroring feature enough? If its not suppoerted why its included..?
Microsoft support policies do not apply to the database mirroring feature in SQL Server 2005. Database mirroring is currently disabled by default, but may be enabled for evaluation purposes only by using trace flag 1400 as a startup parameter. (For more information about trace flags, see Trace Flags (Transact-SQL).) Database mirroring should not be used in production environments, and Microsoft support services will not support databases or applications that use database mirroring. Database mirroring documentation is included in SQL Server 2005 for evaluation purposes only, and the Documentation Policy for SQL Server 2005 Support and Upgrade does not apply to the database mirroring documentation.
View 1 Replies
View Related
Aug 29, 2007
Ok, here's the deal. This has been killing me for months now.
Here's the setup - SQL 2000 database on a Shared Infrastructure (cluster). I have a database on a named instance. My port number is xxxxx. I have dbo (through Windows Auth) permissions on my database. When I connect at the office, I get through fine, no question. When I connect at home, I get error 26 in my asp.net 2 app (using System.Data.SqlClient), cannot find SQL Server database. I can connect through the SQL 2005 Management Studio using the same servernameinstance name I use at the office. I can connect through the SQL 2000 Query Analyzer using servernameinstancename;(semicolon)portnumber. I've tried all sorts of combinations in my web.config -
servernameinstancename,(comma) portnumber
servernameinstancename;(semicolon - causes web.config to blowup) portnumber
ipaddressinstancename, (comma) portnumber
and i still get nothing. usually it's 'error 26' - but if i use this:
Data Source=ipaddressinstancename,portnumber;Network Library=DBMSSOCN;Initial Catalog=xxx;Trusted_Connection=Yes;
I get 'Login failed for user domainuser'
I've tried making an alias. I've tried using ODBC. I've even tried a freakin' DSN. No dice.
Nothing seems to work - I'm at the end of my rope. Can someone please help?
View 4 Replies
View Related
May 28, 2015
I have a 2012 AlwaysOn DB Mirroring environment set up with two nodes. Both have 5 installs of SQL named instances.
The issue we are having is when we patch one server and fail everything over, some of the applications will error. Some of the applications had to have their web.config files updated with hostinstance name because it seems to not work with DNS.
View 5 Replies
View Related
Sep 11, 2006
Hi All..
We are planning to build a cluster environment on MS SQL 2005. We want to install multiple named instances in a single database server and use cluster for that database server.
Is this option possible ? Any relevant documentation would be helpful
Thanks in advance
Regards
Madhav
View 2 Replies
View Related
Jul 20, 2005
Hello,What could possibly cause data in the SQL server database to beremoved, except being deleted manually? We had a couple of situationswhere data in certain records disappeared although the records werestill there. The data is entered and editted through the web interfacein ASP. The web interface is accessed by anyone who has an account inour database.I am more of a web programmer, not a SQL server administrator, so notvery familiar with SQL Server log or error tracking. If you cansuggest any way to track this kind of events (data disappearing), Iwould appreciate it very much.HB Kim
View 10 Replies
View Related
