Missing dll file: upgraded

Showing posts with label upgraded. Show all posts

Monday, March 26, 2012

mobsync.exe errors after installing sql server sp3a

Server : w2k server sp4
Tablet : w2k sp4
Sql Server 2000

A few days ago we upgraded our servers and tablet pc's with sql server sp3a. At the same time we also changed the publisher and it now uses a static filter to reduce the number of records in the tablet database. Since we have done this we have been getting an error message when we try to synchronize via the windows synchronization manager on our tablet pc's. The error message is "mobsync.exe has generated errors and will be closed by windows. You will need to restart the program. I looked up the error message and it is a stack overflow. This does not happen every time but about 50% of the time. We can always sync from within enterprise manager and everything works fine every time.

If any one has any ideas I would greatly appreciate it and thank you in advance.Check thru event viewer for further information and see any other applications are affected such as IE.

What was the previous version of service pack on SQL?|||Satya I checked the application and system logs and there doesn't seem to be anything in them around the times of the failures. However I did find a DrWatson log and after reviewing it I noticed that the problem was there before we installed sp3a. We upgraded from sp2. I noticed that this problem started happening when I changed the publication to use a static filter. We set up the filter on one table on a few fields in the table and this is applied to foreign keys in other tables. The filter is on a job table and we filter on iProcessedFlag < 2 AND sdtDateIn >= '1/1/2003' AND sdtDateFinished IS NULL AND iJobNumber > 5999. The processedflag and the sdtDateFinished signify whether the job is finished or not. This filter is then applied to other tables in the database based on foreign key job_id. There about 8 foreign key linked tables. If you have any ideas why this filter is causing problems point me in the correct direction. This is the same filter that we use on our PDA publication and it works fine although it goes through a different replication mechanism.|||Just wanted to let everyone know the findings on this problem. I had to contact Microsoft after I discovered that it was not sp3 that was causing the problem but was actually the filter that I started using on the publication. There was nothing wrong with the filter, it was a Microsoft problem dealing with the filter. They send me a hot fix to put on each of the units that was experiencing the problem but only time will tell if the problem is fixed. This problem does not happen when you sync from Enterprise Magager, only when you sync from Windows Synchronization Manager. I guess as a last note, Microsoft has known about this problem for a year now but did not do enough testing of it to get it into sp3. I guess that we will have to wait until sp4 comes out or the next version of Sql Server.

Monday, March 12, 2012

missing tables

