Hi all, Im new here so il start with a little introduction of myself, My name is Arjan im 19 years old from Holland, and i work for a company to compleet my ICT Education.
My situation:
My boss gave me a server with server 2003 standard and Sql server 2005 and visual studio 2005 installed already, he asked me if i could figure out how the 'new' reporting services work, Im pretty new to SQL and the reporting service but i figured out i had to install asp.net / frameworks and IIS.
So right now i wanna start the Reporting Services Configuration Manager and i get an error that says 'Invalid namespace' and when im trying to approach by using my browser i get 'page not found' so obviously their is Alot wrong. I asked my boss if i could not reinstall everything and do it in the correct order (IIS / ASP.net / Frameworks before installing SQL server 2k5 but that was not an option because we dont seem to have the cd's anymore.
The server is not connected to any network or the internet.
My Question:
Is their any way to fix this? and if yes could anyone tell me where to start
Thanks in Advance!
ps if their is information or logs that u need in order to help me just say so :-)
Ok, I created SSIS packages on my local box. All of my packages are using config files for the db connections and other configurations that'll be changed per environment. My question is how do I deploy the .dstx file and the associated config file to the servers?
Right now I'm running the packages in BIDS as I create them. I now want to run them on an actual server
What are the minimum permissions required to deploy an SSIS package to SQL Server? Here is what I have tried:
1. No additional permissions (i.e user created with no special permissions):
Deployment Error: No execute permissions on sp_put_package???
2. Dbowner role on msdb dataabase
Deployment Error: The SaveToSQLServer method has encountered OLE DB error code 0x80040E14 (Access to Integration Services package 'xxx' is denied.). The SQL statement that was issued has failed.
3. Sqladmin role on login: No errors
Most DBAs are reluctant to give sqladmin role to developers. Is there any way around this restriction?
I have a SSIS package, which get data from oracle 9i, and dump into sql server 2005 64bit itanium, its running fine. When I am deploying the package on SQL Server 2005 its showing me the error with connection. on 64bit Oracle Net manager showing its able to connect oracle successfully. I think actually the problem is with encryption, as the package is developed on 32bit machine, therefore all connection strings are encrypted for that machine. Is there some has faced same issue? please help!
I have just installed SP2 on our server and this has caused a number of SSIS packages containing encripted data (SFTP tasks purchased from /nsoftware) to stop working. When executing them from business development studio they work fine, but when I install them into the server I get this error "The Validate method on the task failed, and returned error code 0x80131500 (You must specify an SSH host.). The Validate method must succeed and indicate the result using an "out" parameter." The SSH host is specified correctly in all tasks, because as I said I can run them from the development studio without any error. Does anyone have a clue on how to resolve this? Thank you in advance.
I restored a backup from SQL 2000 onto a new SQL 2005 server. The database restored and the matching user who was the owner of that database in SQL 2000 was created as a user in SQL 2005 as well as being designated as the "schema" for that database. I was having trouble logging in with the user that was created after the restore, so I created a new user and assinged the new user as DBO of the new database, set up the new users default database and schema, and everything was working fine, my database driven application worked perfectly under that user.
Then I installed SSIS, as it was recomended as a solution to another problem. After installing SSIS I can not run queries without specifying a schema name. For example this query will not work, it returns table not found:
SELECT * FROM <table_name>
However if I specify the schema name like this, the results return:
SELECT * FROM <schema>.<table_name>
This screws up my database application as it does not include the schema name in its transactions.
I do not understand why installing SSIS would have changed this.
I built a SSIS(writing out to a flat file ) in 32 bit machine and it woks fine . But however when I deploy to the produciton server(64 bit) the SSIS writes out garbage data . After some research I found out that the problem with the 32 bit OS and 64 bit OS problem.What is my next step. Am I out of luck that now I will have to redesing the SSIS in 64 bit?
Something a little wride mysterious is happening with my package when I deploy it to run at the SSIS server instance. Everytime that I try to deploy it (from my local development environment) to SSIS server, my package is not keeping its database user and password.
As the database user and password are the same one we dont need to use the XML setting to keep these data there.
So, does anyone know what could be happening with my package and/or my deployment?
We would like to deploy SSIS packages as an ETL Tool to an appserver that does not have SQL Server 2005 installed. Is this possible, or does it HAVE to be executed on the server with SQL 2005 installed?
As we know Sql Server 2005 provides its ability to deploy clr assembly on it. However my problem is that my assembly has a configuration file. I used ConfigurationManager.GetSection to create some of the object. When I am deploying the project the trouble is that the app.config is missing. I used a class lib project type to create the assembly. Besides changing a storing method, can I still use this config file to reach my goal? Sqlserver.exe.config is not a good idea and it is not workable. The sqlserverexe host cannot find the assembly files.
Hi, when deploying assembly from VS into SQL Server 2005, deployment fails with these error messages:
Msg 0, Level 11, State 0, Line 0 A severe error occurred on the current command. The results, if any, should be discarded. Msg 0, Level 20, State 0, Line 0 A severe error occurred on the current command. The results, if any, should be discarded.
I'm deploying assembly with UNSAFE permission setting. What's wrong, please?
I need to install the SSIS components on the referenced database server. I believe the SSIS components are cluster aware, so I was planning on just doing add/remove and selecting the components. Rather than breaking the cluster apart to patch the components back to SP1, I was thinking of just running the SP2 install right over the top of the running cluster to bring everything up to SP2.
I'm looking for any suggestions/comments on whether this is the proper way to proceed or if I'm going to have a problem.
Today, I download SQL Server 2005 Business Intelligence Metadata Samples Toolkit from Microsoft download center, per readme.txt instructions, build the project, but there was an error as below:
Error 1 The project could not be deployed to the 'localhost' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server. 0 0
After then, I just build the project,but didn't deploy it, then I try to launch DependencyAnalyzer console application, there was also an there:
Error occurred: A connection cannot be made. Ensure that the server is running.
I have installed SSIS on server running SQL 2000 but I don't see the Business Intelligence or SSIS. I could see the SSIS service is running but do not see VS or BI version of VS.
Hi, I am running SQL Server 2005 x64 DE on Vista x64. I installed MS VS 2005 Pro. Edition. During the setup of VS, I did a custom install, un-checking the SQL Express addition box. After installation, I received errors that indicated the SQL Express did not install. Even though I do not have SQL Express installed on my machine, MS Update says that I need SQL Express SP2. My SQL DE is up to date with SP2 and MS Update indicates as "optional" that I need SQL SP2.
Is SQL Express a necessity for VS Pro? If not, why is MS Update indicating that I need SQL Express SP2? In addition, why is MS Update telling me I need SQL SP2 when it is already installed?
Note: I installed SQL SP2 manually, not through MS Update. This makes me believe that MS Update is not detecting it.
I need to install SQL Server 2005 Standard Edition on a new Windows Server 2003 machine that has SQL Server 2005 Express Edition installed by a backup application (Backup Exec). Will I need to uninstall the express edition in order to install the standard edition? Can the two coexist as separate instances or will the standard edition installation simply upgrade the express installation?
I installed sql server 2005 sp2 including business intelligence development suite , however I got a message some client components not compablitable .This morning I searched my programs and found that I have new visual studio 2005 on my computer (before I just had vs 2008) as well as business intelligence developer (which does not work) It seems I I would like to get rid of vs 2005 also fix business intelligence studio . Previously I deleted vs 2005 express off my computer........(I have vista and I would only like to keep tools meant for sql standard 2005 reporting services etc here is a list of my sql sp2 install package By the way I doubled clicked sql_tools.msi and did not run as administrator Does that make a difference? I wonder if this is a problem with vs 2008 and sql 2005......
Time: 05/06/2008 20:49:23.437 KB Number: KB921896 Machine: BILLPREC690 OS Version: Professional (Build 6000) Package Language: 1033 (ENU) Package Platform: x86 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: Cluster Installation: No
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Products Detected Language Level Patch Level Platform Edition Setup Support Files ENU 9.00.1399.06 x86 Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x86 STANDARD Analysis Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x86 STANDARD Reporting Services (MSSQLSERVER) ENU RTM 9.00.1399.00 x86 STANDARD Notification Services ENU RTM 9.00.1399.00 x86 STANDARD Integration Services ENU RTM 9.00.1399.00 x86 STANDARD SQL Server Native Client ENU 9.00.3042.00 x86 Client Components ENU RTM 9.00.1399.06 x86 STANDARD SQLXML4 ENU 9.00.1399.06 x86 Backward Compatibility ENU 8.05.1054 x86 Microsoft SQL Server VSS Writer ENU 9.00.1399.06 x86
********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID SQLWriter Microsoft SQL Server VSS Writer Service 2700
********************************************************************************** Product Installation Status Product : Setup Support Files Product Version (Previous): 1399 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlSupport.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Database Services (MSSQLSERVER) Product Version (Previous): 1399 Product Version (Final) : 3042 Status : Reboot Required Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 3010 Error Description : ---------------------------------------------------------------------------------- Product : Analysis Services (MSSQLSERVER) Product Version (Previous): 1399 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixOLAP9_Hotfix_KB921896_sqlrun_as.msp.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Reporting Services (MSSQLSERVER) Product Version (Previous): 1399 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRS9_Hotfix_KB921896_sqlrun_rs.msp.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Notification Services Product Version (Previous): 1399 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixNS9_Hotfix_KB921896_sqlrun_ns.msp.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Integration Services Product Version (Previous): 1399 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixDTS9_Hotfix_KB921896_sqlrun_dts.msp.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : SQL Server Native Client Product Version (Previous): 3042 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_sqlncli.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Client Components Product Version (Previous): 1399 Product Version (Final) : 3042 Status : Reboot Required Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log Error Number : 3010 Error Description : ---------------------------------------------------------------------------------- Product : SQLXML4 Product Version (Previous): 1399 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_sqlxml4.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Backward Compatibility Product Version (Previous): 1054 Product Version (Final) : 2004 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SQLServer2005_BC.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Microsoft SQL Server VSS Writer Product Version (Previous): 1399 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlWriter.msi.log Error Number : 0 Error Description : ----------------------------------------------------------------------------------
I have installed integration service on a SQL Server 2005 development server and could not start the service. Windows Server 2003 Standard Edtion (SP2) + SQL Server 2005 Developer Edition (SP2) are installed on the server. When trying to start the service from SQL Server configuration tool or directly from service, got message saying that the service did not start in a timely fashion. Nothing is logged to event log.
Found this this kb. http://support.microsoft.com/kb/918644 The problem description is similar but not sure whether it is the same problem.
I have 9 Dimensions and 16 Fact Packages in my SSIS Project. All these 25 packages uses one source (SQLServer A - staging) and a seperate destination (SQlServer B - Warehouse) . I have completed my development. Now i want to move these packages to production environment. I have a Parent package to control all these facts and Dimensions.
1. Should I always change the Protection level of the Package to "DontSaveSensitive" before moving to some other machine where it has to run under a different user?
2. Which is the best way to follow for configuring the connection strings in my development? Having a variable for each connection string @ parent project level and pass it to child packages or Configure the connection strings directly in a XML config file for one package and in all my other packages i have to say the package to Reuse the existing config file as the source and dest is same for all these packages?
And am hearing one more buzz word "Proxies for running SSIS packages". Any information on this also will help me.
I need to install SQL server 2005 in my desktop. I have already installed Visual Studio 2005 and selected to install all add ons during initial installation of VS 2005.
Now, when i inserted my CD for installing SQL server 2005, there is nothing that has to be installed.
I checked that SQL 2005 Express edition is already installed in my system.
Kindly let me know, if by installing VS 2005 with all add ons will install SQL server 2005 as well?
I need to install SQL server 2005 in my desktop. I have already installed Visual Studio 2005 and selected to install all add ons during initial installation of VS 2005.
Now, when i inserted my CD for installing SQL server 2005, there is nothing that has to be installed.
I checked that SQL 2005 Express edition is already installed in my system.
Kindly let me know, if by installing VS 2005 with all add ons will install SQL server 2005 as well?
I was wondering if anyone might be able to help me. I was trying to run SQL Server 2005 express edition after downloading it from the internet. I must admit i'm new to SQL server. So this is why i like to get a feel of how it works and that sort of things. However, when i tried to run it, it's saying that i needed .Net Framework 2. Then, after having downloaded the .Net and run the setup, the error message came up with the following message.
"Error creating process <c:Documen~1userslocals~1 empixp000.TMPInstall.exe>. Reason: c:windowssystem32advpack.dll"
It still gives me the same error message after updating the advpack.dll i got from the internet.
Has anyone had the same experience as i've been having now?
I have a problem. I downloaded SQL server 2005 "standard or develope" trial version, which did not install on my computer. Probably not working on my OS. So the trial version did not work. Could someone please give me a clue which version that would work??
My OS an SP-level is; Windows XP Professional Version 5.1 (Build 2600.xpsp_sp2_gdr.050301-1519: Service Pack 2)
(Windows XP Professional version 2002 32-bit, Windows XP Service Pack 2, IIS, .NET Framework 2.0., 13GB free space, processor intel 1,5 GHz, 256MB RAM)
I am trying to install SQL Server 2005 on XP with SP2. According to Microsoft this should be sufficient. However when I try to install it says I need WIndows Installer 3.1. I cannot get this from Microsofts website as i'm not using a proper copy of XP.
Does anyone know a way round this before I go and buy XP?
This is the file I need...
WindowsInstaller-KB893803-x86.exe
To complicate matters further i'm running XP on my Mac via Virtual PC (but i'm told this shouldn't matter)