Developers wanting to access sql server developer edition on XP workstation in small office network (workgroup) will have problems using windows authentication (trusted connection) if the XP "server" machine has "simple file sharing" enabled.
Simple file sharing in XP can be disabled in control panel - folder options.
For this sneak mode to work accounts with the same user and password should exist on both "client" and "server".
I recently installed VB6.0 Enterprise on my system. As a part of the installation is the option to install SQL Server 6.5 Development. I elected to install SQL. The install went without any glitches. Upon going into SQL Enterprise Manager, I was asked to register the server where SQL was running. My understanding was that SQL would allow me to register the name of my host system. (This is a stand alone system with VB6.0 and Sql development 6.5 installed - no network attached). SQL will not allow me to register my server's name as the host server. It says that if cannot connect to the named server. SQLSERVER and SQL EXEC services appear to be running without any problems. Anyone have any idea where I should start or what could be disallowing my connection/registeration of my server. Any help would be greatly appreciated..... Thanks... Tom
I have the following connection string in my Windows app that works fine on the Server: workstation id=SCSXP;packet size=4096;integrated security=SSPI;data source=scsxp;persist security info=False;initial catalog=nala But when I use that string on a workstation, it times out. I do have a Network connection to the Server. How should I modify the connection string to work on the workstation? Thanks, Bill
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.
Could someone please tell me what I have to set at the Server side so that I will be able to STOP and START the SQL Server using Enterprise Manager and `sa` login remotely, say from the workstation.
This might not be a SQL Server question, might be something else. Ihave a workstation on a LAN that can't connect to the SQL Server. WhenI try to configure a User DSN to connect to it, the server name I wantappears TWICE in the list of possible servers. No matter which one Iselect, it can't get the connection.The workstation also can't connect through EM or QA.We've checked the user's permissions, we've re-installed some serverpacks, re-installed the Client Tools, we've even hunted through theregistry, everything looks OK, but we still can't connect. This is theonly machine on the LAN that can't connect. Everybody else connectsfine.I'm stumped. Any ideas? Anybody ever seen the server name appeartwice like that?-Emily
I€™ve moved my server folder which contains about 10 dtsx and its ADO .net connection as well as OLEDB into my folder workstation. Then, when I€™m gonna to open them appears this error:
Error 1 Error loading M_HAC_Modelo198_CECA.dtsx: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Clave no vĂ¡lida para utilizar en el estado especificado.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. c:ssishacienda_anualM_HAC_Modelo198_CECA.dtsx 1 1
Translate into english: "Clave no vĂ¡lida para utilizar en el estado especificado" = Invalid key for to use in the specified state (more or less)
What really happen? Well, I wrote these packages using a domain user (belong to Administrators group in Active Directory) via Terminal Server and now I want to modify them by mean my domain user (I already have got installed sql25k client tools and the stuff required)
I thouht that these connections were saved in the same folder where dtsx, dtsproj, etc..
Solution? Create them again? I hope that it will be a piece of cake otherwise...
I set up the collector, and specify the Run As as my AD account in the Collector Set - Properties - General screen. My AD account is the local admin of the remote server.
However, the collector does not seem to work. Although the collecting set is shown as running, the The blg file stays at 64K. If I open it, there is nothing inside (no counter at the bottom). What did I miss?
I thought I had applied sp2 successfully but I discovered when I tried to apply the hotfix ( sqlserver2005-kb933097-x86-enu.exe), that the SQL Server Tools and Workstation Components wasn't at the 3042 level.
The recommendation in the log file is to:
"Update 3152 is dependent on prerequisite update 3042. Exit setup and refer to the Knowledge Base article to find the prerequisite patch."
Does anyone know where I find the prerequisite patch?
Any help would be appreciated.
Regards Noel
Time: 03/13/2007 18:05:39.045 KB Number: KB933097 Machine: NOEL_EVO OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600) Package Language: 1033 (ENU) Package Platform: x86 Package SP Level: 2 Package Version: 3152 Command-line parameters specified: Cluster Installation: No
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Products Detected Language Level Patch Level Platform Edition SQL Server Database Services 2005 (SQL2005) ENU SP1 2005.090.3042.00 x86 DEVELOPER SQL Server Analysis Services 2005 (SQL2005) ENU SP1 2005.090.3042.00 x86 DEVELOPER SQL Server Reporting Services 2005 (SQL2005) ENU SP1 9.00.3042.00 x86 DEVELOPER SQL Server Notification Services 2005 ENU SP1 9.00.3042.00 x86 DEVELOPER SQL Server Integration Services 2005 ENU SP1 9.00.3042.00 x86 DEVELOPER SQL Server Tools and Workstation Components 2005 ENU SP1 9.1.2153 x86 DEVELOPER
********************************************************************************** Products Disqualified & Reason Product Reason SQL Server Tools and Workstation Components 2005 The product instance SQL Tools does not have prerequisite update 3042 installed. Update 3152 is dependent on prerequisite update 3042. Exit setup and refer to the Knowledge Base article to find the prerequisite patch. Install the prerequisite and rerun the installation.
I have need to configure Microsoft SQL Server 2014 express on my development machine. I have never worked with Microsoft SQL Server and could use some direction. I have done MYSQL work before but the seems much different.
I created a CLR UDF that returns a large number of rows, when I run it from my VPC (XP, SQL Server Developer Edition and 1GB Memory) it takes approx 2 min and 30 secs to start displaying the rows (Using Management Studio), when I run the same query in our development server (Win 2003, SQL Server Enterprise Edition, 8 GB Memory and 8 Processors) it takes more than 15 min to start displaying the results, does anybody have an idea why is this happening?
Everytime I do an install of SQL Server 2005 and I don't select to install all components (even if I make sure Workstation components and all sub components are selected) SQL Management Studio never loads. The setup completes without error however there is no SQL Management Studio anywhere on the system. I know I have searched hard for it. Has anyone else had this problem? Am I missing something?
We currently built a new SQL2005 server and have serveral sentitive Payroll database hosted in it. I managed to seperate some roles to various users to prohibit them to direct access the data but can access it via front-end application.
The problem is I setup a backup operator with the following rights
Server Roles -- Public
User Mapping
User Mapped to this login / Database membership for
PayrollDataBase_1 BackupOperatorName
db_backupoperator / db_denydatareader / db_denydatawriter / public
However, I try to login using the 'BackupOperatorName' in my workstation and Backup the PayllrollDataBase_1 to a server shared path says E:SqlDataBacupPayrollDataBase_1.BAK. Afterward, I copy it over the network back to my workstation and RESTORE in back to my local SQL2005 instant using the local SQL2005 SA user. All data CAN BE browse
Anyone please help to post how to restrict the Backup operator can only Backup the database but cannot restore to its local SQL2005 instant
I have installed successfully Microsoft SQL server 2005 in MSCS.
However the set up did not install Workstation components (client tools - SSMS etc).
I have successfully installed workstation components in one node of cluster.
However setup is giving following error while installing workstation components on other node. (From this node MS SQL server 2005 was installed).
Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.
I did "C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, /setup".
It executed but no error, no output.
Any gues, help in isolating issue?
Any more information required.(Media is ok. Setup has been tried after reboot. There is enough disk space.)
Regards.
Mahesh =========== Setup
1) Microsoft Cluster of two nodes. 2) Hardare - HP Blade servers 3) OS - Windows 2003 EE with SP2 4) SQL Server 2005 Standard Edition with SP2.
=============================
MSI (s) (B0:7C) [17:40:20:390]: Note: 1: 1722 2: SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A 3: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe 4: /setup MSI (s) (B0:7C) [17:47:23:609]: Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
MSI (s) (B0:7C) [17:47:35:921]: Note: 1: 1729 MSI (s) (B0:7C) [17:47:35:921]: Product: Microsoft SQL Server 2005 Tools -- Configuration failed.
MSI (s) (B0:7C) [17:47:35:953]: Cleaning up uninstalled install packages, if any exist MSI (s) (B0:7C) [17:47:35:953]: MainEngineThread is returning 1603 MSI (s) (B0:A0) [17:47:36:062]: Destroying RemoteAPI object. MSI (s) (B0:80) [17:47:36:062]: Custom Action Manager thread ending.
I'm having some problems debugging SQL Server stored procedures on a SQL Server 2005 server. I have installed Visual Studio 2005 on a workstation running Windows XP, now I'm trying to debug a ASP.Net web application that has some code that executes the stored procedures on a Windows 2003 Server running SQL Server 2005.
I opened VS2005 ... created a connection to the SQL Server 2005 instance ... open the Stored procedure ... right click the stored procedure name and selected Step into Stored Procedure and the following message is displayed:
Unable to start T-SQL debugging.Could not attach to SQL Server process on 'ServerName'.
Hi all!Is there any function in SQL that I can use to get current date fromworkstation? All functions which I tried (now(), getdate() etc.)returns current date from server but I need date from workstation.Regards,Mirnes Lemes
I would like to know if one can adminiter SQL server remotely using MMC on NT workstation? If so, how do you install the MMC and SQL Enterprise Manager Add-in on NT workstation?
How can I configure my workstation running WIN95 to used the SQL Enterprise Manager from the server end and other utilities. I have installed the client network utility.
Reason to use enterprise manager because I wanted to perform administrative tasks on my workstation and I've installed SQL SERVER 7.0(Standard version with 5 clients)on the WINNT 4.0 server.
Hi all;I am trying to replicate our database by using the merge replication.[color=blue]>From server side I tried to connect to the workstation. I have[/color]installed MSDE to the client machine. I can see the machine name on theSQL Server Group however I wasnt able to create the conncetion betweenthe machines. I have checked my network connection, there is no problemI can see the machine and I can connect it through the network. I triedto use Client Network Utility with Named Pipes and TCP/IP but not agood news. I couldnt achieve to connect to the machine. So couldsomeone please help me out with this problem. I am really in trouble Ihave to find out this end of this week.RegardsAs
I've got VS 2008 Pro installed, as well as SQL Sever 200 (which I must keep installed). When I run the install for SQL Server 2005 developer edition, it continually fails to install
I had a perfectly good working copy of SQL Server 2005 installed. However, at some point I needed the Report Services Designer so I could edit my reports in Visual Studio. I inserted the CD and selected the feature from the list and it installed. Only problem being that it has completely removed my Management Studio and practically every other tool I didnt explicitly checked when installing the RS Designer.
When I tried to run the same Setup again and check everything, it tells me that there is no change between what I have selected and what is installed, which sounds like total bs to me, since my pc doesnt have a management studio etc anymore.
Out of pure misery I decided to remove my entire SQL Server installation, inc Instance, hoping to start anew and achieve the result I wanted with the least amount of frustration. I ended up here and followed it all the way: http://support.microsoft.com/kb/909967
When I started reinstalling, I ran into something new. The installer refuses to let me install anything but the Workstation components, books online and development tools. All the other options are greyed out and not even available.
Someone please help me get my SQL Server back up and running because I'm getting hopeless.
It appears that there is no way to install SQL Server 2005 Workstation Components on an x86 operating system (XP in this case) if you have the x64 install disks (Standard Edition). Can someone verify this?
I am finding it hard to believe that workstation components for a standard Windows client environment are not distributed with the version of SQL Server that matches Windows 2003 x64.
Hi again, could anyone tell me what to do about this...I'm not a dba but I do need direct access to the sql server such as scheduling new jobs (I can execute them immediately as pkgs or even run them as jobs on my machine, but to schedule I need to go to the server. The NT administrator does not like the idea of anyone else touching his server, so is there any way to circumvent the situation and do the scheduling from my workstation? Someone had mentioned creating an icon on my desktop but I'm not clear on the idea. Thanks a million. I get great help on this website.
I have installed SQL 6.5 client tool on to my workstation. Since then, we have upgraded to SQL 7.0 on our server. I installed SQL 7.0 client tool to my workstation and have been using it. I want to remove SQL 6.5 client tool from my workstation and do not know how. There is no uninstall button in the SQL 6.5 folder nor this program exists in Add/Remove Program in COntrol Panel. Can you help? Thank you.
I have 3 NT Workstations that will not connect to my SMS database using NT Integrated Security. The SQL 6.5 server is set up to use mixed security. The only way to connect to the server is to use a standard sql account. Any ideas? THis happens to all users even administrators.
I have Vista Ultimate (IIS Enabled), SQL Server 2005 Developer Edition (downloaded and ran the SP2 Update), Visual Studio 2008. VS2008 installs no problem. When I install SQL Server 2005, I get an error when it trys to install the last part( Workstation Components, Management Studio, etc). I have tried FULLY, MANUALLY removing all SQL products and registry entries. I have used Windows Installer Cleanup Utility. I have tried Microsoft's recommended way of manually removing SQL Server 2005. If I manually run SqlRun_Tools.msi the error comes up right away.
The error is: "A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component."
Here's the Setup Error log: http://toby.pastebin.com/f63405e24
Hey yall. I'm a DBA in a company where I do NOT have the ability tocontrol who logs into my SQL servers as administrator, so I'm lookingfor a way to uninstall the workstation components WITHOUT completelyuninstalling all of my instances. Does anyone know how to do this?All I can find is the complete removal option in add/remove, and theinstall cd setup doesn't have a remove function that I can find. Anyidea's?The reason for wanting to do this is so that every tom dick and harrythat logs in as administrator doesn't have the ability to just open EMand do what they please. I want to force people to log in fromanother box so I can get tighter control over who can access mydatabases. Any help is awesome, thanks!Joshua Austill
I'm having no success install SSMS on a 32 bit workstation from 64 bit media.
I'm aware from researching that the SSMS is 32 bit, in fact I see it run as a 32 bit app on the server.
However, when i try and install from the 64 bit CD or DVD I get errors such as not a valid Win32 application, or when i tre random msi's guessing as to which is ssms I get "This installation package is not supported by this processor type. Contact yoru product vendor."
I run a Pent D 2.8 on 32 bit XP
Any assisstance on how to install SSMS on a 32 bit workstation from the 64 bit media would be greatly appreciated.
Just getting started using SSRS (SQL Server Reporting Services) 2005 in production and I've got what should be a simple question.
How do I configure a development workstation to be able to develop SSRS reports which will run on a networked server running SQL Server 2005?
Here is my problem... I installed VS2005 (Visual Studio Pro 2005) and SQL Server 2005 workstation components (with SQL Server SP2) on the workstation but the "Business Intelligence Projects", "Business Intelligence Wizards", and "Report Projects" are missing from the New > Project types. How do I get them added?
I can access the network SQL Server and the http://<Server>/Reports from the workstation. On the SQL Server I can develop & deploy reports using BIDS (Business Intelligence Development Studio), on the server. But on the workstation I cannot create a new Report Project nor can I open an existing reporting project (rptproj) or solution. (I get the error that rptproj is not intalled and that I should install the associated program...which is what?)
WORKSTATION:
Windows Vista Business with all the latest updates.
Visual Studio Pro 2005 with SP1 & Vista SP1 Update installed.
SQL Server 2005 Standard with SP2 & Reporting Services installed.
This should be a simple question, but I'm suprised that it is not working after installing what seemed like the appropriate components from the SQL Server 2005 disk.
Any suggestions on how to get the SSRS projects to show up and work in the Visual Studio 2005 on the development workstation?
I cannot install management studio on workstation (development machine).
I have removed both instances of SQL Express (one installed with VS2005, the other with Office Business Tools). Have ensured all SQL components are removed.
Is it true that SMSS won't install over IE7, that must have IE6 installed to get SMSS.
