I want my deployment environment to be as centralized as possible, but the processing environment to be distributed.
Here is what I had in mind. I have one server running SQL Server DB and SQL Server Agent. I have all the SSIS packages deployed on this server and schedule them as jobs in SQL Server Agent.
Now I have two other machines just running SSIS service (no other component). When the agent executes the packages, he should use either of the two machines. (Load balancing would be good, or I can manually assign the packages to the machines too).
is this possible? recommended?
Another approach would be that each SSIS Server, also has SQL Server and Agent installed. And respective packages are installed and scheduled on their respective servers. But here I have to maintain the packages and schedules on 2 machines.
I'm trying to test my ASP.NET application. Everything is working to the point of getting to my login page to open. When I try to login I receive and error that the database does not exist or access is denied. I used the developer version of SQL Server to create the database and installed the MSDE on my test PC. Then I copied the mdf and ldf files to the new PC. Is there something else I should be doing? Or any suggestions?
I created a sql database on my development machine for my .net app. There are whole brunch of tables and stored procedures. Now I'm at the point to test my app on integration environment, instead of recreating each table and stored procedure, is there an efficient way to promote them. (note I use both MSDE version on both machine)
Hi all,I am doing a project that involved with the big volume of data to beuploaded to the SQL server. Due to the limitation at my employer'ssite, I couldn't have the bulk admin right. I am looking at thecommand BCP and wonder if there is any copyright issues if I were touse BCP and to deploy the command?Thanx.
I want install the project in client side .. In installation time i want to access the my server .. How i can make the setup file to access the internet.. please help me.....
I tried to deploy a package to production and failed miserably. The error is pretty simple "Format of the initialization string does not conform to specification". Trouble is, I opened my source on the production machine, generated a new connection string from a new connection manager and guess what, the string comes out EXACTLY the same as the one my package is set to point to at runtime. so, where do I start?
some general stuff. There are ADO and OLEDB connection in the package. Each gets its connection string from a variable. the variable is set in a script task which pulls the data out of an encryped sql server column. when the connection string is displayed via a simple message box, it is exactly what I want i to be, e.g. Data Source=a.b.c.d;User ID=A_USER;password=password;Initial Catalog=a_database;Provider=SQLNCLI.1;Auto Translate=False;
I am guessing that it must be a setting or option on the SQL Servers themselfs, something in its configuration as otherwise the strings are identical so there must be something in the way that one SQl server is not set up to allow connections from another?
I'm working through Ch 3 of "SQL Server 2005 Reporting Services Step by Step" by Stacia Misner, published by Microsoft Press, but I can't get the example report in Ch3 to deploy. I get a long error message, which says this:
TITLE: Microsoft Report Designer ------------------------------
A connection could not be made to the report server http://localhost/ReportServer.
Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'. The request failed with the error message: -- <html> <head> <title> SQL Server Reporting Services </title><meta name="Generator" content="Microsoft SQL Server Reporting Services 9.00.2047.00" /> <meta name="HTTP Status" content="500" /> <meta name="ProductLocaleID" content="9" /> <meta name="CountryLocaleID" content="1033" /> <meta name="StackTrace" content=" at Microsoft.ReportingServices.Diagnostics.RSConfiguration.Load() at Microsoft.ReportingServices.Diagnostics.RSConfiguration.Construct(String configFileName) at Microsoft.ReportingServices.Diagnostics.RSConfiguration..ctor(String configFileName, String location) at Microsoft.ReportingServices.Diagnostics.RSConfigurationManager..ctor(String configFileName, String configLocation) at Microsoft.ReportingServices.Library.Global.get_ConfigurationManager() at Microsoft.ReportingServices.WebServer.Global.StartApp() at Microsoft.ReportingServices.WebServer.Global.Application_BeginRequest(Object sender, EventArgs e)" /> <style> BODY {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE: 8pt; COLOR:black} H1 {FONT-FAMILY:Verdana; FONT-WEIGHT:700; FONT-SIZE:15pt} LI {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE:8pt; DISPLAY:inline} .ProductInfo {FONT-FAMILY:Verdana; FONT-WEIGHT:bold; FONT-SIZE: 8pt; COLOR:gray} A:link {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC; TEXT-DECORATION:none} A:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#FF3300; TEXT-DECORATION:underline} A:visited {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC; TEXT-DECORATION:none} A:visited:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; color:#FF3300; TEXT-DECORATION:underline}
</style> </head><body bgcolor="white"> <h1> Reporting Services Error<hr width="100%" size="1" color="silver" /> </h1><ul> <li>The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError) </li><ul> <li>Access to the path 'C:Program FilesMicrosoft SQL ServerMSSQL.3Reporting ServicesReportServerRSReportServer.config' is denied.</li> </ul> </ul><hr width="100%" size="1" color="silver" /><span class="ProductInfo">SQL Server Reporting Services</span> </body> </html> --. (Microsoft.ReportingServices.Designer)
I'm attempting to deploy CLR Stored Procedures from Visual Studio 2005.
I have a VS Database project with stored procedures for all of the tables in our database. (I would really like to keep everything together in 1 DLL), everything seems fine except...
I keep receiving the following error when attempting to deploy to SQL Server:
Error 1 Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
After some experimentation I have determined that its because the DLL is too large: 1.8 mb. (I also have a larger one).
I have looked through various documentation sources but have found none concerning this problem other than specifing something aboug a 100ms execution timeout (not sure if this is the same).
Deployment works if I trim down the size of the DLL (i.e., remove procedures from the solution)
Is there anyway to deploy large DLLs to SQL Server without having to break them up? If so, where is the setting to allow a longer timeout period for deployment?
Have my first .NET app deployed to remote host and configured successfully, except for one thing: can't figure out how to export my SSE tables to the SQL server database on the remote server. I tried SQL Server Management Studio Express ... with that, I can access the remote database, but can't access the local database file I produced with VSWDE. What is the appropriate tool to use to export tables from a local SSE database file to a remote SQL Server 2005?
I am trying to add membership to my site. i use visual web developer and the set controls. i.e. login etc. I also used the asp web config tool which is where my test users are. Everything works locally. but when i upload it and try to log on I get this error message: Server Error in '/' Application.
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.SqlClient.SqlException: 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:
[SqlException (0x80131904): 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +735043 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +820 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84 System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197 System.Web.Security.SqlMembershipProvider.GetPasswordWithFormat(String username, Boolean updateLastLoginActivityDate, Int32& status, String& password, Int32& passwordFormat, String& passwordSalt, Int32& failedPasswordAttemptCount, Int32& failedPasswordAnswerAttemptCount, Boolean& isApproved, DateTime& lastLoginDate, DateTime& lastActivityDate) +1121 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved, String& salt, Int32& passwordFormat) +105 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved) +42 System.Web.Security.SqlMembershipProvider.ValidateUser(String username, String password) +83 System.Web.UI.WebControls.Login.OnAuthenticate(AuthenticateEventArgs e) +160 System.Web.UI.WebControls.Login.AttemptLogin() +105 System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e) +99 System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +35 System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) +115 System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +163 System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5102 Can anyone out ther please help me with this. thanksNick
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210
I have a dev machine with VS2005Pro, WinXPSP2. I create a web site with authentication built with the ASP.Net Configuration Tool in VS2005.
The site, login and all other functionality are fine when tested on the dev machine.
I use copy web site to 'deploy' the site to a W2003R2 server. The authentication process doesn't recognize the password. All other web functionality is fine. With SSMSE I can see that the request is actually being processed by SS2005E.
Is this likely to be an encryption problem due to differing machine keys or something similar? What is the recommended approach to moving ASPNETDB from the dev machine to a server?
Hi. I created an app on my laptop and wish to deploy it to a server. I followed the steps to release the project and I copied the files over to the server. I'm getting an access denied or server does not exist error message. I went into the code behind pages to change the connection string but it still doesn't work. I think it has something to do with the SQL Server name. It's just local. The person that installed it did not change the name. In enterprise manager, it looks like this. (local) (Windows NT) Should the connection string be SERVER/(local) ? Is there a default name I'm not aware of? Any help would be greatly appreciated. Thanks!
Here is the error message:
Server Error in '/' Application. --------------------------------------------------------------------------------
SQL Server does not exist or access denied. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
hi everyone. i've recently upgraded to ASP.NET 2.0 and have successfully created a web application using the 2.0 membership provider. everything is working GREAT... ...until it's time to deploy! for the past 2 days i have been stuck trying to figure out why my app cannot connect to my SQL Server 2005 database. i am plagued by the: "login failed for user 'NT AUTHORITY/NETWORK SERVICE'" error. the database is aspnetdb.mdf located in the app_data folder of my web application. the "LocalSqlServer" connection string name is used for connecting to the database (using the "attach" menthod steps taken so far: installed vs2005 on the target server, opened the project, connected to the database and added the "NT AUTHORITY/NETWORK SERVICE" user as a db owner to the aspnetdb.mdf database installed SQL Server 2005 Management Studio Express to try to accomplish the same thing as through vs2005 gave the NT AUTHORITY/NETWORK SERVICE account full access to the folder where the web application resides. attempted to create a custom connection string to attach the database and connect using an SQL user instead of a windows user, but "attaching" an MDF file seems to only work with integrated security. attempted to attach the database using the Management Studio Express and added a SQL user as the db owner. but SQL can't find the database even when it's attached. i've deleted, rebooted, uninstalled, reinstalled, recopied, etc. several times with no luck. one thing that i find very peculiar: on the target server, when i open the WSAT through vs2005 it shows 0 users, even though there ARE some in the database when i run the app on in development environment. in this situation, i try to log in to the application and the login page returns a "user not found" error. after returning to the WSAT and creating a new user, i try to log in again and get login failed for NT AUTHORITY/NETWORK SERVICE again. can someone PLEASE help me. it just doesn't seem like it should be this difficult. the new membership provider in 2.0 is really easy to use...how could it be so difficult to deploy?? PLEASE PLEASE PLEASE help. thanks in advance!
I hv developed a client server application that uses Access Xp ( adp file) as front end and SQL Server 2000 as database. Inside the vba code i hv extensively made use of sql dmo library objects. For the program to work properly i am forced to install Sql server client tools especially (enterprise manager) on end users workstation which is something i am not happy with. Whithout SQL client tools installed Access pops up an error like "Can't create activex object".
I googled that issue and gathered informations stating that some dll's file must be installed for SQL dmo to work smoothly in a VB application and i guess that same also stands for Access vba since they are almost quiet the same.
In my application setup package i hv included these below dll's and they hv been set to be loaded in application directory as following but the problem still remains.
I have inherited a deployment running inside a custom .net application. I'm looking to deploy an updated version of a report to the report server. My question is there a manual way of deploying an RDL? I'm afraid of taking down the application entirely and I do not have detailed enough documentation to bring it back up. Thanks!
Is there a way that would allow me to deploy ssis for end user in a given file, where the end user simply clicks some icon that will tiger the ssis deployment process?
Hi All, I am able to execute my ssis package from BID environment using SQL Server Authentication. However, when I deploy the package on SQL Serve 2005 using Windows Authentication, the package fails. The package is a simple one, it read two servers, truncate tables and load the data on the destination server.
I am not sure why this fails when I execute the package on the server environment, but works fine when I run it from BID.
I have a SSIS package on my local machine, and would like to deploy it to DEV server. Which files should i be moving to the SQL DEV Server? and where? How do I modify connection managers or is there a way to do that from the Management Studio or some other way? Thanks and I would definitely appreciate some prompt advise.
I am looking at deploying some ssis package's as files, my question can I install just integreation services on on server to run the packages or do I need the full installation of sql server 2005
A report runs well in Visual Studio environment. Once it is deployed to the local report server, got an #Error indication without an actual message. The report has an embedded code with a database connection in it. Any idea what the problem is?
I am considering the different options for package deployment on the server. Until now, I have found several different ways to deploy packages to the server (File System):
Using the Import option from the Management Studio (only one by one) Using the Deployment Utility (Needs building the whole project. Opens all the packages in debugging mode, cannot deploy to different folders) Using the dtutil by constructing a command line for each package deployment. (complicated) Simply copying the files from the local project folder to the "Program FilesMicrosoft SQL Server90DTSPackages" folder on the server.
Does anyone have any other suggestions for deployment? The 4th seems to be the easiest one, but I seen anybody suggesting such an action. What's the downside of such an action?
I have a report project I have deployed onto a remote Reporting Services server several times smoothly and easily. Recently I logged into the site in IE to test the reports using a username and password with MUCH lower security than my own. Since then I cannot deploy reports. I get a message that "The permissions granted to 'domainLoser' are insufficient for performing this operation." This is as it should be. Loser should NOT be able to deploy reports. The problem is I can't get it back to being me, the admin. I have reported, opened the reports in IE using my own login, reopened VS2005, tried setting IE to require authentication to force a login again, and then rebooted again.
Does anyone have a suggestion about how to correct this? Had I known I would NEVER had tested this on the same PC I was deploying from. I seem forever stuck as Loser now.
Thanks for any suggestions or questions for clarification. Eva
I'm trying to deploy an application that runs DTS packages from the local machine.
I've read some articles that it would be enough to install the SQL Client Tools on the local machine to make the DTS work . I did this, the package executes a few steps (it shows message boxes and writes data into the database), then (before executing some validation tasks on the data) it throws an exception 'Execution was canceled by user'. I've set the pbCancel flag and the package runs fine on some computers, but on an empty system that only contains my application and the Sql Client Tools I get this exception.
Do I have to install anything else or do I have to make some changes to DTS package to make it work?
I am trying to deploy the reports from my PC to the server but getting different kinds of errors. Here is what I have done- 1- In Visual studio added the proxy using web reference - http://myserver/reportserver/reportexecution2005.asmx 2- I have added the class - ReportingService2005.cs in my project. 3 - When I call the 'CreateReport' passing all the parameters it sometimes says "Client found response content type of ", but expected 'text/xml'. The request failed with an empty response" or sometimes "access to the path C: eportfolder is denied"
Not sure if I really have the correct forum for this posting so appologies if it is not. My question refers to the basic functionality of the new Sharepoint 3.0 both WSS and MOSS.
In version 2.0 of Sharepoint Services reports were displayed in Sharepoint using Report Explored to navigate and Report Viewer to display the report. Also KPI's were displayed in a web part which came from Business Scorecard Manager 2005.
I have been investingation both WSS3.0 and MOSS and have installed WSS3.0 to test. I notice that I can connect to reporting services with CTP2.0 for sql server. I can upload reports into document lists and run them from there. My question is has the old idea of using the report explorer gone as when you have report manager running in sharepoint integration it has no website to upload files or manage permissions. Is the document upload method the new way or am I missing something.
More importantly though is the display of KPI's is this now only available in MOSS 2007 and no longer a function of WSS3.0 as you cannot install Business Scorecard manager on WSS3.0 but it appears this is built in to MOSS.
Any guidelines to this new functionality would be greatly appreciated
I am doing SQL Server deployment of multiple SSIS projects. 2 of the projects have dtsx files that are named the same. Is there anyway to deploy to SQL Server to put these in different projects so that they dont conflict?
I have created a report which contains a sub report.But the problem is when i deployed my rdl in my report server,my sub report wont show : "Error SubReport could not be shown".
But still,when i also deployed my sub report for that main report,still, it wont show.. what could be the reason for this?? Thanks...
Error 1 Deployment and/or registration failed with error: 0x8973190e. Error writing file '%CSIDL_PROGRAM_FILES%PDAPDADB.sdf'. Error 0x80070020: The process cannot access the file because it is being used by another process. Device Connectivity Component
Hi I get this error when I try and deploy the emulator but it only happens when I run the database on the emulator it works fine before I do this. I run the database just to see if the database gets populated. Does anyone know how to solve this problem.
