Ssis Package Can't Connect To Pop Server Over The Internet From Sql Server Agent
Dec 20, 2007
Sql server agent is running under a domain account that is a member of administrators and domain users amongst others, and the package is executed as the service account. Connecting to servers on the same domain works and when I run it from the msdb package store in ssis (ssis runs under the network service account ...) it will connect to the pop server as well. Permissions, fiddly proxies .. the answer's out there somewhere
View 3 Replies
ADVERTISEMENT
Apr 10, 2007
Dear All,
I'm using SSIS package to extract text file, and load into SQL Server. I test the SSIS package import manually, it works. Then I'm using SQL Server Agent to set up schedule. According to the log, the job agent work at the scheduled time, yet job agent throw out the error message.
Message1:
The job failed. The Job was invoked by User sysAdmin. The last step to run was step 1 (Extract Data).
Message2:
Executed as user: SQLSERVERsysAdmin. The package could not be loaded. The step failed.
Now I only have 1 step and set up "on success action" then "quite the reporting success". Any clue? Thanks
will
View 11 Replies
View Related
Apr 9, 2007
Hi Everyone:
I would like to find out, if there is something I can implement/or should I need to implement to avoid running two concurrent processes of 1 SSIS Package. I mean by default, I will schedule the SSIS package to run utilizing SQL Server Agent. But How I avoid/prevent it to run concurrently or what do I need to setup where I only allow 1 instance of my package to run. Thanks.
View 10 Replies
View Related
Apr 5, 2007
Dear All,
My SSIS package is "Extract" data from Oracle and Load into SQL Server.
The SSIS package does not run when I call the SSIS package from a SQL Server Agent job step
I have gone through all the steps in the doc http://support.microsoft.com/kb/918760, but it still doesn't work.
Is it because of connection to "Oracle" database? and SQL Server Agent service could not recognise the Authentication information to Oracle?
Why I am saying this is becuase it works if I change the package to "Extract" data only from SQL Server.
Anyone has experience on this problem?
Many Thanks in Advance
John
View 11 Replies
View Related
Sep 6, 2007
I've been looking everywhere for a hint on how to tackle this, but can't get it to work.
I have an SSIS package that I am trying to run from SQL Server Agent.
I have been able to run it fine from the IDE, and from within the Integration Services system on my database server. However when I try to run the package via SQL Server Agent I get the following error:
"Executed as user: MyDomainSQLServer. The package execution failed. The step failed."
The login name is the SQL Server service account, which is a domain account on our domain. The package is set with EncryptSensitiveWithPassword and the password is supplied on the command line via the /DECRYPT flag.
I am thinking that maybe there is a permissions problem with the service account, but I can't find any detailed information about what actual permissions this account requires. I have tried expanding its permissions, but continue to get this error.
How should the MyDomainSQLServer account be configured?
View 4 Replies
View Related
Feb 1, 2007
I have a problem running an SSIS package in a SQL Server job. The package runs fine if I run it from the MSDB location, but if I try to run the job it fails. The job is set to Run as: SQL Agent Service Account. The SQL Service Agent service runs as a domain user SQLExec. I have logged in as this user and run the SSIS package and it runs fine, but if I create a job with only this step it fails. There isn't much information about where there is a problem. Any ideas or ways to troubleshoot this problem would be very much appreciated.
Thanks, john
View 3 Replies
View Related
May 29, 2007
Hi
I hv created a new Job for my SSIS Package... but when i start the job manually it gives me this error below:
"Executed as User:localhost/SYSTEM. THe package could not be loaded.the Step Failed".
i have my package deployed in Storage Packages[MSDB]...
Could you help me on this....
THanks!
Karthik
View 1 Replies
View Related
Feb 9, 2007
Hello
do ne one know how to call a SQL SERVER agent job from a SSIS package?
regards,
Anas
View 1 Replies
View Related
May 13, 2008
I created a SSIS package using VS2005 with the "ProtectionLevel" set to "DontSaveSensitive" . I executed the package and it completed without an error. I then built the package and deployed it to the SSIS inside the folder "MSDB". I run the pakage in SSIS and it worked perfectly. Then I created a job in SQL Server Agent and have it run in a per-set schedule. It failed to run withthe following error:
Message
Executed as user: SRVSOUDB01SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:11:02 PM Error: 2008-05-12 22:11:03.17 Code: 0xC001401E Source: STDM Connection manager "Target_AS_STDM.abf" Description: The file name "\Svmppodb01OLAP DataSql DataBackUpAS_STDM.abf" specified in the connection was not valid. End Error Error: 2008-05-12 22:11:03.17 Code: 0xC001401D Source: STDM Description: Connection "Target_AS_STDM.abf" failed validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:11:02 PM Finished: 10:11:03 PM Elapsed: 0.422 seconds. The package execution failed. The step failed.
The error mentioned the step in SSIS Package that requires to copy the backup of the OLAP database file "AS_STDM.abf" from the Source Server location (local processing server SRVSPOYDB01) to the Targer Server location (remote production server SVMPPODB01) "Svmppodb01OLAP DataSql DataBackUpAS_STDM.abf". This step worked in the SSIS(SRVSOUDB01) when executing there. Why it is not working in Sql Server Agent(SRVSOUDB01). It also works in VS 2005.
Thanks.
View 3 Replies
View Related
Mar 12, 2007
Hello All,
My database application has certain stored procedures which are scheduled to run at certain predefined interval (say once everyday). Now to implement this logic I have two options with me, first being to use the EXECUTE SQL TASK of the SSIS package and schedule it using the windows scheduler and the other is to use the SQL Server Agent Jobs and schedule it there itself. Now the current implementation is using the SSIS packages and I even know that the second approach of using the SQL Server Agents Job is better.
The only thing I want to know is whether it makes sense to invest time in converting my SSIS packages (20 in all) to SQL Server Agent jobs or not. Can somebody briefly explain or give some pointers regarding the performance benefits of Agent Jobs over the SSIS packages.
Thanks in Advance
Mitesh
View 5 Replies
View Related
Mar 3, 2008
Hi
I have setup a step in SQL Server Agent to run a SSIS package that I have created. However the step fails straight away and refers me to the history log, which doesnt seem to show what the problem is.
I've tried running the package manually through dtexec.exe and it runs through fine. Does anyone know what the problem could be?
Thanks
View 9 Replies
View Related
Oct 1, 2007
I have an SSIS ETL Package that runs perfectly in debugger.
It is saved to the local SQL Server using "rely on server security".
The SQL Server Agent job runs at night and the job fails right at the last step. It is actually loading the data, because I write a record with row counts to an audit table, and they are successfully incrementing.
The real issue to me is that it is failing randomly, sometimes it will run 7 times then fail once, others it will go 2 or 3 days then fail. The job runs at the same time every night, and takes within a minute or two variance.
I've looked at the logs, and done a trace, and I can't seem to find anything that would cause the failure. The closest thing to an error is a join parameter note in the trace that's on tthe MSDB database.
Not a lot to work with, I know... but does anybody have any advice for me? Thank you in advance!
View 2 Replies
View Related
May 9, 2006
HELP! I have been banging my head against a brick wall on this one all this morning AAAAAAGGGHHH!
1. I have an SSIS package that runs a simple SQL script and then updates a few tables by downloading some XML of the web. It runs fine when I kick it off manually under SSMS.
2. I created a SQL Server Agent job to run it every day. This always fails. The error information in the log is useless ("Executed as user: domainuser. The package execution failed. The step failed." - I had already figured that out!). It fails almost straight away, and when I enable logging for the SSIS package, no info is ever logged (text file, windows event log, whatever).
3. Out of desperation I have changed Agent to run under the same domain user account that I created the package with. No use.
My questions:
1. How can I get more detailed logging from SQL Server Agent?
2 Any ideas about why it's failing in the first place.
Many thanks in advance.
Ben
View 17 Replies
View Related
Nov 28, 2007
Hello,
I try to run a job from SQL Server Agent to execute an SSIS package, but it always fails. However, if I execute the SSIS package directly, it will succeed.
The SQL Agent Job History shows "Unable to start execution of step 1 (reason: Error authenticating proxy DB1DB1_CREDENTIAL, system error: Logon failure: unknown user name or bad password.). The step failed."
P.S. DB1 is my server name, DB1_CREDENTIAL is the account creating the credential
The SQL Server Agent Error Log shows "[298] SQLServer Error: 22046, Impersonation error. [SQLSTATE 42000]"
I've created an account on OS and assigned it to a credential.
Then, I created a proxy with the credential and then created the SQL Server Agent job with that proxy.
P.S. My SSIS package protection level is created as "Rely on server storage and roles for access control", because if it is set as "Do not save any sensitive data", package execution will fail even I run it directly.
How can I successfully run SSIS package from SQL Server Agent?
Do I lose any setting steps?
Thanks for help.
Lilia
View 18 Replies
View Related
Feb 21, 2008
HI,
I am having a strange error coming in SQL server 2005.
I had a DTS package developed in SQl server 2000. Then i had migrated that DTS package to SSIS package using Execute DTS 2000 package. The conversion is successfull.
Then when i manullt execute this package it runs successfully without giving any error.
But then wheh i schedule a SQL server agent job for the same above SSIS package it fails giving me some cryptographic error as follows:
Message
Executed as user: CATOS-CGDBTUW02SYSTEM. ....3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:00:00 PM Error: 2008-02-20 23:00:00.66 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "PackagePassword" with error 0x8009000B "Key not valid for use in specified state.". 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. End Error Error: 2008-02-20 23:00:00.66 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "SQLPassword" with error 0x8009000B "Key not valid for use in specified state.". 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. End Error Error: 2008-02-20 23:00:01.00 Code: 0x00000000 Source: Execute DTS 2000 Package T... The package execution fa... The step failed.
Not sure why is this happening.
Manually running the SSIS package from Visual studio does not gives error, but the same SSIS package when is been schedule from SQL server 2005's SQL server agent job it fails giving above error.
Please help me out how to rectify whith this.
Thanks.. in advance
Regards,
Ashok
View 3 Replies
View Related
Dec 19, 2007
I have a problem where I have an SSIS package (SQL Server 2005) that won't run properly from SQL Server Agent, but it runs fine when kicked off manually from Integration Services -> Run Package or when run in debug from Visual Studio.
The first step in the package checks for the existance of a file via a script task. The script looks like this...
Code Block
Public Sub Main()
Dim TaskResult As Integer
Dim ImportFile As String = CStr(Dts.Variables("BaseDirectory").Value) + CStr(Dts.Variables("ImportDirectory").Value) + CStr(Dts.Variables("ImportFile").Value)
If Dir(ImportFile) = "" Then
Dts.TaskResult = Dts.Results.Failure
Else
Dts.TaskResult = Dts.Results.Success
End If
Return
End Sub
This script runs fine and the file is seen as expected when I run the package manually. But as a step in a SQL Server Agent job, it doesn't see the file.
The SQL Server Agent service is set to start up / log on as a Local System Account. I've also tried setting up a credential / proxy (using an account that I know can see and even move / rename the file) to run the job as but that didn't seem to help.
The package is being run from SQL Server (stored in MSDB) and is set to rely on SQL Server for sensitive information, so I don't think that's an issue; other packages are set up like this in terms of sensitive data and run fine.
Any ideas why my script can't "see" the file I'm looking at when it's kicked off by SQL Server agent? I've looked and looked...I can't seem to figure this out. I would really appreciate any help you might be able to offer up.
View 12 Replies
View Related
Nov 23, 2010
My package is connecting to an external data provider using an OLEDB driver . The package runs fine in debug mode.When i tried to run the same from SQL server agent it failed to aquire the connection. The OLEDB provider does not contain too much of information , ( connection string, initial catalog, blank user name and password).The same package executes successfully if i run using dtexec in BAT file.But if i use the dtexec in sql server job step as operating system command and try to run, the job will fail reporting " can not aquire the connection".
View 2 Replies
View Related
Mar 12, 2008
Hi
I have a problem i receive the following error message when i try to add an new step into a SQL Server Agent job :
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
Additional information:
An exception occured while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.(Microsoft SQL Server, Error: 3930)
This error pops up right after i change the type of the step to "SQL Server Intergration Services Package"
I have made the following configurations:
The user group (windows group) that the user belongs has the following roles in msdb :
db_dtsadmin
db_dtsltuser
db_dtsoperator
SQLAgentOperatorRole
SQLAgentReaderRole
SQLAgentUserRole
i have made a proxy to sql server agent which has the following subsystems :
"SQL Server Integration Services Provider" the proxy is tied to the same login which has those SQLagent and dts roles in msdb database.
Im using windows authentication and the user that logs into the sql server is in the same group that i have set all of the rights.
Ps. Clearly im missing some role or right somewhere because as soon as i give the group sysadmin role then all the users in that group can create SSIS steps in the agent.
Ps. Ps. I have been living under the impression that i dont have to give sysadmin rights to people that create ssis packages and schedule then with the agent.
View 1 Replies
View Related
Jan 4, 2008
I'm trying to execute my package using schedule in SQL Server Agent, I've already tested my package by run it manually in Integration services and it works. The table created, the data from my flat file also inserted into the table correctly and the result return with success.
The question is why when I execute my package using SQL Server Agent, the SQL Server Agent keep executing my package like infinite loop until I stop the job. after I stop the job there is no error generated by sql server. Could you figured why this happen?? I've already tried to upgrade into SP2 and set the package protection level and still not get good result from it. thank you.
View 11 Replies
View Related
Apr 1, 2008
Hello
I'm trying to run a task that executes a script file (cmd). When i run it with in bids with my own users (domain admin) it works. When i start a cmd prompt and try to run the cmd file directly from the network location where it is it works (with my own rights and with the sql server agent user).
Now when i try to run in from smss > agent jobs > job and run job it never completes. Im not getting any error message either it just keeps on running on the step ??? It seems like a rights issue, but the account running the sql server agent is able to execute the cmd file directly from the command prompt.
There are no errors in any error logs anywhere and no error is displayed...
Ps. Im running the job step as a integration service pacgake.
View 8 Replies
View Related
Aug 3, 2006
I am trying to
copy a database from our company's external SQL
Server(production) to our local SQL
Server(development). The Copy Database wizard fails on the step
"Execute SQL Server Agent Job".
Following is the error in the log file.. Please advise
InnerException-->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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
View 7 Replies
View Related
Oct 19, 2010
I have a SSIS package which reads an excel file and loads data into a table using script component(C#) as a source. The package runs without any errors when I manually run it on my machine and on the server. But the package fails when run as a SQL Server Agent job.
I tried all the possible fixes I found on the web but still can't get it to work.
View 14 Replies
View Related
Aug 17, 2006
I have an SSIS package that runs fine through command pormpt although when I try to run it from a SQL Servr Agent Job CmdExec step it bombs out. Please help this has me stumped...the SSIS package uses an XML connection string so certain key settings such as connection strings and email info can be changed easily. Currently this is all on the same machine. I have not moved it beyond where I am developing.
On the command line I am using the following command...
dtexec /F "S:connectionscontacts.dtsConfig" /DE "password"
Below is the output log...
Microsoft (R) SQL Server Execute Package Utility
Version 9.00.1399.06 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 6:59:40 PM
Progress: 2006-08-16 18:59:41.29
Source: Data Flow Task
Validating: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.29
Source: Data Flow Task
Validating: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.71
Source: Data Flow Task
Validating: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.73
Source: Data Flow Task
Validating: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.77
Source: Data Flow Task
Validating: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.77
Source: Data Flow Task
Validating: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.77
Source: Data Flow Task
Validating: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.77
Source: Data Flow Task
Validating: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.79
Source: Data Flow Task
Prepare for Execute: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.79
Source: Data Flow Task
Prepare for Execute: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.79
Source: Data Flow Task
Prepare for Execute: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.79
Source: Data Flow Task
Prepare for Execute: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.81
Source: Data Flow Task
Pre-Execute: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.84
Source: Data Flow Task
Pre-Execute: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.90
Source: Data Flow Task
Pre-Execute: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.90
Source: Data Flow Task
Pre-Execute: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.92
Source: Data Flow Task
Post Execute: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.92
Source: Data Flow Task
Post Execute: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.92
Source: Data Flow Task
Post Execute: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.92
Source: Data Flow Task
Post Execute: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.92
Source: Data Flow Task
Cleanup: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.93
Source: Data Flow Task
Cleanup: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.93
Source: Data Flow Task
Cleanup: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.93
Source: Data Flow Task
Cleanup: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.95
Source: Send Mail Task
The SendMail task is initiated.: 0% complete
End Progress
Progress: 2006-08-16 18:59:42.09
Source: Send Mail Task
The SendMail task is completed.: 100% complete
End Progress
DTExec: The package execution returned DTSER_SUCCESS (0).
Started: 6:59:40 PM
Finished: 6:59:42 PM
Elapsed: 1.984 seconds
When I try to use the same command within SQL Server Agent Job using a CmdExec step I get the following error...
Description: The package is attempting to configure from the XML file "S:connectionscontacts.dtsConfig". End Info Warning: 2006-08-16 18:40:03.15 Code: 0x80012012 Source: contactsPackage Description: The configuration file name "S:connectionscontacts.dtsConfig" is not valid. Check the configuration file name. End Warning Warning: 2006-08-16 18:40:03.15 Code: 0x80012059 Source: contactsPackage Description: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to see descriptions of which configuration failed. End Warning Info: 2006-08-16 18:40:03.20 ... Process Exit Code 1. The step failed.
Thanks in advance for any help!!!
View 2 Replies
View Related
Oct 27, 2005
My English is not good.
I want to connect to other computer that installed M$ SQL Server2K over INTERNET. could you help me, plz.
I have used DNS (DOMAIN NAME SYSTEM) to forward to my computer( that connect to INTERNET) and my friend computer is the same. (because we have not static IP).
Thanks
:D
View 7 Replies
View Related
Mar 6, 2005
Hi,
Can someone please tell me how to do that?
I tried to connect to a sql server through internet by using sql query analyzer but it failed.
I searched for information in the internet but came to no avail.
Can someone please shed some light?
Thanks!
View 2 Replies
View Related
Sep 6, 2006
Hi there
We have the following problem. Our DB (MSDE 2000) is situated on remote server on which we
have
administrator privilege. The application which works on Local net connect to every machine in
the
net and see the database on one of the mashine as well.
The connection string is
data source=192.168.0.1XXXX;initial catalog=XXXX;integrated security=SSPI;persist security
info=True;workstation id=XXXX;packet size=4096"
but when we change IP in the connection string to our remote server(in internet with static IP) one we get
an exception says that
SQL server does not exist or access denied.
We opened ports on firewall but problem is still here. Then swithched off the firewall at all
but
same exception comes.
Thanks for answers
View 12 Replies
View Related
Feb 13, 2006
Hi,
i created a SSIS package to import data to a remote sql server, using the following connection string:
"Data Source=My-SQL;User ID=PortalUser;Password=Password;Initial Catalog=TestOMIWarehouse;Provider=SQLNCLI.1;Auto Translate=True;";
and got an error "Login failed".
When i give PortalUser a sysadmin server role, it works. But i don't want to give PortalUser a sysadmin role. Any suggestions? Is sysadmin role required to access a remote server using Sql server authentication?
thanks! Any help would be appreciated.
alea
View 4 Replies
View Related
Mar 18, 2004
Hi,
I am making a web application and it works fine. It uses Sql Server 2000 as the database. But when I connect to the Internet and compile or run my application it gives me this message :
" SQL SERVER DOES NOT EXIST OR ACCESS DENIED"
it works finewhen iam not connected to the internet
View 4 Replies
View Related
Jul 25, 2005
I'm Building a windows application which updates an internet site's database.Is it possible to connect directly to the sql server through the internet?If so is it the most efficient way ? perhaps a web service or streaming is a better solution?Thanks.
View 1 Replies
View Related
Feb 27, 2004
Hi all,
I 'm in VietNam, i want to use SQL server 2000 to connect to SQL server in China throught the internet. I did it in many way but it did not work, please show me.
Best regards
View 2 Replies
View Related
Apr 11, 2004
i have got to connect to sql server desktop engine over internet with the following connection string
conString = "Provider=SQLOLEDB.1;Persist Security Info=True;Initial Catalog=" & dbName & ";Network Address=" & IPAddress & ";Data Source=" & DataSource & " ;User ID=" & UserId & " ; Password=" & Password
Plz also inform me about the restriction imposed in connectivity by any of the window operating system such as that win 98 wont work or work!
There is no firewall involved. The two computers are in the same room and connected directly to the internet.
Even the ping is not going to either computer.
So what could be the possible problem and the solution.
need urgent
View 1 Replies
View Related
Jul 12, 2007
Hi!I am trying to connect to my SqlServer 2005 thru internet, but it is notworking. I have a dyndns updater on my server which tells me an ip addressof the router. The router is configured to forward TCP port 1433 to LAN IPaddress of the computer on which is SQL Server installation.What is the connection string to connect to my server.I tried xxx.dyndns.org:1433, but it doesn't work. There is a defaultinstance installed on that machine.Please help.Zvonko
View 6 Replies
View Related
Mar 29, 2007
Hi guys,
Can somebody tell me where i can find ( or explain me ) the steps to
connect to sql server using the internet. I am using VB6 (SP6) and SQL SERVER 2000
I want to set up asql server on a central location ( PC ) so that 4 different sites can access the data stored
Thanks for all help
grtz Robert
View 1 Replies
View Related
