Showing posts with label quotthe. Show all posts
Showing posts with label quotthe. Show all posts

Monday, March 19, 2012

Error in Sending Emails

Hi,

i am getting the following error when i try to schedule a report and Delivery it through an email

"The e-mail address of one or more recipients is not valid"

although, i have mentioned my pop3 mail account, i have included the smtp server details in the .config files as per the msdn help.

pl help me solve this

T & R,

Bharath V V

Which article are you refering to ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||try to give only one email id. and then if it works, try to give multiple ids. check ur SMTP server you have given is valid one|||

Hi,

i have reffered to the following article:

http://msdn2.microsoft.com/en-us/library/ms159155.aspx

Regards,

Bharath V V

Error in Scheduling SSIS Package

Hi,

When I am trying to schedule the SSIS package and start the job, I am getting the following error. It is not executing properly.

"The job failed. The Job was invoked by User prakash.srinivasan. The last step to run was step 1 (TestSchStep1)."

Pls provide some solution to this.

Thanks in advance.

Regards,
Prakash Srinivasan.

Please see this KB on how to troubleshoot this:

http://support.microsoft.com/kb/918760

|||I had the same problem and replace the user for another one which was domain admin and works properly|||

Hi,

I created a package with the username who has admin rights only and tried to schedule it. But I am getting this error.

"The job failed. The Job was invoked by User prakash.srinivasan. The last step to run was step 1 (CopyFile_Step1)

Executed as user: AMR500\sqladmin. The package execution failed. The step failed."

Pls provide some solution for this.

Thanks & Regards,
Prakash Srinivasan.

|||

Hi

Check the service of SQL Server Agent whether it is running in your account.

Regards

H.SRIRAM

|||

Prakash - have you reviewed the KB article referenced above? It describes possible problems due to different protection levels, and most importantly how to enable logging and troubleshot this kind of problems.

|||

Dear prakash,

Did u check whether the package runs in sql server ?.

if it is not successful then you need to define package protection as donot save sensitive and use SSIS configuration to store database connection in XML or sql server. Once it successful then try for schedule the package.

if schedule fails check your sql server agent services(Control panel- administrative tools-services). By defualt it will be Local Account System change to current user. Try to execute the package It will work.

Sriram

|||

Hi,

Did u check whether the package runs in sql server ?.

Yes, it is running in the SQL Server only.

Also, as you mentioned I set the ProtectionLevel as Don't Save Sensitive only and used the Package Configuration for ConnectionString and stored in the XML file.

And I checked the SQL Server Agent services, it was like sqladmin. If I change my username, then other packages will get affected right.

Also guide me how to change the username in the SQL Server Agent Services.

Thanks & Regards,
Prakash Srinivasan

|||

Change the username under which the Agent service runs. You can do this in the good old Services panel.

-Jamie

|||

i am executing as an administrator and running the package as an admnistrator. But still it fails

jas

|||

One thing you might want to check is to see if the PC where you developed the application is on the same version as the server where you are running the package.

I had this same problem while I was developing on SQL 2005 SP1 and deploying the package to run on SQL 2005. Once I installed SP1 on the server, the packages started running successfully again.

Hope this helps,

Jarret

Error in Scheduling SSIS Package

Hi,

When I am trying to schedule the SSIS package and start the job, I am getting the following error. It is not executing properly.

"The job failed. The Job was invoked by User prakash.srinivasan. The last step to run was step 1 (TestSchStep1)."

Pls provide some solution to this.

Thanks in advance.

Regards,
Prakash Srinivasan.

Please see this KB on how to troubleshoot this:

http://support.microsoft.com/kb/918760

|||I had the same problem and replace the user for another one which was domain admin and works properly|||

Hi,

I created a package with the username who has admin rights only and tried to schedule it. But I am getting this error.

"The job failed. The Job was invoked by User prakash.srinivasan. The last step to run was step 1 (CopyFile_Step1)

Executed as user: AMR500\sqladmin. The package execution failed. The step failed."

Pls provide some solution for this.

Thanks & Regards,
Prakash Srinivasan.

|||

