Hi All,
I am using SQL SERVER 2005 Standard Edition. I have enabled
database mail from Surface Area Configuration and also configured
database mail from Object Explorer ->management.
When i am trying to send mail by using extended stored
procedure xp_sendmail i am getting error as follows:
xp_sendmail: Procedure expects parameter @.user, which was not
supplied.
It will be a great help if you guys can help me.
Thanks in advance.
Hi,
It looks like you configured Database Mail, a new feature in SQL Server
2005, but are trying to send e-mail using xp_sendmail, a stored procedure
that uses SQL Mail, which is a different SQL Server feature. Use
sp_send_dbmail instead. Look BOL for more details and examples.
Make sure you really configured Database Mail, right-click Database Mail and
select 'Send Test E-mail' to test that it works.
By the way, SQL Mail, according to BOL, will be removed in a future version
of SQL Server.
Hope this helps,
Ben Nevarez
"mohit" wrote:
> Hi All,
> I am using SQL SERVER 2005 Standard Edition. I have enabled
> database mail from Surface Area Configuration and also configured
> database mail from Object Explorer ->management.
> When i am trying to send mail by using extended stored
> procedure xp_sendmail i am getting error as follows:
> xp_sendmail: Procedure expects parameter @.user, which was not
> supplied.
> It will be a great help if you guys can help me.
> Thanks in advance.
>
Showing posts with label configuration. Show all posts
Showing posts with label configuration. Show all posts
Thursday, March 22, 2012
error in xp_sendmail
Hi All,
I am using SQL SERVER 2005 Standard Edition. I have enabled
database mail from Surface Area Configuration and also configured
database mail from Object Explorer ->management.
When i am trying to send mail by using extended stored
procedure xp_sendmail i am getting error as follows:
xp_sendmail: Procedure expects parameter @.user, which was not
supplied.
It will be a great help if you guys can help me.
Thanks in advance.Hi,
It looks like you configured Database Mail, a new feature in SQL Server
2005, but are trying to send e-mail using xp_sendmail, a stored procedure
that uses SQL Mail, which is a different SQL Server feature. Use
sp_send_dbmail instead. Look BOL for more details and examples.
Make sure you really configured Database Mail, right-click Database Mail and
select 'Send Test E-mail' to test that it works.
By the way, SQL Mail, according to BOL, will be removed in a future version
of SQL Server.
Hope this helps,
Ben Nevarez
"mohit" wrote:
> Hi All,
> I am using SQL SERVER 2005 Standard Edition. I have enabled
> database mail from Surface Area Configuration and also configured
> database mail from Object Explorer ->management.
> When i am trying to send mail by using extended stored
> procedure xp_sendmail i am getting error as follows:
> xp_sendmail: Procedure expects parameter @.user, which was not
> supplied.
> It will be a great help if you guys can help me.
> Thanks in advance.
>|||On Jan 18, 12:51=A0pm, Ben Nevarez
<BenNeva...@.discussions.microsoft.com> wrote:
> Hi,
> It looks like you configured Database Mail, a new feature in SQL Server
> 2005, but are trying to send e-mail using xp_sendmail, a stored procedure
> that uses SQL Mail, which is a different SQL Server feature. Use
> sp_send_dbmail instead. Look BOL for more details and examples.
> Make sure you really configured Database Mail, right-click Database Mail a=nd
> select 'Send Test E-mail' to test that it works.
> By the way, SQL Mail, according to BOL, will be removed in a future versio=n
> of SQL Server.
> Hope this helps,
> Ben Nevarez
>
> "mohit" wrote:
> > Hi All,
> > =A0 =A0 =A0 =A0I am using SQL SERVER 2005 Standard Edition. I have enabl=ed
> > database mail from Surface Area Configuration and also configured
> > database mail from Object Explorer ->management.
> > =A0 =A0 =A0 =A0When i am trying to send mail by using extended stored
> > procedure xp_sendmail i am getting error as follows:
> > =A0 =A0 xp_sendmail: Procedure expects parameter @.user, which was not
> > supplied.
> > =A0 =A0 =A0It will be a great help if you guys can help me.
> > =A0 =A0 =A0Thanks in advance.- Hide quoted text -
> - Show quoted text -
Hi,
Thanks a lot. It helped me a lot.
I am using SQL SERVER 2005 Standard Edition. I have enabled
database mail from Surface Area Configuration and also configured
database mail from Object Explorer ->management.
When i am trying to send mail by using extended stored
procedure xp_sendmail i am getting error as follows:
xp_sendmail: Procedure expects parameter @.user, which was not
supplied.
It will be a great help if you guys can help me.
Thanks in advance.Hi,
It looks like you configured Database Mail, a new feature in SQL Server
2005, but are trying to send e-mail using xp_sendmail, a stored procedure
that uses SQL Mail, which is a different SQL Server feature. Use
sp_send_dbmail instead. Look BOL for more details and examples.
Make sure you really configured Database Mail, right-click Database Mail and
select 'Send Test E-mail' to test that it works.
By the way, SQL Mail, according to BOL, will be removed in a future version
of SQL Server.
Hope this helps,
Ben Nevarez
"mohit" wrote:
> Hi All,
> I am using SQL SERVER 2005 Standard Edition. I have enabled
> database mail from Surface Area Configuration and also configured
> database mail from Object Explorer ->management.
> When i am trying to send mail by using extended stored
> procedure xp_sendmail i am getting error as follows:
> xp_sendmail: Procedure expects parameter @.user, which was not
> supplied.
> It will be a great help if you guys can help me.
> Thanks in advance.
>|||On Jan 18, 12:51=A0pm, Ben Nevarez
<BenNeva...@.discussions.microsoft.com> wrote:
> Hi,
> It looks like you configured Database Mail, a new feature in SQL Server
> 2005, but are trying to send e-mail using xp_sendmail, a stored procedure
> that uses SQL Mail, which is a different SQL Server feature. Use
> sp_send_dbmail instead. Look BOL for more details and examples.
> Make sure you really configured Database Mail, right-click Database Mail a=nd
> select 'Send Test E-mail' to test that it works.
> By the way, SQL Mail, according to BOL, will be removed in a future versio=n
> of SQL Server.
> Hope this helps,
> Ben Nevarez
>
> "mohit" wrote:
> > Hi All,
> > =A0 =A0 =A0 =A0I am using SQL SERVER 2005 Standard Edition. I have enabl=ed
> > database mail from Surface Area Configuration and also configured
> > database mail from Object Explorer ->management.
> > =A0 =A0 =A0 =A0When i am trying to send mail by using extended stored
> > procedure xp_sendmail i am getting error as follows:
> > =A0 =A0 xp_sendmail: Procedure expects parameter @.user, which was not
> > supplied.
> > =A0 =A0 =A0It will be a great help if you guys can help me.
> > =A0 =A0 =A0Thanks in advance.- Hide quoted text -
> - Show quoted text -
Hi,
Thanks a lot. It helped me a lot.
Monday, March 19, 2012
Error in Reporting Services Configuration Manager
Hello
I've got an error when I want to initialize the Report Server by means of RS Configuration Manager.
All points are check in green except "Encryption Keys" that is in "Optionnal configuration" and "Initialization" that is in "Not Configured".
When I click on "Initialization" an error occured :
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable)
When I want to browse the report this error occured:
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) (rsRPCError). Cannot generate SSPI context.
Someone can help me ?
Thanks
Arnaud
I am having the same problem.
|||First make sure you have correctly entered and apply the information on the "database setup" panel. I think the "Cannot generate SSPI context" error may contain a clue. A quick search found the following kb: http://support.microsoft.com/?id=811889. Let us know if it helps.Error in Reporting Services Configuration Manager
Hello
I've got an error when I want to initialize the Report Server by means of RS Configuration Manager.
All points are check in green except "Encryption Keys" that is in "Optionnal configuration" and "Initialization" that is in "Not Configured".
When I click on "Initialization" an error occured :
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable)
When I want to browse the report this error occured:
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) (rsRPCError). Cannot generate SSPI context.
Someone can help me ?
Thanks
Arnaud
I am having the same problem.
|||First make sure you have correctly entered and apply the information on the "database setup" panel. I think the "Cannot generate SSPI context" error may contain a clue. A quick search found the following kb: http://support.microsoft.com/?id=811889. Let us know if it helps.
Sunday, March 11, 2012
Error in one on RS2KSampleReports.sln
Hi RS Support team,
Have downloaded the RS2KSampleReports.zip and found that there is a small problem with the configuration of the table object in MDX_Expression.rdl. For example if you run the report for Vancouver the resultant report will be 21 pages long. The Product Category gets split over multiple pages instead of showing all the product categories on one page. Took me a while to figure out but I fixed the problem by changing the table1_Group2 group to a Group Header â' originally it had been defined as a Group Footer while table1_Group1 was already a Group Header.
I think this kind of problem may have been similar to the one that Jesse O asked about in his post â'Weird Page Break Issuesâ' a couple of months ago.
Just wanted to let you knowâ?¦
--
Cheers,
NickJust a correction to that previous post - it was RS2KOLAPSampleReports.zip that has the problem
--
Cheers,
Nick
"NickB" wrote:
> Hi RS Support team,
> Have downloaded the RS2KSampleReports.zip and found that there is a small problem with the configuration of the table object in MDX_Expression.rdl. For example if you run the report for Vancouver the resultant report will be 21 pages long. The Product Category gets split over multiple pages instead of showing all the product categories on one page. Took me a while to figure out but I fixed the problem by changing the table1_Group2 group to a Group Header â' originally it had been defined as a Group Footer while table1_Group1 was already a Group Header.
> I think this kind of problem may have been similar to the one that Jesse O asked about in his post â'Weird Page Break Issuesâ' a couple of months ago.
> Just wanted to let you knowâ?¦
> --
> Cheers,
> Nick
Have downloaded the RS2KSampleReports.zip and found that there is a small problem with the configuration of the table object in MDX_Expression.rdl. For example if you run the report for Vancouver the resultant report will be 21 pages long. The Product Category gets split over multiple pages instead of showing all the product categories on one page. Took me a while to figure out but I fixed the problem by changing the table1_Group2 group to a Group Header â' originally it had been defined as a Group Footer while table1_Group1 was already a Group Header.
I think this kind of problem may have been similar to the one that Jesse O asked about in his post â'Weird Page Break Issuesâ' a couple of months ago.
Just wanted to let you knowâ?¦
--
Cheers,
NickJust a correction to that previous post - it was RS2KOLAPSampleReports.zip that has the problem
--
Cheers,
Nick
"NickB" wrote:
> Hi RS Support team,
> Have downloaded the RS2KSampleReports.zip and found that there is a small problem with the configuration of the table object in MDX_Expression.rdl. For example if you run the report for Vancouver the resultant report will be 21 pages long. The Product Category gets split over multiple pages instead of showing all the product categories on one page. Took me a while to figure out but I fixed the problem by changing the table1_Group2 group to a Group Header â' originally it had been defined as a Group Footer while table1_Group1 was already a Group Header.
> I think this kind of problem may have been similar to the one that Jesse O asked about in his post â'Weird Page Break Issuesâ' a couple of months ago.
> Just wanted to let you knowâ?¦
> --
> Cheers,
> Nick
Subscribe to:
Posts (Atom)