Will FTP And File System Tasks Run In Workgroup Edition?
Feb 1, 2007
I have a package that does an FTP and some File System Tasks. It runs perfectly fine in BIDS but doesn't want to run via SQL Agent. Is the SQL Server Edition the problem?
I'd like to upgrade from my current SQL Server version: 09.00.3042 (Workgroup edition that comes with SBS upgrade) to the standard edition that I've just purchased. I've attempted to run setup.exe SKUUPGRADE=1 from the command prompt and it just tells me that there's nothing new to install.
I don't really want to uninstall the current installation just to do something that shouldn't be complicated to do, upgrading software versions should not be a difficult process.
I've run into a problem with SSIS packages wherein tasks that write or copy files, or create or delete directories, quit execution without any hint of an error nor a failure message, when called from an ASP.NET 2.0 application running on any other machine than the one where the package was created from. By all indications it appeared to be an identity/permissions problem.
Our application involves a separate web server and database server. Both have SQL Server 2005 installed, but the application server originally only had Integration services. The packages are file system-deployed on the application server, and are called using Microsoft.SqlServer.Dts.Runtime methods. For all packages that involve file system tasks, the above problem occurs.
When the above packages are run using the command prompt (either DTEXEC or DTEXECUI) the packages execute just fine. This is expected since we are using an administrative account. However when a ShellExecute of the same command is called from ASP.NET, the same problem occurs.
I've tried giving administrative permissions to the ASPNET worker process user to no avail.
I have likewise attempted to use the SQL Server Agent job approach but that approach might not be acceptable for our clients since it means installing SQL Server 2005 Database services on the application server.
I have read the relevant threads in this forum, namely http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1044739&SiteID=1 and http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=927084&SiteID=1 but failed to find any solution appropriate for our set up.
I need to run a trace on a SQL 2005 Workgroup Edition. Profiler is onlyavailable in Standard and Enterprise?SQL 2005 BOL refers to serveral SPs and functions for tracing but I don'thave those in my workgroup edition.Any other options? Can I connect a SQL 2000 Profiler to 2005?Thanks.
If I have an instance of SQL Server 2005 Workgroup, am I able to run simple ETL packages against it? By simple I mean:
1. Extract data from a comma separated flat file.
2. Load the flat file data to an Access (2002/2003) database.
3. Load the flat file data to a SQL 2005 table.
4. Execution of .dtsx package.
5. Ways to execute a package (i.e. can schedule a package to be run with the SQL Server Agent)?
6. Notification (i.e. SMTP email) on events from package (i.e. on error).
I have been using the Developer Edition, which I know has all/most of the features of Enterprise. How do the SSIS features change between Developer and Workgroup editions?
I have a problem understanding the feature comparison chart for the different Sql2005 editions. It has the two lines (right under Database Engine)
- Microsoft .Net Framework
- CLR runtime integration
According to the chart the Workgroup Edition does not support the .Net Framework. But it does support the CLR runtime integration. So what does that effectively mean? What is possible, what not (like writing SPs in C#, access to web services or I/O)?
Would be great if someone could clarify the support for CLR/.Net in that area
We have developed an application using VS 2005 and SQL Server 2005 Developer Edition.
Currently, our client is asking if they could buy the SQL Server 2005 Workgroup Edition.
Is it ok? I'm afraid that the SP we made using CLR and any other functionality might not work.
We are suggesting our client to use the SQL Server 2005 Standard Edition instead. But for them to save money, can they use the Workgroup Edition instead?
I have licensed a german version of sbs 2003 premium. With the upgrade to sbs 2003 r2, I will buy the rights to use the sql 2005 workgroup edition. But the german sbs 2003 r2 is not available by now.
I could go in production with the sql 2005 trial, this is an entreprise edition.
My question is : can I downgrade the sql server 2005 from this trial edition (entreprise) to the workgroup edition ? Is it possible ? easy ? any recommendations ?
I am trying to install the workgroup edition on Windows SBS 2003 R2. After the removal of an unwanted SQL Express Edition installation - the standard install of SQL 2005 from CD hangs during setup.
In the log file _WI.log is: ... MSI (s) (B0:2C) [23:01:14:968]: Pathbuf: 0, pcchPathBuf: 0 MSI (s) (B0:2C) [23:01:14:968]: MsiProvideAssembly is returning: 1607 MSI (s) (B0:2C) [23:01:14:968]: No System Restore sequence number for this installation. MSI (s) (B0:2C) [23:01:14:968]: Unlocking Server MSI (s) (B0:2C) [23:01:14:968]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'. MSI (s) (B0:2C) [23:01:15:015]: MainEngineThread is returning 1603 MSI (s) (B0:A0) [23:01:15:109]: Destroying RemoteAPI object. MSI (s) (B0:80) [23:01:15:109]: Custom Action Manager thread ending. MSI (c) (B4:54) [23:01:15:125]: Back from server. Return value: 1603 MSI (c) (B4:54) [23:01:15:125]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (B4:54) [23:01:15:125]: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is '1'. Aktion beendet um 23:01:15: ExecuteAction. Rückgabewert 3. MSI (c) (B4:54) [23:01:15:125]: Skipping action: FatalError (condition is false) Aktion beendet um 23:01:15: INSTALL. Rückgabewert 3.
i have no idea what i am doing here and could use some help from someone who knows what they are doing.
i have a proliant ml350 g3 server running windows 2003 server with sql express 2005 software.
all the databases are running in compatibility sql 7 mode.
I would like them to be in sql 2005 mode if possible. Is there a way to upgrade the databases in the process?
here's a plan I came up with:
take sql workgroup 2005 edition evaluation, install it on a machine.
Mount all databases on the machine.
Wipe out the sql express 2005 machine, reinstall workgroup edition on the new server.
but here is my question
is there a way to migrate the data from the workgroup edition over to the new server through a DTS copy process, and if so, will it create a new version of the databases with the proper collation or the proper english?
please let me know. if this works, i will be thrilled!
I will be installing a new, SBS2003 R2 server that comes with SQL 2005 Workgroup Edition. We currently have a SQL 2000 Standard server. Can I installed SQL2000 Standard on SBS2003 R2? The reason for this is that we're not ready to migrate to SQL2005 and we need to continue running SQL2000.
It seems like the upgrade tries to use Windows authentification although I've told it to use SQL Server authentification. Or did I miss a parameter in my command line?
If I do the upgrade manually it works without needing Windows authentification.
We have only a small busines and haven't got too much experience with servers and now have a proliant server coming in with SBS 2003 R2 Premium with the 4 GB max memory that SBS 2003 can handle according to the specs.
We weren't planning on using the SQL 2005 worlgroup edition up till now, but now we might. According to the specs of SQL server 2005 workgroup edition however, it has a max RAM of 3GB!
Is this going to be a problem and should we keep using our previous DB, or can we migrate toward SQL server with the 4 GB of RAM?
I have an SBS 2003 server that is running SQL 2000 standard edition which was recently upgraded to Small Business Server 2003 R2.
I have installed SQL 2005 workgroup edition on the SBS 2003 R2 server which acts both as an AD server and Exchange server. I installed SQL 2005 for the purpose of using SQL 2005 for my sharepoint services on the Small Business Server R2.
Now I have SQL 2000 and SQL 2005 workgroup edition installed, but I'm unsure whether I can uninstall the SQL 2000 and how to know whether the sharepoint instance is running in SQL 2005 or SQL 2000?
Additionally, I have some MSDE's running for WSUS and Server Reporting which are installed by the Small Business Server installation.
Which tools should I use to become familiar with identifying the databases and which version of the database engine is used for which database regardless of whether it is a SQL instance or a MSDE instance.
How can I identify which SQL versions are not in use and whether I can uninstall if not needed.
I have clients that have the MSDE version installed and we need to upgrade there program to the MSSQL 2005. Is there an easy way to convert the data? Should or Could I uninstall MSDE and than install MSSQL2005 WorkGrp? Will there data be affected? Any tips would be appreciated.Thanks!
I've heard that the Standard version supports the use of CommandNotification and that the Express version does not. What about the Workgroup edition? The reason I'm asking is because there is a substantial monthly difference in cost between the two versions if I were to have my site hosted. I've been developing with MS SQL 2005 Express so obviously I have not tested this caching feature. Are command notifications reliable? On paper, it sounds impressive and extremely efficient especially if a site is to have heavy traffic and you can't afford the overhead of heavy database processing that is useless if the data is unchanged. Does the Workgroup edition support automatic change notifications? Have automatic notifications been proven reliable and vastly more efficient than crude polling methods? Thanks in advance.
I can schedule my task in DTS provided my sql server agent runs in the same windows authentication as of the windows login(specified the user name and pass word in the logon properties of sql server agent) and DTS package owner.
it is failing when i run with local system account. why is that so.
Hi I've build a client management (Windows) application in VS2005 which works fine on the local development machine but falls over when trying to connect to the SQL Server Express file located on a second machine on the same Workgroup. Several of the apllications will connect to the database file from networked computers. The error I get when testing the connection or trying to connect via the App is:---------------------------------------------------------------The file "Z:BushBreaks.MDF" is on a network path that is not supported for database files.An attempt to attach and auto-named database for file z:ushbreaks.mdf failed. A database with the same name exists, or specified file cannot be opened or it is on a UNC share.--------------------------------------------------------------- How can I configure this database and/or connection to be able to allow connections to the MDF file? Please note that security is not an issue if that is at all relevant. Many ThanksJohn
I have a VERY Legitmate use to install sql 4 workgroups on a pc without licensing it. I am making a disk image for MANY pcs to be imaged and load licensing after the imaging is completed.
I have been able to do this with Windows XP Professional, MS Office 2003 and a couple non-Ms programs. The information for MS software even came from their KB, so I know what I am doing is legit. I just can't find any information on doing this for my sql app.
hye everyone, when i browse my web application the eror as below display.. what should i do.. any suggestion or tips...
"Cannot start your application. The workgroup information file is missing or opened exclusively by another user. 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.OleDb.OleDbException: Cannot start your application. The workgroup information file is missing or opened exclusively by another user. "
Hi i have two version of SQL server express (with Visual Studio 2005) and developer edition i am trying to access an sql database file -created by the express edition integrated with Visual studio- using a developer edition instance can i just attach it and access it. and can i use BI and reporting services on that file
Hi all, I'm kinda new at programming, and am currently attempting to create a web application. I have an error when I try to insert information into a sql server database, and can't find how to fix it no matter how hard I try. The error I get is: Cannot start your application. The workgroup information file is missing or opened exclusively by another user. I have it so a user is logged in and is shown a form to fill out, then submits it (which creates an insert statement and sends it to the database). My connection string is as follows: CnnString = "Provider=Microsoft.Jet.OLEDB.4.0;" + "data source=serverdestination;" + "User id=user;" + "Password=pass;"; If you need any more information, just let me know. Any help would be greatly appreciated!
Just curious if there are any tutorials/help files/forums on using this and other Konesans control Flow and data flow task? most import the flow watcher task.
I need to parameterize some values in the data flow so that i can chnage the values directly in parameter file and re run the data flow for new value in the passed in the parameter. This can be easy for other who do not know about the flow of data flow task as to where to change the variable/parameter.
How can this be accomplished. I want the data flow task to refer to this file before it starts executing and pick the appropriate value from the file.
Or is their any better way to accompalish what i want to do here in SSIS.???
The import from Flat File Source fails: Error 0xc02020a1: Data Flow Task 1: Data conversion failed.
The data conversion for column "ArticleName" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.". (SQL Server Import and Export Wizard)
I have changed the size of the column "ArticleName" (varchar) to max but the error comes up again.
The data i want to import came with multiple flat files. They all could import properly but this one is a problem.
I'm copying files to a folder with the naming convention as follows in the source folder:
CM_ABC_MY_TEST.txt
In the destination folder, this filename needs to appear as:
CM_XYZ_MY_TEST.txt
In my File System Task, I'm pretty sure I'm going to need an expression with a replace, substring, etc. But am having a hard time nailing down the exact syntax.
Does anyone know how to do this using variables? Everytime I try it, I get the
Error: Failed to lock variable for read access with error 0xc00100001.
I also tried it writing a script and still the same error. If I hard code the values into the variables it works fine but I will be running this everday so that it will pull in the current date along with the filename. So the value of the variables will change everyday. Here is my expression:
I was wondering if there is a way to 'Move File' with the File System Task inside of a For Each Loop container but to dynamically set the Destination path variable.
Currently, this is what I have: FileDestinationPath variable - set to C:TestFiles FileSourcePath variable - set to C:TestFiles FileNameAndLocation variable - set to blank
For Each Loop Container €“ Iterates through a folder C:TestFiles that has .txt files in it with dates in the file name. Ex: Test_09142006.txt. Sets the file path (fully qualified) to the Variable Mapping FileNameAndLocation.
Script Task (within For Each Loop, first step) €“ Sets the FileDestinationPath to the correct dated folder within C:TestFiles. For example, if the text files I want to move are for the 14th of September, it takes FileDestinationPath and appends the date folder to the end of it. The text files have a date in the file name (test_09142006.txt) and I am picking this apart (from FileNameAndLocation in the For Each Loop) to get the folder date. (dts.Variables(€œUser::FileDestinationPath€?).Value = dts.Variables(€œUser::FileDestinationPath€?).Value & €œ€? Month & €œ_€? & Day & €œ_€? & Year & €œ€?) which gives me €œC:TestFiles 9_14_2006€?.
File System Task (within For Each Loop, second step) €“ This is where the action is supposed to occur. I want it to take the FileDestinationPath and move the FileNameAndLocation file (from the For Loop) into this folder for each run.
Now as for my problem. I want this package to run everyday but it has to set the FileDestinationPath variable dynamically according to that day€™s date. Basically, how do I get this to work since I can€™t hard code the destination path variable from the start? I have the DestinationVariable on the File System Task set to the FileDestinationPath variable, after the script task builds it. However, using FileNameAndLocation as the SourceVariable on my File System Task tells me that the €œVariable €œFileNameAndLocation€? is used as a source or destination and is empty.€?
Let me know if I need to clarify further€¦...I may be missing something very simple. Any help would be greatly appreciated!
I am able to run SSIS packages as SQL Server Agent jobs with a Control Flow items "File system task", if I move a file (test.txt) from a drive (c on the server (where SQL Agent jobs run) to a subdirectory on the same drive. But, if I try to move a file on a network drive, the package fail.
Historically I've always written a VB script to copy a file from a sharepoint library. I don't like this method because I have to input a username & password in the script and maintain a config file.
Yesterday I was playing around with using a file system task. The sharepoint file has a UNC path so why not? I created a simple test package with a single file system task that copies the sharepoint file (addressed via UNC) to another network location. Package runs fine locally.
I try running on our utility server but am getting a "The file name [SHAREPOINT UNC PATH] specified in the connection was not valid" error. Package is running with a proxy on the server and the proxy account has the same permissions to the sharepoint site (so far as I can tell) as me.
I have used the copy database wizard, but I realized I had forgotten to shrink the transaction log file. So I canceled the wizard. My database, detached by the wizard, has now disappeared. The mdf file is still there, but when I try to attach it manually I get the "create file encountered operating system error 5 while attempting to open the physical file..." error.
I have created a File System task which is contained in a Foreach Loop Container. I have .bak files that are populating a directory from a maintenance backup plan.
There is a point where I need to delete the .bak file's after I've zipped them all up.
How do I set the SourceVariable to read through the directory and pick up just the .bak file's in the directory to delete.