Hi

Check the service of SQL Server Agent whether it is running in your account.

Regards

H.SRIRAM

|||

Prakash - have you reviewed the KB article referenced above? It describes possible problems due to different protection levels, and most importantly how to enable logging and troubleshot this kind of problems.

|||

Dear prakash,

Did u check whether the package runs in sql server ?.

if it is not successful then you need to define package protection as donot save sensitive and use SSIS configuration to store database connection in XML or sql server. Once it successful then try for schedule the package.

if schedule fails check your sql server agent services(Control panel- administrative tools-services). By defualt it will be Local Account System change to current user. Try to execute the package It will work.

Sriram

|||

Hi,

Did u check whether the package runs in sql server ?.

Yes, it is running in the SQL Server only.

Also, as you mentioned I set the ProtectionLevel as Don't Save Sensitive only and used the Package Configuration for ConnectionString and stored in the XML file.

And I checked the SQL Server Agent services, it was like sqladmin. If I change my username, then other packages will get affected right.

Also guide me how to change the username in the SQL Server Agent Services.

Thanks & Regards,
Prakash Srinivasan

|||

Change the username under which the Agent service runs. You can do this in the good old Services panel.

-Jamie

|||

i am executing as an administrator and running the package as an admnistrator. But still it fails

jas

|||

One thing you might want to check is to see if the PC where you developed the application is on the same version as the server where you are running the package.

I had this same problem while I was developing on SQL 2005 SP1 and deploying the package to run on SQL 2005. Once I installed SP1 on the server, the packages started running successfully again.

Hope this helps,

Jarret

Error in Scheduling SSIS Package

Hi,

When I am trying to schedule the SSIS package and start the job, I am getting the following error. It is not executing properly.

"The job failed. The Job was invoked by User prakash.srinivasan. The last step to run was step 1 (TestSchStep1)."

Pls provide some solution to this.

Thanks in advance.

Regards,
Prakash Srinivasan.

Please see this KB on how to troubleshoot this:

http://support.microsoft.com/kb/918760

|||I had the same problem and replace the user for another one which was domain admin and works properly|||

Hi,

I created a package with the username who has admin rights only and tried to schedule it. But I am getting this error.

"The job failed. The Job was invoked by User prakash.srinivasan. The last step to run was step 1 (CopyFile_Step1)

Executed as user: AMR500\sqladmin. The package execution failed. The step failed."

Pls provide some solution for this.

Thanks & Regards,
Prakash Srinivasan.

|||

Hi

Check the service of SQL Server Agent whether it is running in your account.

Regards

H.SRIRAM

|||

Prakash - have you reviewed the KB article referenced above? It describes possible problems due to different protection levels, and most importantly how to enable logging and troubleshot this kind of problems.

|||

Dear prakash,

Did u check whether the package runs in sql server ?.

if it is not successful then you need to define package protection as donot save sensitive and use SSIS configuration to store database connection in XML or sql server. Once it successful then try for schedule the package.

if schedule fails check your sql server agent services(Control panel- administrative tools-services). By defualt it will be Local Account System change to current user. Try to execute the package It will work.

Sriram

|||

Hi,

Did u check whether the package runs in sql server ?.

Yes, it is running in the SQL Server only.

Also, as you mentioned I set the ProtectionLevel as Don't Save Sensitive only and used the Package Configuration for ConnectionString and stored in the XML file.

And I checked the SQL Server Agent services, it was like sqladmin. If I change my username, then other packages will get affected right.

Also guide me how to change the username in the SQL Server Agent Services.

Thanks & Regards,
Prakash Srinivasan

|||

Change the username under which the Agent service runs. You can do this in the good old Services panel.

-Jamie

|||

i am executing as an administrator and running the package as an admnistrator. But still it fails

jas

|||

One thing you might want to check is to see if the PC where you developed the application is on the same version as the server where you are running the package.

I had this same problem while I was developing on SQL 2005 SP1 and deploying the package to run on SQL 2005. Once I installed SP1 on the server, the packages started running successfully again.

Hope this helps,

Jarret

Friday, March 9, 2012