I upgraded SQL Server 2000 with 2005 Developer. Now, I have only 6 system
tables in the master database. All the others disappeared. I need them for
running my old stored procedures. Do I have to reinstall 2000 to get back
the functionality?
AntoninWhat we used to call system tables are not implemented as views. Read in Books Online about
"compatibility views".
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Antonin" <antonin@.comphub.com> wrote in message news:uoQXFfwgHHA.1244@.TK2MSFTNGP04.phx.gbl...
>I upgraded SQL Server 2000 with 2005 Developer. Now, I have only 6 system tables in the master
>database. All the others disappeared. I need them for running my old stored procedures. Do I have
>to reinstall 2000 to get back the functionality?
> Antonin
>|||Thanks Tibor,
I can not find any how to fix this:
'Invalid object name 'master.dbo.sysxlogins'
Antonin
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uZKmhnxgHHA.4892@.TK2MSFTNGP03.phx.gbl...
> What we used to call system tables are not implemented as views. Read in
> Books Online about "compatibility views".
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Antonin" <antonin@.comphub.com> wrote in message
> news:uoQXFfwgHHA.1244@.TK2MSFTNGP04.phx.gbl...
>>I upgraded SQL Server 2000 with 2005 Developer. Now, I have only 6 system
>>tables in the master database. All the others disappeared. I need them for
>>running my old stored procedures. Do I have to reinstall 2000 to get back
>>the functionality?
>> Antonin
>|||When you use undocumented features in a product you need to expect things like these. Sysxlogins
wasn't documented.
The old system tables (what was documented) are now called compatibility views. The new views has a
high degree of backwards compatibility, but again for what was documented in the first plans. These
are meant for backwards compatibility and the replacement are the new catalog views.
So, you need to go through your code and find what code uses old undocumented stuff, and fix it
before it will run (well) on 2005.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Antonin" <antonin@.comphub.com> wrote in message news:%23cXL6rygHHA.4992@.TK2MSFTNGP06.phx.gbl...
> Thanks Tibor,
> I can not find any how to fix this:
> 'Invalid object name 'master.dbo.sysxlogins'
> Antonin
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:uZKmhnxgHHA.4892@.TK2MSFTNGP03.phx.gbl...
>> What we used to call system tables are not implemented as views. Read in Books Online about
>> "compatibility views".
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Antonin" <antonin@.comphub.com> wrote in message news:uoQXFfwgHHA.1244@.TK2MSFTNGP04.phx.gbl...
>>I upgraded SQL Server 2000 with 2005 Developer. Now, I have only 6 system tables in the master
>>database. All the others disappeared. I need them for running my old stored procedures. Do I have
>>to reinstall 2000 to get back the functionality?
>> Antonin
>>
>|||> When you use undocumented features in a product you need to expect things
> like these. Sysxlogins wasn't documented.
Sadly, though, Microsoft does talk about it in their documentation. In SQL
Server 2000 Books Online, look at these topics:
Resolving Permission Conflicts
SQL Profiler Data Columns
And in 2005, there is a topic (Breaking Changes to Database Engine Features
in SQL Server 2005, ironically!) that says:
<snip>
You can identify dormant SQL Server 6.5 logins by using the following query:
SELECT * FROM sysxlogins WHERE (xstatus & 2048) = 2048;
</snip>
They corrected a similar issue I brought up on connect a while back, where
sp_who2 was mentioned in a single Books Online article. I just entered a
new one for this omission, which will at least correct the 2005 issue.
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=272245|||I found somewhere that I should use syslogins view in 2005 instead of
sysxlogins. Now I get when running this
SELECT 'ServerRole' = A.name, 'MemberName' = B.name
FROM master.dbo.spt_values A, master.dbo.syslogins B
WHERE A.low = 0
AND A.type = 'SRV'
AND B.srvid IS NULL
AND A.number & B.xstatus = A.number
Server: Msg 207, Level 16, State 1, Line 6
Invalid column name 'srvid'.
Server: Msg 207, Level 16, State 1, Line 7
Invalid column name 'xstatus'.
Where can I find the mappings between sysxlogins and syslogins columns?
Antonin
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%239yaPC1gHHA.4872@.TK2MSFTNGP03.phx.gbl...
>> When you use undocumented features in a product you need to expect things
>> like these. Sysxlogins wasn't documented.
> Sadly, though, Microsoft does talk about it in their documentation. In
> SQL Server 2000 Books Online, look at these topics:
> Resolving Permission Conflicts
> SQL Profiler Data Columns
> And in 2005, there is a topic (Breaking Changes to Database Engine
> Features in SQL Server 2005, ironically!) that says:
> <snip>
> You can identify dormant SQL Server 6.5 logins by using the following
> query:
> SELECT * FROM sysxlogins WHERE (xstatus & 2048) = 2048;
> </snip>
> They corrected a similar issue I brought up on connect a while back, where
> sp_who2 was mentioned in a single Books Online article. I just entered a
> new one for this omission, which will at least correct the 2005 issue.
> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=272245
>|||"Antonin" <Antonin.Koudelka@.fmc.sa.gov.au> wrote in message
news:%23Sm1vyVhHHA.1240@.TK2MSFTNGP04.phx.gbl...
>I found somewhere that I should use syslogins view in 2005 instead of
>sysxlogins. Now I get when running this
> SELECT 'ServerRole' = A.name, 'MemberName' = B.name
> FROM master.dbo.spt_values A, master.dbo.syslogins B
> WHERE A.low = 0
> AND A.type = 'SRV'
> AND B.srvid IS NULL
> AND A.number & B.xstatus = A.number
> Server: Msg 207, Level 16, State 1, Line 6
> Invalid column name 'srvid'.
> Server: Msg 207, Level 16, State 1, Line 7
> Invalid column name 'xstatus'.
> Where can I find the mappings between sysxlogins and syslogins columns?
Perhaps you can tell us what you're trying to do and someone can suggest a
better way to do that in SQL 2005.
In general, any time you mess with system tables, you risk running into
issues like this.
> Antonin
>
> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in
> message news:%239yaPC1gHHA.4872@.TK2MSFTNGP03.phx.gbl...
>> When you use undocumented features in a product you need to expect
>> things like these. Sysxlogins wasn't documented.
>> Sadly, though, Microsoft does talk about it in their documentation. In
>> SQL Server 2000 Books Online, look at these topics:
>> Resolving Permission Conflicts
>> SQL Profiler Data Columns
>> And in 2005, there is a topic (Breaking Changes to Database Engine
>> Features in SQL Server 2005, ironically!) that says:
>> <snip>
>> You can identify dormant SQL Server 6.5 logins by using the following
>> query:
>> SELECT * FROM sysxlogins WHERE (xstatus & 2048) = 2048;
>> </snip>
>> They corrected a similar issue I brought up on connect a while back,
>> where sp_who2 was mentioned in a single Books Online article. I just
>> entered a new one for this omission, which will at least correct the 2005
>> issue.
>> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=272245
>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Below is the whole code. I inherited this. It runs a security report every
morning at six o'clock. I tried to work out what it is doing by running it.
However, I was not able to do it. I thing that there are some much smarter
guys than I am in this group and for them it would be obvious. I know,
everybody has other things to do than debugging someone else's code.
Nevertheless I would appreciate help. Thank you.
Antonin
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO
CREATE PROCEDURE dbo.usp_GenerateSecurityReport
AS
SET NOCOUNT ON
PRINT 'SERVER: ' + CAST(SERVERPROPERTY('servername') AS Varchar) + '\' +
ISNULL(CONVERT(char(20),SERVERPROPERTY('InstanceName')),'DEFAULT')
PRINT ''
PRINT 'Server Role members'
PRINT ''
SELECT 'ServerRole' = A.name, 'MemberName' = B.name
FROM master.dbo.spt_values A, master.dbo.sysxlogins B
WHERE A.low = 0
AND A.type = 'SRV'
AND B.srvid IS NULL
AND A.number & B.xstatus = A.number
PRINT ''
PRINT 'Database Role members'
PRINT ''
DECLARE curSecurity CURSOR FAST_FORWARD FOR
SELECT [name] FROM master..sysdatabases
DECLARE @.vchName varchar(50)
DECLARE @.vchSQL varchar(3000)
OPEN curSecurity
FETCH NEXT FROM curSecurity INTO @.vchName
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'Database Name: ' + @.vchName
PRINT ''
SET @.vchSQL = 'select substring(r.[name], 1, 30) AS RoleName,
SUBSTRING(u.[name], 1, 50) AS DB_User
from ' + @.vchName + '.dbo.sysusers r
inner join ' + @.vchName + '.dbo.sysmembers m on m.groupuid = r.uid
inner join ' + @.vchName + '.dbo.sysusers u on u.uid = m.memberuid
where r.issqlrole=1
order by 1, 2'
--print @.vchSQL
exec(@.vchSQL)
PRINT ''
FETCH NEXT FROM curSecurity INTO @.vchName
END
CLOSE curSecurity
DEALLOCATE curSecurity
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:Ooy303VhHHA.4300@.TK2MSFTNGP05.phx.gbl...
> "Antonin" <Antonin.Koudelka@.fmc.sa.gov.au> wrote in message
> news:%23Sm1vyVhHHA.1240@.TK2MSFTNGP04.phx.gbl...
>>I found somewhere that I should use syslogins view in 2005 instead of
>>sysxlogins. Now I get when running this
>> SELECT 'ServerRole' = A.name, 'MemberName' = B.name
>> FROM master.dbo.spt_values A, master.dbo.syslogins B
>> WHERE A.low = 0
>> AND A.type = 'SRV'
>> AND B.srvid IS NULL
>> AND A.number & B.xstatus = A.number
>> Server: Msg 207, Level 16, State 1, Line 6
>> Invalid column name 'srvid'.
>> Server: Msg 207, Level 16, State 1, Line 7
>> Invalid column name 'xstatus'.
>> Where can I find the mappings between sysxlogins and syslogins columns?
> Perhaps you can tell us what you're trying to do and someone can suggest a
> better way to do that in SQL 2005.
> In general, any time you mess with system tables, you risk running into
> issues like this.
>
>> Antonin
>>
>> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in
>> message news:%239yaPC1gHHA.4872@.TK2MSFTNGP03.phx.gbl...
>> When you use undocumented features in a product you need to expect
>> things like these. Sysxlogins wasn't documented.
>> Sadly, though, Microsoft does talk about it in their documentation. In
>> SQL Server 2000 Books Online, look at these topics:
>> Resolving Permission Conflicts
>> SQL Profiler Data Columns
>> And in 2005, there is a topic (Breaking Changes to Database Engine
>> Features in SQL Server 2005, ironically!) that says:
>> <snip>
>> You can identify dormant SQL Server 6.5 logins by using the following
>> query:
>> SELECT * FROM sysxlogins WHERE (xstatus & 2048) = 2048;
>> </snip>
>> They corrected a similar issue I brought up on connect a while back,
>> where sp_who2 was mentioned in a single Books Online article. I just
>> entered a new one for this omission, which will at least correct the
>> 2005 issue.
>> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=272245
>>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com
> http://www.greenms.com/sqlserver.html
>

