We have standardized on Hyperion as our reporting tool. So far I have
only set up a couple of Access databases as data sources for it. Now
there is a request to report off our eOn (telephony management) SQL
Server database using Hyperion. The eOn SQL Server box is in a
workgroup that is not part of the rest of our domain. (We only have
one domain because we don't have a "forest", whatever that means.) It
is behind a router owned by eOn along with a PBX and some other stuff.
Setting up a data source for Hyperion requires creating a special data
source file called an .oce on the box where the Hyperion fat client
(required for most administrative tasks) resides, and also setting up a
different special data source file called a .das on the server where
the Hyperion services run. (The analysts and end-users do not have the
fat client, their access is web-based.)
I have to register the eOn SQL Server by using the IP address and SQL
Server authentication. (I was told that I can't use Windows
authentication because it is not in the domain.) From the box on
which the Hyperion fat client resides, I cannot register the eOn SQL
Server. The error message is "timeout expired". Tracerting indicates
there are no intermediate hops when attempting to connect from this
VLAN. From my desktop, which is on a different VLAN, I can connect to
and register it. This trip includes one hop at our 6509. From one of
my servers which is on the same VLAN as the fat-client box, I am able
to connect and register. On the fat-client box I tried deleting and
re-registering another SQL Server and there was no problem.
The IP address I have to use to connect to the eOn SQL Server is *NOT*
the actual IP address of the box it resides on, but rather the eOn
router, which translates it to the address of the server. We have no
control over this, eOn creates this setup. I'm not sure how it knows
which of the devices behind it a given message is for.
I'm trying to run a test from my test environment which is a non-domain Windows 2000 server to access my domain 2003 with SQL2005. I have install 2005 tools to try to access the SQL server.
- I have try following the KB265808 - no success. - Reading alot of blogs and it seems all are pointing to the same problem. "Remote access" but the settign is enabled.Error Message:
TITLE: Connect to Server ------------------------------
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
Question: Could Windows 2003 security be blocking access? I'm using sa account to access.
Also, sa account does not seems to work for remote access. It is ok when accessing locally.
-A "master domain" AD, a "sub domain" AD, a trust relationship between the two (sub trust master) -A sql server 2005 on a win server 2003 in "sub domain" AD -A linked server to "sub domain" AD -A linked server login using a "sub domain" admin acccount -A view to this linked server -A grant on masterDomain/Domain Users to the database -A grant on subDomain/Domain Users to the database -We want all connections done through "Windows Authentication" not "Database Authentication".
Queries on the view work fine using "sub domain" user accounts. Queries on the view fail using "master domain" user accounts (including master domain admin accounts)
"Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "ADsDSOObject" for linked server "ADSI" reported an error. The provider indicates that the user did not have the permission to perform the operation."
All connections are done through "Windows Authentication" not "Database Authentication".
Can we establish cross domain connectivity with "Windows Authentication" ?
Below are details of the implementation:
SELECT TOP (100) PERCENT * FROM OPENQUERY(ADSI, 'SELECT displayname, givenName, sn, cn (etc...) FROM ''LDAP://OU=PEOPLE,DC=subDomain,DC=com'' WHERE objectCategory = ''Person'' AND objectClass = ''user'' ')
In SQL Server Mngt Studio in Server Objects/Linked Servers/Providers/ ADSI properties security tab I have:
"connections will: <be made using this security context> Remote login:'subDomainAdminAccnt' With password: 'subDomainAdminAccntPassword'
Error: Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "ADsDSOObject" for linked server "ADSI" reported an error. The provider indicates that the user did not have the permission to perform the operation.
Msg 7320, Level 16, State 2, Line 1
Cannot execute the query "SELECT displayname, givenName, sn, cn
FROM 'LDAP://OU=PEOPLE,DC=subDomain,DC=com'
WHERE
objectCategory = 'Person'
AND objectClass = 'user'
" against OLE DB provider "ADsDSOObject" for linked server "ADSI".
Does anyone know what SQL Server uses to identify other servers which contain SQL Server, when you attempt to register a new server through enterprise mgr? For instance when you go through the new sql server registration wizard, the second screen allows you to choose what server you would like to register, and it shows you the available servers on the lan that contain sql server 6.5 or 7.0. What is enterprise mgr using to locate the other servers containing SQL Server? Thanks in advance.
I just created a new db on a programmer's machine. Now I cannot register his sql server on my sql server. It doesn't like 'sa'. I can connect as 'administrator' but then I cannot do anything. Seems like the logins are messed up. I am not able to execute any stored procedures as administrator.
I have recently installed SQL Server 2000, And trying to register a remote SQL 7 server, through enterprise manager which fails with the following error message: Timeout expired
I am able to connect to the same server using Query Analyzer. I was able to register this server from the same machine, prior to the installation of SQL 2000. Also, I am still able to connect to other SQL 7 servers, with SQL 2000 enterprise manager.
Over the weekend we changed ISPs on our SQL Server 2000 machine. The only configuration change was the IP address. I'm able to register the server from client machines using EM which are on the same network, but I can't register it from home. I've verified the IP address, username/password etc and the connection just fails with the message 'Sql Server does not exist or access is denied.' Could this be a port issue? Any ideas? Thanks.
Please pardon my ignorance, but I am using MS SQL2000...On system start upthe Server Service Manager defaults to server "BACK" which is not evenregistered in the SQL Enterprise Manager. Enterprise Manager shows only oneserver " OFFICE" which is the one I want to default to. How do I remove the"Back" server completly from the system?thank you
Ok, well I just installed Visual Studio.NET 2003 on my PC, and to prepare for next years courses I thought I might get going on some of the exercises. But I am rather new to this and when I try to expand "SQL Server" in the "Server Explorer Window" I get this message.
Could not automaticly discover any SQL Server instances. Choose Register SQL Server instance from the shortcut menu if you know there are SQL Server instances on this machine.
From there all I know is that I can right click on "SQL Server" and chose register new instance, but I do not know what to enter, and it suggrests leaving it balck but that doesn't work. I will get an instance but when I try to expand it another error pops up.
So as you can see I have no idea what I am doing when it comes to SQL Server, can any one help me with this?
hi, I have just installed Ms sql 6.5 and tried to register the server, I typed a name and did not get any response. This installation was on a single pc which is not connected to the network... any idea of why the server is not responding. Do I need to give a name to the pc before I installed the sql server and then use register the server...
Hi all, I have installed SQL Server 2k personal ed on Win xp and now I want to add another instance other than that one I added when installation.But I do not know how? I used EM and its wizard but it says could not find server or access is denied... -any quick help is appreciated
I am trying to register a SQL Server 2000 on a client machine. It was workig fine , until yestarday when he moved and got a different system IP. But one of the SQL Server 'A' is getting connected. But when I try to register the server 'B' its giving an error " SQL Server does not exist or access denied". I am giving correct login credintels. When I tried to ping ( using cmd) the Server 'B' , the system was able to connect.
I was on the SQL Server Express Edition site (http://www.microsoft.com/sql/editions/express/default.mspx), and I used a link that suggested by registering my SQL Server Express I could get some royalty free images and an e-book. I followed the process, and they immediately sent me an email full of links, some of which do not seem to work. The link for the Registration Benefits Portal takes me to a "Page Not Found" error on Microsoft. The article within Resources called "Using SQL Server 2005 Reporting Services with SQL Server Express" also doesn't work.
I guess I didn't really need these "benefits", but it was kind of aggravating. This is 10 minutes I won't ever get back.
Since the email said to report any problems to the forums, this is what I am doing.
I have set up SQL Server Express with a Server Name / Instance name RMUKOCSQLEXPRESS
However, from another Server running the full SQL Server 2005 Management Studio I cannot seem to register the above Server. The usual message of : "An error has occurred while establising a connection to the server...."
I have allowed remote connections, set up default, named pipes etc on the SQL Server Express. Yet from the SQL Server Express Management Studio I can register full 2005 Server / Instances but not the other way round.
Is there anything else I need to be aware of or check for.
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
When I try to regiter a sql server, I take this error message. I am using Sql Server 2005. What is the problem,can you help me?
I am running SQL 7 (SP3) on a 2000 Server. When I configure the server as part of the Workgroup I have no problems connecting from the workstation. However, if I join the server to our 2000 domain, I cannot connect and/or register the server from the workstation through EM.
Is this a security issue? If so, what are the minimum requirements or what else am I missing. Any suggestions would be appreciated.
We are running 3 versions of SQL - 6.5, 7.0, and now 2000. I have all three versions installed on my PC and run Enterprise Manager to manage the 2000 and 7.0 servers. The one 7.0 server is registered fine. When I try to register the other 7.0 server I get the following message -
(SQL DMO) SQL Server xxxx must be upgraded to version 7.0 or later.
This same server is registered through Enterprise Manager on another PC running the 3 versions of SQL and both SQL 7.0 servers work fine on that Enterprise Manager installation.
Any suggestions as to what I need to do to be able to register the 7.0 server on the Enterprise Manager running on my PC?
I'm trying to register a remote OLAP server under OLAP Manager. After I enter the machine name I get the following:
Errors occurred while connecting to <server>. Cannot open the following registry key on the server computer (<server>): SoftwareMicrosoftOLAP ServerServer Connection Info Do you still want to register this server?
The noticeable thing about this error message is that the registry key is missing the first level (HKEY_....). Has anyone been able to register a remote server? I can run OLAP Manager on the server without a problem. I just uninstalled and reinstalled OLAP services on the server and my desktop. There is a registry key with this path under HKEY_LOCAL_MACHINE on the server.
my SQL is running TCPIP and everytime I register the server from a client, I have to enter in the IP address. Can I use a hostname to map an IP address to a server name and then enter the server name to register the server?
My office computer just had Vista installed on it and while going back through to re-install my software, I have encountered a problem in SQL Server 8.0. (Yes, I know it's old and likely has comparability issues with Vista, but I don't have the option to upgrade at this point.) I have two servers to register. One works fine, but the other won't register and returns the error "SQL Server does not exist or access denied. ConnectionOpen (Connect())". I am able to register these on machines running XP and Windows Server 2003, but not on my Vista machine. Does anyone have any suggestions on how to fix this problem?
My office computer just had Vista installed on it and I have now encountered a problem in SQL Server 2000 sp4. (Yes, I know it's old and has comparability issues with Vista, but I don't have the option to upgrade at this point.) I have two servers to register. One works fine, but the other won't register and returns the error "SQL Server does not exist or access denied. ConnectionOpen (Connect())". I was able to register this one server that isn't working while previously running XP on my office computer and even as a test on another server running Windows Server 2003. This leads me to believe the problem is isolated with my installation on Vista and not with any permissions, etc. I have been scouring different forums looking for a fix for this, but have come up empty handed. Does anyone have any suggestions on how to fix this problem?
helloi am new to sql server and .net programing here is a problem i gotwhile trying to register sql server over internet on sql serverenterprise manager , i open register sql server wizardclick next, gave ip address of the sql server( i want to register) inavailable servers and add it , gave sql authenticationbut got the error"sql server does not exist or access denied coonectionopen(connect())"please advice me how to solve this problemnote: tcp/ip network library is enabled on my server and the client aswelli have also tried this in vb.netDim conect As New SqlConnection("data source =202.154.228.184;net='dbmssocn';database = pmec ; user id = sa;password = sa ")but the same exception is thrownkindly help me solve this problem, i need to solve it badlythanks
When Trying to register a SQL Server using Windows Authentication, I get the following error:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
When I edit the properties and make it SQL Authentication, it works fine. The SQL Server Service is starting up with a domain user account. If that makes any difference. Funny thing is, that my co-worker, can register the SQL Server in his Enterprise Manager using Windows Authentication. We are both Domain Admins and members of the servers local admin group. So, I'm not sure what to do now.
I checked under Security, Logins...and neither of us are listed under there.
After using ADMT to migrate the domain user or group into the root domain, when I use enterprise manager to try and change the permissions allocated to that domain user/group, i get the 'Error 15401 NT user or Group not found'.
This is a correct error as the user is now in the root domain, however sql (in sysxlogins) still thinks its in the child domain.
Is there a simpler way, other than collecting the users permissions, deleting the user from SQL then adding back in with the correct domainusername format, then adding the permissions back?
I tried renaming the 'name' in sysxlogins (not recommended) and while that worked, whenever I tried to add the migrated user to another database, the login name was missing and would not resolve.
I believe it is something to do with the SID not matching.
we recently migrated from our in-house domain to the Enterprise domain. Everything went smooth except for the fact that I can no longer accept my dBs using my SA or my domain admin account. There is only 1 account I can get into the management studio with but it has no admin privileges, so I can't make any password changes or add accounts. I don't have a test environment so kind of hesitant to experiment with our production system.
I have installed SQL SERVER 2000 on my harddrive. And iam trying to registor my computer as a registor but its keep giving me that "Connection failed and not able to connect to the server" ( I dont know the exact message ).
Does anybody knows how to solve it. Iam using Windows XP Professional.
I have a IIS server on "A" Domain. My application is hosted on on a machine which is under that domain.
I have a DB server, SQL server 2000 on B Domain. The server is a named instance of SQL Server 2000. I have a default SQL Server 7.0 on that same machine.
For the application i am trying to connect from the IIS to database server, but i am unable to connect to the named instance, but i can connect to the default 7.0 instance.
The connection string used for the application is as follows: oConn.open "Driver={SQL Server};Server=server_nameinstance_name;Database= db_name;uid=user_name;pwd=password;"
I am getting SQL Server does not exists error messege on page...
Please help, me if any one knows how to connect to the database server which is on different domain and is a named instance using the connection string in ASP page..
Hi all,Have a situation that my company has never run across before. Clientis running NT4 for the domain server, using terminal services 2000 andrunning an application with a SQL Server backend and they areexperiencing locking problems. Once one person gets locked out theneveryone trying to access that tables is also locked out as a result.It is not specific to a certain User, or module within theapplication. It's not a specific time of the day (like when a backupwould be running) and sometimes it's in the middle of the night whenthere are actually less Users on the system.We have 500 customers using this application. Most are using SQLServer backend, alot of the newer customers are using TerminalServices, and the number of Users is not accessive as compared to ourother customers. THe only difference is that I do not specificallyknow of another client with an NT4 Domain server in the mix.We actually switched to SQL Server as the recommended back end due tolocking issues using SQLBase because SQL Server is row locking andSQLBase is page locking. Since making this change we have stoppedseeing the locking for years until now. Is this a SQLServer issue orissue with the NT Domain server?Anyone have any ideas???ThanksA
I'm setting up a simple SSRS implementation for a non-profit organization, using two servers hosted at a data center. The first server has SQL Server Standard Edition and Reporting Services installed. I've designed and deployed a number of useful reports on this server.
I was hoping to isolate this first server by installing IIS and SSRS on the second server, have users browse from the Internet to that second server (over SSL, of course), and have all reports served up from databases (and, presumably, the report server database) on the first server.
During the installation of SSRS on the second server, however, I'm being prompted to specify the service account. According to the help text:
"Reporting Services. Service accounts are used to configure a report server database connection. Choose a domain user account if you want to connect to a report server database on a remote SQL Server instance. If you are using a local report server database, you can use a domain user account or Local System to run the service."
I believe I want to configure SSRS to connect to a report server database on a remote SQL Server instance; therefore, it appears that I need to enter a domain user account. The only problem is, neither server belongs to a domain; they are members of a simple two-server workgroup.
Does SSRS, configured to connect to a report server database on a remote SQL Server instance, require a domain? Does what I'm hoping to accomplish require a domain? Creating a two-server domain seems like overkill for this implementation, doesn't it?
I appreciate any comments and suggestions. Thanks!