Error In Merge Replication while server syncs

At first we received error like

"The merge process could not retrieve identity range resource for table..."

then after solving this error we again started syncing of servers manually then we got some other error like

"the process could not enumerate changes to the subscriber".

We tried our best to solve this problem but some error appears each time like

"The process could not deliver the snapshot to the Subscriber."

"The schema script 'sync -t"Design" -o"dbo" -d"\\ECOSYSTEM\D$\FTP\MSSQL\EcoSystem\ftp\ECOSYSTEM_MLEcosystem_MLEcosystem\20060619204802\Design_1337.bcp" -hORDER( [intDesignId] ASC)' could not be propagated to the subscriber"

again identity erroe emerges and agin we do the same process.

How to solve these problem?

These look like transitory network issues. Can you set QueryTimeout to something larger and see if this solves the problem.

-- Hilary Cotter

Error in Merge replication "The schema script..."

I'm trying to set up a merge replication. Publication is created successfully and snapshot also, but when I create pull subscription on subscriber server and merge agent starts, after some time I get an error message of this type:

The schema script '\\ANIL\REPLDATA\unc\ANIL_BEJK_BEJK\20070625142735\dl_HF_vMSCene_3836.sch' could not be propagated to the subscriber.

It seams there is a problem with certain Views and SPs, because tables are successfully created, and some Views and SPs also.

I tried to exclude problematic articles, but every time another one pops up. Up until now, I excluded 7 articles from publication (1 Stored Procedure and 6 Views) but I still get errors.

I gave up because I can't exclude half of the Views and SPs just to make it work.

Is there something that can be done to solve this problem?

Thanks!
Does your SQL Server agent account have rights to read the share \\anil\repldata? Ensure that this account also has rights to list files and folders on the physical drive underlying \\anil\repldata.

If you are using a push subscription it should be the SQL Server agent account on the publisher. If you are using a pull subscription is should be the SQL Server agent account on the subscriber.|||

Hi Hilary

Sharing permisions were set to Read/Write to "Everyone", and security permisions also Read/Write to "Everyone", but it didn't work until I added an account on subscriber computer (which is not in domain) with same username and password as one that exists on publisher (which is in domain). I set SQL Server Agent to use that account and everything started to work fine.

I'm connecting to publisher using the VPN, and despite the fact that those two accounts are not from the same domain, everything is working fine. This is a little bit confusing. It looks like domain name doesn't play any role when logging in to shared folder.

Thanks for the help.

Anil

Error in Merge replication "The schema script..."

I'm trying to set up a merge replication. Publication is created successfully and snapshot also, but when I create pull subscription on subscriber server and merge agent starts, after some time I get an error message of this type:

The schema script '\\ANIL\REPLDATA\unc\ANIL_BEJK_BEJK\20070625142735\dl_HF_vMSCene_3836.sch' could not be propagated to the subscriber.

It seams there is a problem with certain Views and SPs, because tables are successfully created, and some Views and SPs also.

I tried to exclude problematic articles, but every time another one pops up. Up until now, I excluded 7 articles from publication (1 Stored Procedure and 6 Views) but I still get errors.

I gave up because I can't exclude half of the Views and SPs just to make it work.

Is there something that can be done to solve this problem?

Thanks!
Does your SQL Server agent account have rights to read the share \\anil\repldata? Ensure that this account also has rights to list files and folders on the physical drive underlying \\anil\repldata.

If you are using a push subscription it should be the SQL Server agent account on the publisher. If you are using a pull subscription is should be the SQL Server agent account on the subscriber.|||

Hi Hilary

Sharing permisions were set to Read/Write to "Everyone", and security permisions also Read/Write to "Everyone", but it didn't work until I added an account on subscriber computer (which is not in domain) with same username and password as one that exists on publisher (which is in domain). I set SQL Server Agent to use that account and everything started to work fine.

I'm connecting to publisher using the VPN, and despite the fact that those two accounts are not from the same domain, everything is working fine. This is a little bit confusing. It looks like domain name doesn't play any role when logging in to shared folder.

Thanks for the help.

Anil