hi everybody
i have a problem while trying to connect to my sql server database
1st i have created my database from my HELM control panel
database name :ramy
IP Address: 74.52.76.178
Local Port: 1433
Remote Port: 1501
thats all but now iam trying to open it via ms sql server enterprise manager but i cant
1st i click on register server
then he ask me for available servers i write : 74.52.76.178
then i select sql server login info
then he asks about username and password
username : ramy
password : 5402248
(these are correct values ) use it freely its just for trials
i get error message that he cant connect or login faliure
my question now
where i put the ip address and where to put the port
thanks
I have a database on my server provider ..and i connect via Enterprise Manager ...the thing i want to know is if theres a way to connect direct to my own database ..instead of having all databases in the tree layout and then selecting mine
is there a way in Enterprise Manager to point the Register Sql Server direct to my database ??
I want to set up a tunneled ssh connection to a sqlserver in the enterprise manager. I can register the server, but when i want to connect the following error pops up:
I designed a DTS package with eleven different connections. When I try to see the proberties of a connection the enterprise manager immediatly closes without giving me a warning. This happens only with two connections (in my example M1 and M2). This mistake has no influence to the execution of the package. In my opinion it is a fault of the DTS package desinger but may be that I made something wrong. Is there anybody who knows this mistake? Thanks for your help.
I have Enterprise Manager version 8.0When I try to register an online databse provided by an ISP I get thefollowing error message:"SQLServer does not exist or access denied[]ConnectionOpen(Connect()"I have tried it many times and checked user name, password, port 1433(as required by ISP), all to no avail.I am running SQL Developer and I have no other versions of SQL or MSDEon my computer,I would be most grateful for any help than anyone can give in solvingthe problem,Best wishes, John Morgan
I have had a problem with Enterprise Manager connecting to SQL Server. At first this problem was experienced with one particular network user... whichever PC he logged onto, Enterprise Manager took ages to connect to SQL Server and every operation was painfully slow. Creating a new Windows NT logon fixed the problem.
I now have this same problem but only on my PC. It doesn't matter which Windows NT logon I use, using Enterprise Manager is painfully slow. I've tried creating a new Windows NT profile, checking the hard drive for errors, defragmenting the disk, reinstalling Enterprise Manager etc but nothing works.
What is strange is that connections from VB applications on my PC are fast. It is only Enterprise Manager that is slow.
I am using the latest service pack for SQL Server.
I thought it could be a problem with the Enterprise Manager registry values but don't want to start messing with them!
Has anyone else experienced this problem? Any advice would be great as I can't find any help from microsoft other than installing the latest service pack for SQL Server.
I am using a dial up connection to the Internet and to an online SQLServer database.I have a problem in that when I use Enterprise Manager to access evenmy local server , or even, it appears, when it is just open with noconnection to any SQL Server, I experience very slow data transferover my normal dial up connection.I am reasonably sure it is Enterprise Manager causing the problem aswhen I close it and redial I have an acceptable rate of data transferusing my dial up connection.Can anyone:a. support my conclusion that Enterprise Manager is the probablecause of the slow connection.b. suggest a solutionBest wishes, John Morgan
Hi,I am seeing very slow connections from some client enterprise managersto server. Even at server level it takes 1 minute or less to open adatabase. I have adjusted some of the memory for the SQL server, butthere are only about 60 Dbs on the server, totalling about 2 GBs.CPU is very low at all times, 1 GB of ram, p3 1.4Ghz. SQL 2k.I know I should refrag the disk, but is there anything else I can doto speed up SQL operation via enterprise manager--ODBC connections is fairly fast, as well as query analyzer.Adam
Hi,I have an interesting scenario. I have a SQL Server 2000 Standard Edition instance running on Computer A. I'm trying to access it through computers B and C.Computer B has Sql Server 2005 Express Edition installed and I was able to use its Management Studio and connect to instance on Computer A.Computer C has SQL Server 2000 Standard Edition installed. When I try to connect to the instance on Computer A, I get connection failed message.I checked some settings. Both TCP/IP and Named pipes are enabled on the instance in A. The TCP/IP port is set to 1433 for both client and server.Please give me some ideas as to how I can solve this problem. -Thanks
I am using SSIS 2005 on Windows 2003 server. Using Excel Source to dump the data for staging database. I am getting following error while I execute it through BI studio's execute button.
I have deployed my packages into Sql Server and I am using Configuration File. As my Data Source is Excel, I have changed the connection string during deployment with Server Path. But I am getting the following errors. Actually the File Exist in Path. May I know What is cause of the issue? Do I need to give any permission to execute the package.
SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
component "Excel Source Service Contract Upload" (1) failed validation and returned error code 0xC020801C.
One or more component failed validation.
There were errors during task validation.
DTS_E_OLEDBERROR, Error Code: 0x80004005 Source: "MS JET DB Engine" Description : Path is not valid
On one of our machines, all of the SQL Server 2000components except for the main Server component (SQL Servercore) itself were installed (Management tools, etc) a while agoand everything was running fine. Now I go and add/install theServer component and then Service Pack 3a.It seems that Service Manager won't start up (I get an hourglass cursor)and now I find that Enterprise Manager won't run as well. No errormessages appeared and I don't think I saw anything unusual inthe log file.However, I can use Enterprise Manager on a differentmachine and connect to the database (so the databaseitself seems to be running).Any suggestions as to what the problem might be and how tofix it? I like to see if I can repair this without havingto do a reinstall.Thanks.PF
IF someone can assist me. Everytime I load up enterprise manager the service manager turns off. And the enterprise manager can't connect to the local database. But everytime i turn it back on and try to connect again it shuts it off and around and around we go. Help would be appreciated. Thanks.
I am working on SQL Server 2005 (x64) with Windows Server 2003 (x64) operating system. I am having a major issue in SSIS. Here is the detailed explanation of the issue :
I have an EXCEL file in 2003 / 2007 version. It contains some data. I want to import the data using SSIS into SQL Server 2005 (x64) database table. I have taken "EXCEL FILE SOURCE" and "SQL Server DESTINATION". It was failed on importing data. Surprisingly it works fine in SQL Server 2005 (x32). Can you please explain why it is NOT woking on (x64) ?
Here is the error code i am getting:
[Excel Source [1]] Error: The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009.
I have an SSIS package that I need to modify. It was developed in Visual Studio 2005 and runs faithfully in production on SQL Server 2005. Suddenly, I can't open the package on my own workstation. I see a big red "X" image and a message stating "Microsoft Visual Studio is unable to load this document." The real reason the document can't be loaded appears to be:
Error loading DataWarehouseLoader.dtsx: The connection type "OLEDB" specified for connection manager "Warehouse Logging OLE DB" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
Does anyone know what causes this and what I can do? The package has been in production for 9 months and I've never seen this problem before.
I have a package that uses a for loop to iterate through an unknown amount of excel files and pull their data into a table. However, there will be cases when the file is corrupted or has some sort of problem so that either the transformation will fail or the excel data source will fail with an oledb connection error. Could anyone suggest a clean way to trap these errors? Specifically, the "Cannot Aquire Connection from Connection Manager", which is the excel connection.
I installed SQL Server MSDE 2000 but I can't find how to start it. Does this package include an Enterprise Manager or not? I thought that maybe it was a standard XP Pro feature. I had no problem finding it in W2000 Pro.
Has anyone encountered this error: When you are in Enterprise manager and you select a database then the tables tab and then you select a table and go to open table- select all rows, I get an error--An unexpected error happened during this operation-Query Designer encountered a query error! Please let me know if you have seen this. Also, when I access this from one networked computer I get the same error, then when I access it from another I do not!! The servers are interacting with Pivotal. The one that works does not!!
Hi all, I have SQL 7.0 desktop addition installed on my local win NT workstation. I am able to connect to my local server using Quary Analyser but when i am trying to connect using EM, i am not able to connect. I am receiveing the following error message. __________________________________________________ ___________________________ A conncetion could not be established to "servername" - Specified SQL Server not found. ConnectionOpen(CreateFile()). Please verify SQL server is running and check your SQL Server registration properties(by right clicking "servername" node) and try again. __________________________________________________ ___________________________ I have tried as said in the error message and also tried connecting with "sa" but its not working. I can see that the server is running and i am able to connect through QA.
I am fairly new sql dba in a company and I am sure Enterprise Manager is installed on PC's and it shouldn't. Is there a way of finding out other then visiting each workstation. Thanks in advance..
I am considering upsizing my Access 2000 DB to a SQL 7 server. I was told that having SQL 7 Enterprise Manager is highly prefferd but not essential as I can maintain the upsized DB with Access 2000. The only way that I have been able to find JUST enterprise manager seems to be with purchasing the whole SQL 7 program for $1300! Microsoft cannot be that cruel, that you have to buy the whole program just for Enterprise Manager!
My questions are:
Can I download just MS SQL 7 Enterprise Manager anywhere for a reasonable fee or free?
and
if not, can I continue to use Access 2000 to maintain the SQL 7 upsized DB?
I have access to a SQL 7 server via my ISP Hosting account. I know Enterprise manager comes with the server software, but how can I get a copy of JUST Enterprise Manager?
Is it possible to administer both 6.5 and 7.0 databases from the same SQL Enterprise Manager? I have read that you cannot do this because the 7.0 "plug-in" to the MMC wont work with 6.5 databases.
We had database corruption and cannot access the Enterprise Manager. DBCC returned errors 9000 to 9999 which I can't get any suggestions on how to handle from BOL. Any ideas!!!!! Thanks.
Hi, I would like to know if we can present users to access details database information about the databases on a server through Enterprise Manager. If you create a SQL login and do NOT give it access to any database, if someone logons on your server with enterprise manager, even though he does not have access to any database, he will still see the list of all database on your servers plus tons of sensitive information like database owner. Is is possible to limit enterprise manager to only view information about database that the user has access to?
How can I force users of Ent Manager 6.5 to enter a name/password when connecting to a server that has been registered? I dont want to use the sa name and password so that anyone could use my workstation to access our servers.
Does anyone know how to turn off or disable the auto discovery for Enterprise Manager. Apparently our Network group is complaining that Enterprise Manager is generating noise on the network, it is not signifcant in volume but they complain it impacts there ability to detect hacking attempts on our network because it causes some false positives. I generally keep Enterprise Manager running because I will always have some manual job running from it and we have so many servers it takes awhile for them to all load when I first fire it up.
