When running the GUI client, I chose to install the SQL Server 2005 'Client Components' on F:Program FilesMicrosoft SQL Server, the installation put over 700MB of files on my C: drive, but there were less than 400MB of files in the location I specified. Only about 1/2 of the files I expected were put in the location I specified.
Why?
How can I redirect all of the 'shared' files and other misc. development pieces to install somewhere other than my boot drive? There is no way to specify this when using the GUI, can it be done with a command line install?
Is it possible to force the SLQ 2005 Client Components to be installed into a diffrent location other than the default location?
What I'm trying to do is run the setup command though the command line to create an unattended client installation with all the client componets to a diffrent location that
Thanks, Any information or examples would be great!
I have a question about client components. I read someplace where if sql client components are preinstalled (if you delete sql express-client components cannot install, even if they are preinstalled
I have sql express default installation from vs 2008 pro I have not installed sql express (client components, database components I wish to install cd standard edition on my computer for reporting services Also wanted to add enterprise server so I need report manager office 2007 installed by myself. I came across this article kb909967. Is there anyway to check make sure I can install client components installs on standard edition I also read kb 964164 installing sql on vs 2008 vista ultimate Thanks
In my SSIS project, i have to retrieve data from an oracle 10g database. On my personal laptop it works, but on our test-env i get the error below, when i try to test my connection to the oracle datasource.
Could this because i have oracle XE installed yet on my personal laptop, and it is not installed on the computer of our test environment where the SSIS runs? If that's the reason, it sounds very strange, because it would mean i have to install an oracle environment also on the computer with SSIS, just to make a connection to another oracle server...
Test connection failed because of an error in initializing provider. Oracle client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3.3 or later client software installation.
Provider is unable to function until these components are installed.
I'm trying to do an unattended install of the client components for SLQ2005. I have read the document on doing a install from the command prompt but when I use the "ADDLOCAL" switches I get some components that I don't require. For example, I am using the following command to run the setup - "start /wait <path>setup.exe ADDLOCAL=Client_Components,SQL_Tools90,Connectivity". When I look at the Add/Remove Programs list I can see that it has installed "MSXML 6.0 Parser", "SQL 2005 Backward Compatibilty" and "Office 2003 Web Components". The only components I require are the "SQL Support Files", "SQL Server Native Client" and " CLient Tools". If I run "start /wait <path>setup.exe REMOVE=SQLXML,TOOLS_BC_DEP" it will remove "Office 2003 Web Components" and "SQL 2005 Backward Compatibilty" but not the "MSXML 6.0 Parser". How can I get rid of this?
I'm building a new server and am having a problem witht he SQL install. It's a Dell 2905 running Windows 2003 SP1 x64 and SQL 2005 x64. I'm able to install everything except for the Client Components, and even upgrade to SQL SP2.
I keep getting the following error:
"There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information" TITLE: Microsoft SQL Server 2005 Setup ------------------------------ There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=50000&EvtType=packageengine%5cinstallpackageaction.cpp%40InstallToolsAction.10%40sqls%3a%3aInstallPackageAction%3a%3aperform%400x643 ------------------------------ BUTTONS: OK ------------------------------
The problem is that I can't find any solutions to this so far. Anyone recognize or have any insight into this?
I have SQL Server 2005 installed on a machine that was recently upgraded to SP2 (build 3042). The server never had the replication feature installed on it. I attempt to add replication to it and I get an error because (I think) I am installing from the initial version media (CD-ROM, build 1399) and the setup appears to want an MSI file for SP2. Any help is appreciated.
I followed the exact procedures in online help How to: Change Components in an Existing Instance of SQL Server 2005 (Setup), but after I get the Ready to Update page, I get the error box:
An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package €˜SqlRun_SQL.msi€™.
Here is a partial output of the SQLSetupxxxx_ComputerName_Core.log file:
Action 17:44:25: ResolveSource. Action start 17:44:25: ResolveSource. MSI (c) (E4!D4) [17:44:25:200]: Resolving source. MSI (c) (E4!D4) [17:44:25:200]: User policy value 'SearchOrder' is 'nmu' MSI (c) (E4!D4) [17:44:25:200]: User policy value 'DisableMedia' is 0 MSI (c) (E4!D4) [17:44:25:200]: Machine policy value 'AllowLockdownMedia' is 0 MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Media enabled only if package is safe. MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Looking for sourcelist for product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C} MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Adding {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}; to potential sourcelist list (pcode;disk;relpath). MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C} MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Media is enabled for product. MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Attempting to use LastUsedSource from source list. MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing net source list. MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNNet 3: 2 MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing media source list. MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Trying media source H:ServersSetup. MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 2203 2: H:ServersSetupSqlRun_SQL.msi 3: -2147287037 MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Source is invalid due to missing/inaccessible package. MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing URL source list. MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNURL 3: 2 MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi MSI (c) (E4:7C) [17:44:25:200]: User policy value 'SearchOrder' is 'nmu' MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Media enabled only if package is safe. MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Prompting user for a valid source. MSI (c) (E4:7C) [17:44:25:200]: Machine policy value 'DisableBrowse' is 0 MSI (c) (E4:7C) [17:44:25:200]: Machine policy value 'AllowLockdownBrowse' is 0 MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Browsing is enabled. MSI (c) (E4:7C) [17:44:25:200]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C} MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Media is enabled for product. MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Attempting to use LastUsedSource from source list. MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing net source list. MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNNet 3: 2 MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing media source list. MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Trying media source SQLSTDSEL;. MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing URL source list. MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNURL 3: 2 MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi MSI (c) (E4:7C) [17:44:44:388]: SOURCEMGMT: Trying source H:SetupSqlRun_SQL.msi. MSI (c) (E4:7C) [17:44:44:388]: Cloaking enabled. MSI (c) (E4:7C) [17:44:44:388]: Attempting to enable all disabled priveleges before calling Install on Server MSI (c) (E4:7C) [17:44:44:403]: SOURCEMGMT: Resolved source to: 'H:Setup' MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C} MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Media is enabled for product. MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Attempting to use LastUsedSource from source list. MSI (c) (E4!D4) [17:44:44:403]: Note: 1: 1706 2: 3: SqlRun_SQL.msi MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Failed to resolve source MSI (c) (E4!D4) [17:44:44:419]: Transforming table Error.
MSI (c) (E4:7C) [17:44:44:450]: Note: 1: 2262 2: Binary 3: -2147287038 Error 1706. An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package 'SqlRun_SQL.msi'. MSI (c) (E4!D4) [17:45:02:731]: Transforming table Error.
MSI (c) (E4!D4) [17:45:02:747]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (E4!D4) [17:45:02:747]: Product: Microsoft SQL Server 2005 -- Error 1706. An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package 'SqlRun_SQL.msi'.
When attempting to install SQL Server 2005 SP1, I receive the error, "a recently applied update, KB913090, failed to install." The Installation complete dialog shows the Client Components product Status as "Failure" with the description detail, "Unable to install Windows Installer MSP file". My Operating System is Windows Server 2003 SP1.
If you enter "Create Database test", the database files (mdf file & log file) are created, by default, in:- C:Program FilesMicrosoft SQL ServerMSSQLData I want to change that to:- D:Database Files I sucessfully moved the model database to this location (using the instructions in BOL) assuming that all new databases would now get created in the same location, but they don't. They still get created in: C:Program FilesMicrosoft SQL ServerMSSQLData
So how do I change the default? (It's not satisfactory to have to move each database after it's created)
We are running SQL Server 2000 w SP4 on a 2 node active/passive Windows 2003 w SP1 configuration. We are presented with 2 150GB LUNs and 1 600MB on particular SAN that does not belong to us. M: and N: drives are the datadrives and Q: is the quorum.
We now have our own SAN and we will be using it for the SQL cluster data storage. The SAN administrator stated that he will present me with 2 150GB LUNs and 1 600MB…pretty much the same configuration.
How will I be able to move all my data and configure the cluster to the new SAN?
I am trying to create a proof of concept to show that we can have packages deployed on 3 different servers and all we need to do is tell the package, upon execution/scheduled task, where to go fetch it's configurations from.
The configurations are using SQL Server as the package configuration. This makes it easier for DBA's to maintain since DBA's are responsible for package executions and job scheduling.
For example, the configuration database and all package configurations would be found on server1, server2 and server3 The difference in values is that on Server1, the configuration for the source data and the destination data point to Server1DatabaseSource and Server1DatabaseDestination and on server2, the configs point the source to Server2DatabaseSource and Server2DatabaseDestination and for server 3, the same thing but pointing to server3.
There is also a connection for the SSIS_Config database we're getting the configurations from. In theory, if we specify a different server where this SSIS_Config database is found, it should override the settings in the package. No?
When I schedule OR execute the package, it's always getting it's configs from the config specified in the package independent of wether I specify it in the Connection Managers of the Execute Package Utility when I manually execute it OR in the data sources tab when I configure the package to be run as a job in SQL Server 2005.
Whenever I make a breaking change to a custom SSIS component/tasks and update the Assembly Version, it seems to break my packages beyond repair, telling me it can't load the task:
Error loading Package1.dtsx: Error loading a task. The contact information for the task is "". This happens when loading a task fails.
All of the properties of said task now show:
Could not get value for property 'c-155-designer-name'. Specified cast is not valid.
Typically, a "breaking" change when it comes to code just means that you need to update your components to adhere to the new contract of the updated signatures. But with SSIS, it seems the only solution to this is to completely remove the component, and re-add the new version, and re-enter all of the property values/expressions. If I have a package containing 10 instances of a task that only had one property removed, for example, this results in a very time-consuming process of fixing my package.
So my questions:
1) Am I doing something wrong in my versioning/deployment that is causing my packages to unnecessarily break?
2) If this is just "by design" and the way it's meant to behave, what is the best practice for making breaking changes to custom tasks/components used by many packages? Should I just never change the assembly version, even when it is a breaking change (this seems to be less disastrous)?
3) As a last resort, if I'm stuck with having to fix the broken tasks, is there a better way to fix them rather than having to completely remove them, re-add them, and re-set all of their properties/expressions?
I have installed my modell database onto c:mssql7data...
How do I now change the properties of this so that when someone creates a database, the path it will get created to is set to d: I thought that I could just move model, but it seems that this isn't possible.
When SQLserver2K was installed it placed master, model, msdb, tempdb data files in the installation location (i.e. C:Program Files....). This puts pressure on the C: drive, which also holds the page/swapfile. I want to move at least the tempdb location to the new 'Default data directory' and log directory we set after installation (i.e. E:MSSQLData).
How do I get tempdb to relocate to E: given that it gets recreated each time SQLserver starts?
changing master database location in sql server 2000
HELLO PLEASE HELP ME I AM TRYING TO CHANGE THE LOCATION OF MASTER DATABASE ( MDF AND LDF ) AND ERRORLOG FILES I HAVE TRIED EDITING STARTUP PARAMETERS IN ENTERPRISE MANAGER I FAILED ,I TRIED IN COMMAND PROMPT "SQLSERVR.EXE " I SUCCEEDED IN CHANGING THE DATA FILE AND ERROR LOG BUT UNABLE TO CHANGE THE LOG FILE PATH FROM DEFAULT LOCATION C:PROGRAM ............ TO D:DATA PLEASE GIVE ME THE PROCESS TO CHANGE DATA ,LOG AND ERROR LOG FILES of master database thanq in advance
I have Windows XP Professional Version 2002 Service Pack2.
I Have:
Microsoft SQL Server Management Studio 9.00.2047.00 Microsoft Analysis Services Client Tools 2005.090.2047.00 Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158) Microsoft MSXML 2.6 3.0 5.0 6.0 Microsoft Internet Explorer 7.0.5730.11 Microsoft .NET Framework 2.0.50727.42 Operating System 5.1.2600
Service Pack is failing to Install CLIENT COMPONENTS; message is:
Product : Client Components Product Version (Previous): 2047 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log Error Number : 29549 Error Description : MSP Error: 29549 Failed to install and configure assemblies c:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2147024894 Error message: The system cannot find the file specified. Error description: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
This situation, I am guessing, also preventing me to run import/export from the SQLServer Client.
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 have downloaded Microsoft SQL Server 2005 Enterprise Evaluation Edition ISO from the following site and burned it onto a DVD. http://www.microsoft.com/downloads/details.aspx?FamilyId=6931FA7F-C094-49A2-A050-2D07993566EC&displaylang=en
Prior to this I have installed Visual Studio 2005 Professional Edtion. During setup I have selected all the native client components i.e. Management Studio, Business Intelligense Studio. But after the install I am not able to see them under All Programs-> Microsoft SQL Server 2005. On further searching I have come across this link
First of all, there is no sqlrun_tools.msi under setup folder of the dvd. And also when I tried to change component from Add/Remove programs and following the instructions as specified on clicking Change Installed components all that I see are: Connectivity Components and Software Development kit.
Could someone tell me how can I install Management Studio/ Business Intelligence Studio seperately? I don't want to go through the process of re-installation.
Everything I've read says that custom data flow components are built by inheriting from the Microsoft.SqlServer.Dts.Pipeline.PipelineComponent class.
But the stock components such as the Derived Column data flow transformation must each be implemented by their own class. So how do I base my custom components on those classes? The documentation for the PipelineComponent class doesn't list any such subclasses.
In another thread Jamie Thomson very informatively said "The components in SSIS are deliberately atomic (i.e. they do something very specific) so that its easy to put them together to build something greater than the sum of the parts". Which does make a lot of sense. However, I've been finding that I end up having to create exactly the same "pattern" of combined transform components again and again in order to solve the same problem but in different dataflows (or even within the same dataflow). Cut-and-paste-tastic! In order to obtain real re-use, it seems to me like SSIS is crying out for an easy way to create new components by using composition - i.e. the ability to take commonly-used combinations of existing components and create new "super" components (without having to write Custom Transform Components in C#/VB.Net and handle everything in code).
Does anyone know if this sort of functionality is likely to make it into SSIS in the forseeable future?
Product: Microsoft SQL Server 2005 -- Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
On Windows XP systems I get the following issue when trying to browse the MSDB folder in SSIS
Client unable to establish connection Encryption not supported on SQL Server. (Microsoft SQL Native Client)
I have noticed another post where several others have noticed the same issue. It appears to only occur on Windows XP installations. Is there a workaround or fix for this?
I have SQL2000 installed as the default instance, and now I'm trying to install SQL 2005 standard edition as a named instance.
I receive this error : SQL Server could not connect to database service for server configuration.. [SQL Native client] Encryption not supported on the client. However I'm able to install client tools
The setup works fine on other box with the same config : SQL 2000/Windows XP, is there any work around for this issue ?
In my SQL 2000 client network utilty "Force proctocol encryption " is desabled and did not find the setting for SQL 2005 !
Hello,Is it necessary to upgrade the Client Connectivity Tools on all clientmachines after the SQL Server database server is upgraded from Version7.0 to 2000?Thank you in advance!Eddy
I have tried this on several different operating systems (VISTA and XP ) and several versions of SQL NATIVE CLIENT including 2005.90.3042.0
I have a 64 bit "SQL NATIVE CLIENT" connection that fails. The exact same connection and code succeeds on 32 bit. My customer and I prepend "oledb:" to the connection string and it starts working.
FAILS on 64 bit: Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Wrigley_Test;Data Source=MONGO;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=RIPTIDE;Use Encryption for Data=False;Tag with column collation when possible=False;MARS Connection=False;DataTypeCompatibility=0;Trust Server Certificate=False
WORKS oledb:Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Wrigley_Test;Data Source=MONGO;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=RIPTIDE;Use Encryption for Data=False;Tag with column collation when possible=False;MARS Connection=False;DataTypeCompatibility=0;Trust Server Certificate=False
I debugged my code to the point that I know it is happening when I call CreateAccessor for my SQL statement.
I have a job that contains a step to run a DTS task (DTSRUN /S.....etc.) via a batch file.
I can run either the DTSRUN command line, or the batch file that contains it just fine, but when I try to run the job, it reports success but does not actually do the work.
I dont get an error message. I am using the sa account to run the DTS task from the command line.
I know this must be a permissions issue. As I am working at a Defense contractor, I cannot get a domain admin account to run SQL Agent.
Can any one give me brief useful explanations or guide me to a usefulresource of what Development Tools component and Profiler are?Is there anything I should be aware of if I want to install ClientConnectivity component (don't want to overwrite anything)?Thank you in advance.
I am not sure why when the packages are run, the components dissapear. The only thing I see is the result in the output. So there is no visual on the tabs. Thanks