missing tables

Missing table log_shipping_monitor table

We upgraded SQL Server from standard to enterprise edition. When attempting to setup a maintenance plan we got an error 208: Invalid object name: msdb.dbo.log_shipping_monitor.
The table log_shipping_monitor doesn't exist in the msdb database.
Any ideas?
what happens if you appy/re-apply the latest sp.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"John M. Snarski" <John M. Snarski@.discussions.microsoft.com> wrote in
message news:8C1CFC6B-49B9-44A9-8FDC-E5A463C6E1D7@.microsoft.com...
> We upgraded SQL Server from standard to enterprise edition. When
attempting to setup a maintenance plan we got an error 208: Invalid object
name: msdb.dbo.log_shipping_monitor.
> The table log_shipping_monitor doesn't exist in the msdb database.
> Any ideas?
|||no change

"Hilary Cotter" wrote:

> what happens if you appy/re-apply the latest sp.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "John M. Snarski" <John M. Snarski@.discussions.microsoft.com> wrote in
> message news:8C1CFC6B-49B9-44A9-8FDC-E5A463C6E1D7@.microsoft.com...
> attempting to setup a maintenance plan we got an error 208: Invalid object
> name: msdb.dbo.log_shipping_monitor.
>
>

Missing Subject

Hi,
last month I installed SQL Server 2000 on a new server (Install SQL2000 and
then upgraded to SP4) because that server is going to replace the main
production server. I've restored the database dumps from the old server to
the new one and did also copy the SQL Agent jobs. Also configured SQL Mail,
because there are some stored procedures that use the xp_sendmail.
Everything seems to work OK, until I noticed that the mails, sent by SQL
Mail using the xp_sendmail are all missing the subject line, whereas the
subject line is present in the mail sent by the (old) production server.
the code in the stored procedures that invoke xp_sendmail is identical on
both machines.
Am I missing something or...
--
Adri
Programmers do it Bit by BitHi
Without seeing the actual call to xp_sendmail it is hard to say, but at a
guess you are possibly concatentating to a NULL value or something similar
either because the data is different or may be CONCAT_NULL_YIELDS_NULL is
different.
John
"Adri" wrote:
> Hi,
> last month I installed SQL Server 2000 on a new server (Install SQL2000 and
> then upgraded to SP4) because that server is going to replace the main
> production server. I've restored the database dumps from the old server to
> the new one and did also copy the SQL Agent jobs. Also configured SQL Mail,
> because there are some stored procedures that use the xp_sendmail.
> Everything seems to work OK, until I noticed that the mails, sent by SQL
> Mail using the xp_sendmail are all missing the subject line, whereas the
> subject line is present in the mail sent by the (old) production server.
> the code in the stored procedures that invoke xp_sendmail is identical on
> both machines.
> Am I missing something or...
> --
> Adri
> Programmers do it Bit by Bit|||Adri skrev:
> ...
> Am I missing something or...
> ...
Actually yes, the Subject ;)|||In fact, a simple
xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message'
,@.subject = 'subject'
delivers an e-mail with an empty subject line :-(
--
Adri
Programmers do it Bit by Bit
"John Bell" wrote:
> Hi
> Without seeing the actual call to xp_sendmail it is hard to say, but at a
> guess you are possibly concatentating to a NULL value or something similar
> either because the data is different or may be CONCAT_NULL_YIELDS_NULL is
> different.
> John
> "Adri" wrote:
> > Hi,
> >
> > last month I installed SQL Server 2000 on a new server (Install SQL2000 and
> > then upgraded to SP4) because that server is going to replace the main
> > production server. I've restored the database dumps from the old server to
> > the new one and did also copy the SQL Agent jobs. Also configured SQL Mail,
> > because there are some stored procedures that use the xp_sendmail.
> >
> > Everything seems to work OK, until I noticed that the mails, sent by SQL
> > Mail using the xp_sendmail are all missing the subject line, whereas the
> > subject line is present in the mail sent by the (old) production server.
> >
> > the code in the stored procedures that invoke xp_sendmail is identical on
> > both machines.
> >
> > Am I missing something or...
> > --
> > Adri
> > Programmers do it Bit by Bit|||Hi Adri
More questions...
I assume you can send mail successfully from Outlook with a subject? if the
subject parameter is before the message parameter does it work? Is this 32 or
64 bit?
John
"Adri" wrote:
> In fact, a simple
> xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message'
> ,@.subject = 'subject'
> delivers an e-mail with an empty subject line :-(
> --
> Adri
> Programmers do it Bit by Bit
>
> "John Bell" wrote:
> > Hi
> >
> > Without seeing the actual call to xp_sendmail it is hard to say, but at a
> > guess you are possibly concatentating to a NULL value or something similar
> > either because the data is different or may be CONCAT_NULL_YIELDS_NULL is
> > different.
> >
> > John
> >
> > "Adri" wrote:
> >
> > > Hi,
> > >
> > > last month I installed SQL Server 2000 on a new server (Install SQL2000 and
> > > then upgraded to SP4) because that server is going to replace the main
> > > production server. I've restored the database dumps from the old server to
> > > the new one and did also copy the SQL Agent jobs. Also configured SQL Mail,
> > > because there are some stored procedures that use the xp_sendmail.
> > >
> > > Everything seems to work OK, until I noticed that the mails, sent by SQL
> > > Mail using the xp_sendmail are all missing the subject line, whereas the
> > > subject line is present in the mail sent by the (old) production server.
> > >
> > > the code in the stored procedures that invoke xp_sendmail is identical on
> > > both machines.
> > >
> > > Am I missing something or...
> > > --
> > > Adri
> > > Programmers do it Bit by Bit|||Adri wrote:
> In fact, a simple
> xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message'
> ,@.subject = 'subject'
> delivers an e-mail with an empty subject line :-(
> --
> Adri
> Programmers do it Bit by Bit
*bonk*
Sorry for my pityful attempt of being funny :) I actually didn't read
your post carefully enough and didn't realize your problem was really
'Missing Subject', not that some client added that as a subject for
your post (that you had sent without a subject)... Ahem...
Btw, did you do a search on Google, I saw a lot of hits using
"xp_sendmail" and "subject" as search parameters even though I didn't
instantly find a solution for the problem...
/impslayer, aka Birger Johansson|||Hi Adri,
My understanding of your issue is:
After the migration of SQL Server 2000 from an older server to a new one,
you can also send email by xp_sendmail in your stored procedures,however
those sent mails' subjects are missed.
If I have misunderstood, please let me know.
I recommend that you try the following:
1) Login as account that is running SQL Server server and open outlook.
2) Tools->Options->Mail Format tab. Change the "compose in message format"
to plan
text and send an email through outlook with a subject.
3) Change the "compose in message format" back to html. Send email with
subject.
Stop and start SQL Server instance might be necessary.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hi Charles,
In fact, I did a new installation of SQL 2000 on a W2K3 server and upgraded
SQL from RTM to SP4. Having done that, I restored the (user)database dumps
from the old server to the new one, and configured SQL Mail as usual.
The old server had originally SQL 2000 RTM installed, upgraded to SP2, SP3,
Hotfix KB891640 applied and at last upgraded to SP4.
I've changed the Mail Format as you supposed, but that did not help.
--
Adri
Programmers do it Bit by Bit
"Charles Wang[MSFT]" wrote:
> Hi Adri,
> My understanding of your issue is:
> After the migration of SQL Server 2000 from an older server to a new one,
> you can also send email by xp_sendmail in your stored procedures,however
> those sent mails' subjects are missed.
> If I have misunderstood, please let me know.
> I recommend that you try the following:
> 1) Login as account that is running SQL Server server and open outlook.
> 2) Tools->Options->Mail Format tab. Change the "compose in message format"
> to plan
> text and send an email through outlook with a subject.
> 3) Change the "compose in message format" back to html. Send email with
> subject.
> Stop and start SQL Server instance might be necessary.
> Sincerely yours,
> Charles Wang
> Microsoft Online Community Support
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>|||Like saying "This page is intentionally blank"!!!
John
"impslayer" wrote:
> Adri wrote:
> > In fact, a simple
> >
> > xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message'
> > ,@.subject = 'subject'
> >
> > delivers an e-mail with an empty subject line :-(
> >
> > --
> > Adri
> > Programmers do it Bit by Bit
> *bonk*
> Sorry for my pityful attempt of being funny :) I actually didn't read
> your post carefully enough and didn't realize your problem was really
> 'Missing Subject', not that some client added that as a subject for
> your post (that you had sent without a subject)... Ahem...
> Btw, did you do a search on Google, I saw a lot of hits using
> "xp_sendmail" and "subject" as search parameters even though I didn't
> instantly find a solution for the problem...
> /impslayer, aka Birger Johansson
>|||Hi Adri,
To make sure this is a dabase wide issue or server instance side issue, I
recommend that you create a new stored procedure with xp_sendmail in a test
database and see whether or not it has the same issue.
Also, you may try recompiling the stored procedures.
Charles Wang
Microsoft Online Community Support|||Hi
Please clarify that using Outlook directly is working ok?
Which version of office is being used?
John
"Adri" wrote:
> Hi Charles,
> In fact, I did a new installation of SQL 2000 on a W2K3 server and upgraded
> SQL from RTM to SP4. Having done that, I restored the (user)database dumps
> from the old server to the new one, and configured SQL Mail as usual.
> The old server had originally SQL 2000 RTM installed, upgraded to SP2, SP3,
> Hotfix KB891640 applied and at last upgraded to SP4.
> I've changed the Mail Format as you supposed, but that did not help.
> --
> Adri
> Programmers do it Bit by Bit
>
> "Charles Wang[MSFT]" wrote:
> > Hi Adri,
> >
> > My understanding of your issue is:
> > After the migration of SQL Server 2000 from an older server to a new one,
> > you can also send email by xp_sendmail in your stored procedures,however
> > those sent mails' subjects are missed.
> > If I have misunderstood, please let me know.
> >
> > I recommend that you try the following:
> > 1) Login as account that is running SQL Server server and open outlook.
> > 2) Tools->Options->Mail Format tab. Change the "compose in message format"
> > to plan
> > text and send an email through outlook with a subject.
> > 3) Change the "compose in message format" back to html. Send email with
> > subject.
> >
> > Stop and start SQL Server instance might be necessary.
> >
> > Sincerely yours,
> > Charles Wang
> > Microsoft Online Community Support
> > ======================================================> > When responding to posts, please "Reply to Group" via
> > your newsreader so that others may learn and benefit
> > from this issue.
> > ======================================================> > This posting is provided "AS IS" with no warranties, and confers no rights.
> > ======================================================> >
> >
> >

Missing Subject

I actually didn't read
your post carefully enough and didn't realize your problem was really
'Missing Subject', not that some client added that as a subject for
your post (that you had sent without a subject)... Ahem...
Btw, did you do a search on Google, I saw a lot of hits using
"xp_sendmail" and "subject" as search parameters even though I didn't
instantly find a solution for the problem...
/impslayer, aka Birger Johansson|||Hi Adri,
My understanding of your issue is:
After the migration of SQL Server 2000 from an older server to a new one,
you can also send email by xp_sendmail in your stored procedures,however
those sent mails' subjects are missed.
If I have misunderstood, please let me know.
I recommend that you try the following:
1) Login as account that is running SQL Server server and open outlook.
2) Tools->Options->Mail Format tab. Change the "compose in message format"
to plan
text and send an email through outlook with a subject.
3) Change the "compose in message format" back to html. Send email with
subject.
Stop and start SQL Server instance might be necessary.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Hi Charles,
In fact, I did a new installation of SQL 2000 on a W2K3 server and upgraded
SQL from RTM to SP4. Having done that, I restored the (user)database dumps
from the old server to the new one, and configured SQL Mail as usual.
The old server had originally SQL 2000 RTM installed, upgraded to SP2, SP3,
Hotfix KB891640 applied and at last upgraded to SP4.
I've changed the Mail Format as you supposed, but that did not help.
--
Adri
Programmers do it Bit by Bit
"Charles Wang[MSFT]" wrote:

> Hi Adri,
> My understanding of your issue is:
> After the migration of SQL Server 2000 from an older server to a new one,
> you can also send email by xp_sendmail in your stored procedures,however
> those sent mails' subjects are missed.
> If I have misunderstood, please let me know.
> I recommend that you try the following:
> 1) Login as account that is running SQL Server server and open outlook.
> 2) Tools->Options->Mail Format tab. Change the "compose in message format"
> to plan
> text and send an email through outlook with a subject.
> 3) Change the "compose in message format" back to html. Send email with
> subject.
> Stop and start SQL Server instance might be necessary.
> Sincerely yours,
> Charles Wang
> Microsoft Online Community Support
> ========================================
==============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>|||Like saying "This page is intentionally blank"!!!
John
"impslayer" wrote:

> Adri wrote:
> *bonk*
> Sorry for my pityful attempt of being funny

I actually didn't read
> your post carefully enough and didn't realize your problem was really
> 'Missing Subject', not that some client added that as a subject for
> your post (that you had sent without a subject)... Ahem...
> Btw, did you do a search on Google, I saw a lot of hits using
> "xp_sendmail" and "subject" as search parameters even though I didn't
> instantly find a solution for the problem...
> /impslayer, aka Birger Johansson
>|||Hi Adri,
To make sure this is a dabase wide issue or server instance side issue, I
recommend that you create a new stored procedure with xp_sendmail in a test
database and see whether or not it has the same issue.
Also, you may try recompiling the stored procedures.
Charles Wang
Microsoft Online Community Support

Monday, March 26, 2012

mobsync.exe errors after installing sql server sp3a

Monday, March 12, 2012

missing tables

missing tables

missing tables

Missing table log_shipping_monitor table

Missing Subject

Missing Subject

Missing dll file

Blog Archive

About Me