"The Return of the bugs"

Hello "precious" developers of Microsoft SQL Server 2000.
Huge bugs are performed when:
1) sp4 has applied for my default instance (developer edition)
2) everytime I setup a new named instance (MSDE Last release) a letter from
the registry key SQLPath (located under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL
Server\80\Tools\ClientSetup) is erased from the end. For example, the SQLPat
h
value must be "C:\Program Files\Microsoft SQL Server\80\Tools", I setup an
instance, SQLPath value becomes "C:\Program Files\Microsoft SQL
Server\80\Tool", I setup another and the SQLPath value becomes "C:\Program
Files\Microsoft SQL Server\80\Too".
Nice haa!?!? The other bug that occurs from the first msde setup is that you
can't anymore uninstall your default instance (dev. edition). The error
message says that the Uninst.isu is corrupted... (maybe reads the corrupted
path from SQLPath reg. key).
Please feel free to inform me if I'm wrong!
RegardsHi
Have you contacted Microsoft PSS and reported these issues?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"x-rays" wrote:

> Hello "precious" developers of Microsoft SQL Server 2000.
> Huge bugs are performed when:
> 1) sp4 has applied for my default instance (developer edition)
> 2) everytime I setup a new named instance (MSDE Last release) a letter fro
m
> the registry key SQLPath (located under
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL
> Server\80\Tools\ClientSetup) is erased from the end. For example, the SQLP
ath
> value must be "C:\Program Files\Microsoft SQL Server\80\Tools", I setup an
> instance, SQLPath value becomes "C:\Program Files\Microsoft SQL
> Server\80\Tool", I setup another and the SQLPath value becomes "C:\Program
> Files\Microsoft SQL Server\80\Too".
> Nice haa!?!? The other bug that occurs from the first msde setup is that y
ou
> can't anymore uninstall your default instance (dev. edition). The error
> message says that the Uninst.isu is corrupted... (maybe reads the corrupte
d
> path from SQLPath reg. key).
> Please feel free to inform me if I'm wrong!
> Regards|||Hello Mike, No, how to contact them?
Ο χρ?στη? "Mike Epprecht (SQL MVP)" _γγραψε:
> Hi
> Have you contacted Microsoft PSS and reported these issues?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "x-rays" wrote:
>|||I' ll call them tomorrow.
Regards
Ο χρ?στη? "Mike Epprecht (SQL MVP)" _γγραψε:
> Hi
> Have you contacted Microsoft PSS and reported these issues?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "x-rays" wrote:
>|||http://support.microsoft.com/gp/assistsupport
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"x-rays" wrote:
> Hello Mike, No, how to contact them?
> Ο χρ?στη? "Mike Epprecht (SQL MVP)" _γγραψε:
>

"SQLServerAgent service hung on starting"

Since I installed sp4 for sql7 on 3 NT-machines last week, I get this message from Service Control Manager on every reboot of those PC's. After checking in the NT EventViewer, the SQLServerAgent service is really started but about 15-20 seconds after the error message.

EventID 7022
SERVICE CONTROL MANAGER
"SQLServerAgent service hung on starting"

Any idea how to solve this or what causes this?Take a look at your SQL Error log. SQL Server Agent will not be able to start unless the error log shows 'Recovery Complete'.|||Check your odbc administrator -> tracing -> check to see if it is enabled (if it is, stop the tracing).|||Thanks for your replies. Problem solved, the error message was caused because I also disabled the Messenger service (for security reasons). Now I enabled it again & the SQGAgent Service starts on reboot without the error warning. I still wonder why because I don't like leaving the Messenger service running.

"Simple" recovery model?

SQL 2000 SP3a on W2K SP4 server. I've created a new database with only three
tables and set the Recovery Model to Simple. The reason being, these tables
are essentially "temp" tables who's data will be constantly deleted and
re-inserted. Since it is all calculated data, I have no need for recovery of
any kind. My problem is this: Even with the Recovery Model set to Simple,
the Transaction Log grows exponentially. This is a real problem for me since
these tables may be emptied and re-populated 1,500 times in one evening.
What recovery model should I use in this situation in order to keep the Log
file size under control? Or should I just run SHRINKDATABASE or some other
utility after each cleaning?
Hi
Keep your transactions short and sweet. If it is all one transaction, and
you update 10 million rows, you will need a lot of space.
Shrink DB will not help unless the transaction is committed or rolled back.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ron Hinds" <__ron__dontspamme@.wedontlikespam_garageiq.com> wrote in message
news:O5ijLRPAGHA.3136@.TK2MSFTNGP15.phx.gbl...
> SQL 2000 SP3a on W2K SP4 server. I've created a new database with only
> three
> tables and set the Recovery Model to Simple. The reason being, these
> tables
> are essentially "temp" tables who's data will be constantly deleted and
> re-inserted. Since it is all calculated data, I have no need for recovery
> of
> any kind. My problem is this: Even with the Recovery Model set to Simple,
> the Transaction Log grows exponentially. This is a real problem for me
> since
> these tables may be emptied and re-populated 1,500 times in one evening.
> What recovery model should I use in this situation in order to keep the
> Log
> file size under control? Or should I just run SHRINKDATABASE or some other
> utility after each cleaning?
>

"Simple" recovery model?

SQL 2000 SP3a on W2K SP4 server. I've created a new database with only three
tables and set the Recovery Model to Simple. The reason being, these tables
are essentially "temp" tables who's data will be constantly deleted and
re-inserted. Since it is all calculated data, I have no need for recovery of
any kind. My problem is this: Even with the Recovery Model set to Simple,
the Transaction Log grows exponentially. This is a real problem for me since
these tables may be emptied and re-populated 1,500 times in one evening.
What recovery model should I use in this situation in order to keep the Log
file size under control? Or should I just run SHRINKDATABASE or some other
utility after each cleaning?Hi
Keep your transactions short and sweet. If it is all one transaction, and
you update 10 million rows, you will need a lot of space.
Shrink DB will not help unless the transaction is committed or rolled back.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ron Hinds" < __ron__dontspamme@.wedontlikespam_garagei
q.com> wrote in message
news:O5ijLRPAGHA.3136@.TK2MSFTNGP15.phx.gbl...
> SQL 2000 SP3a on W2K SP4 server. I've created a new database with only
> three
> tables and set the Recovery Model to Simple. The reason being, these
> tables
> are essentially "temp" tables who's data will be constantly deleted and
> re-inserted. Since it is all calculated data, I have no need for recovery
> of
> any kind. My problem is this: Even with the Recovery Model set to Simple,
> the Transaction Log grows exponentially. This is a real problem for me
> since
> these tables may be emptied and re-populated 1,500 times in one evening.
> What recovery model should I use in this situation in order to keep the
> Log
> file size under control? Or should I just run SHRINKDATABASE or some other
> utility after each cleaning?
>

"Simple" recovery model?

SQL 2000 SP3a on W2K SP4 server. I've created a new database with only three
tables and set the Recovery Model to Simple. The reason being, these tables
are essentially "temp" tables who's data will be constantly deleted and
re-inserted. Since it is all calculated data, I have no need for recovery of
any kind. My problem is this: Even with the Recovery Model set to Simple,
the Transaction Log grows exponentially. This is a real problem for me since
these tables may be emptied and re-populated 1,500 times in one evening.
What recovery model should I use in this situation in order to keep the Log
file size under control? Or should I just run SHRINKDATABASE or some other
utility after each cleaning?Hi
Keep your transactions short and sweet. If it is all one transaction, and
you update 10 million rows, you will need a lot of space.
Shrink DB will not help unless the transaction is committed or rolled back.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ron Hinds" <__ron__dontspamme@.wedontlikespam_garageiq.com> wrote in message
news:O5ijLRPAGHA.3136@.TK2MSFTNGP15.phx.gbl...
> SQL 2000 SP3a on W2K SP4 server. I've created a new database with only
> three
> tables and set the Recovery Model to Simple. The reason being, these
> tables
> are essentially "temp" tables who's data will be constantly deleted and
> re-inserted. Since it is all calculated data, I have no need for recovery
> of
> any kind. My problem is this: Even with the Recovery Model set to Simple,
> the Transaction Log grows exponentially. This is a real problem for me
> since
> these tables may be emptied and re-populated 1,500 times in one evening.
> What recovery model should I use in this situation in order to keep the
> Log
> file size under control? Or should I just run SHRINKDATABASE or some other
> utility after each cleaning?
>

"File not in a recognizeable format" when rendering to excel

I am using a WinXP SP2 machine with SQL2000 SP4, and using Reporting
Services SP2 when I get "File not in a recognizeable format" when
rendering to excel. Same goes for trying to render to PDF.
The weird thing is that on a virtual I have with Reporting Services
RTM, the excel opens fine...so I don't know what is going on.
The way I am generating the report is by manually creating a
request/response, adding on the POST vars, and then writing the output
to the browser (changing the content-type to excel, pdf, etc). As I
said, with the RTM version, the excel generates fine, but with SP2 it
doesnt.
Here are the parameters that I am adding onto the URL when I make the
request, along with my custom params.
//SQL REPORTING SERVICES SPECIAL PARAMS
sb.Append("&rs:Command=Render");
sb.Append("&rs:Format=" + exportType);
sb.Append("&rc:Parameters=false");
sb.Append("&rc:Toolbar=false&rs:Encoding=ASCII&rc:NoHeader=true");
I then I generate and return the request with the code below
(GeneratePostData() basically just creates the POST vars from above)
public static string generateReport(string url)
{
String result = "";
//get the data to post.
string postData = GeneratePostData();
System.IO.StreamWriter myWriter = null;
HttpWebRequest objRequest = (HttpWebRequest)WebRequest.Create(url);
objRequest.PreAuthenticate = true;
// Way 1:
//objRequest.Credentials = CredentialCache.DefaultCredentials;
// Way 2:
objRequest.Credentials = new
NetworkCredential(REPORT_USER,REPORT_PASS,REPORT_DOMAIN);
objRequest.Method = "POST";
objRequest.ContentLength = postData.Length;
objRequest.ContentType = "application/x-www-form-urlencoded";
try
{
myWriter = new
System.IO.StreamWriter(objRequest.GetRequestStream());
myWriter.Write(postData);
}
catch (Exception e)
{
return e.Message;
}
finally
{
myWriter.Close();
}
try
{
HttpWebResponse objResponse = (HttpWebResponse)objRequest.GetResponse();
using(System.IO.StreamReader sr = new
System.IO.StreamReader(objResponse.GetResponseStream()) )
{
result = sr.ReadToEnd();
// Close and clean up the StreamReader
sr.Close();
}
}
catch (Exception e)
{
return "An error occured while generating your report.\n" +
e.Message;
}
return result;
}
anyone have any ideas/things I can try because I am at a loss. Thanks
in advance.I figured out my problem.
I was taking the stream reader and passing the results back to the
output stream and writing it out just using Response.Write. This
worked fine for Reporting Svcs RTM, but NOT for SP2.
After going through various postings, I gather a few ways that others
did similar web request/response calls and found that if I just passed
the raw response stream and wrote it out with
Response.outputstream.write that it worked for BOTH RTM and SP2..
System.IO.Stream rs =ReportBuilder.generateReportStream(ReportBuilder.ReportViewerFullPath);
Byte[] read = new Byte[1024];
int count = rs.Read(read, 0, read.Length);
while(count > 0)
{
Response.OutputStream.Write(read, 0, count);
count = rs.Read(read, 0, count);
}

"...could not load DCOM"

Hello.
I have the same problem.
Version is
Microsoft SQL Server 2000 - 8.00.2039 - Service Pack 4 installed.
Before installation SP4 I had error "Unexpected NULL value returned for
column '[OpenXML].OutSourcedPartCount' from the OLE DB provider
'OpenXML'. This column cannot be NULL." when I didn't specified values
(no XML branches) for columns with default values.
Any ideas?
Zevakov Andrew
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message184753.htmlI can add that in event viewer I have such entries after calling my
stored proc :
Source: MSSQLSERVER
"Failed to Initialize COM (CoInitializeEx returned 80010119)"
"Heterogeneous Queries and Remote RPC will be disabled."
Zevakov Andrew
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message184753.html

Hello All,

I have an SQL 2000 sp4 default instance.
On windows server 2003 sp2 machine that is joined to a domain.
This windows is not the domain controller.

There is a domain account domain\user.
This domain account is a member of the Administrators group locally in the windows.
Also this domain account is a member of SysAdmin fixed server role of the SQL Server instance.
The MSSQLSERVER service is logged in by this domain account.
The SQLSERVERAGENT service is also logged in by this domain account.

Office 2007 (including outlook 2003) is installed on the same windows server machine that SQL resides in.

Lotus notes cloient 6.5 also installed on the same windows server machine that SQL resides in.

In Control Panel - Mail - Profiles: Outlook is the profile used.

In enterprise manager --> Support Services --> SQL Mail --> Properties --> I wrote Outlook in the profile name --> then click "Test" --> I encounter this error: "Error 18025: xp_test_mapi_profile: failed with mail error 0x80040111"

I looked at

http://support.microsoft.com/?id=263556

I could not figured it out

Any help please?

Thanks,

Ven

You need a mapi email client such as Outlook 2000.

I have around 17 SQL/Server 2000's using Domino 6.5 email accounts. Here is the scoop:

Log on to the server as the account that is used for the SQL Service account and install Outlook 2000 (with no service pack). Launch Outlook 2000 and create a mail profile that points to your Domino server. Call this email account SQLMail. Create another Outlook 2000 profile with the name SQLAgentMail and test it (this can be the same Domino account). Then log off the server and log back on using the login account that you normally run the server with. Restart SQL Server (and SQL Server Agent) and then the mapi email profiles created earlier will be available. Set SQLMail to use SQLMail profile and then set SQL Server Agent mail to use SQLAgentMail profile. That's it!

DeWayne

|||

-

|||

DeWayne,

Thanks for your help.

I have other question:

While am setting up SQLMail to use SQLMail profile and then set SQL Server Agent mail to use SQLAgentMail profile.

Receiving the following error.

Error 22022QLServerAgentError: Unable to get the default MAPI Address Book due to MAPI error 271: An error occurred while attempting to open the Window Address Book. Please specify a default mail delivery location in you profile.

If I try to create MAPI profile IBM Lotus Domino Access for Microsoft Outlook - create - new profile through getting the below error.

Failed to create new MAPI profile. Error creating personal Folders service

Note: This error can be caused by an incorrect configuration of out look 2000. If you are using outlook 2000, Please verify that is running in Corporate/Workgroup Mode.

Setup encountered an error and failed to create a MAPI profile.

You will need to reinstall IBM Lotus Domino Access for Microsoft Outlook

(Already we removed and reinstalled)

Any help please?

Ven

|||

DeWayne,

Sorry for the inconvenience,

Restarted SQL Server (and SQL Server Agent) ,the mapi email profiles created earlier still not available.

Can you please help me?

|||

Sure!

You don't need the Notes client installed on the Server at all as you will be using a POP3 email account to connect to the Domino Server (at least that is the way that I run it.)

Sign back on as the SQL Server service account then launch Outlook 2000. Click Tools, Options, click the Mail Services Tab, then click Reconfigure Mail Support and select the Corporate Workgroup option. You may have to setup the mail profile/accounts again if needed (choose POP3 when creating the mail accounts). Be sure to set Outlook to use each profile that you created and launch Outlook and click send/receive to test the email accounts.) Then logoff and sign back in as the normal Server user then restart SQL Server again...

|||

DeWayne,

Thanks you so much. It is working now.

I have other question.

we have five different sql servers.

Is it okif I use the same ( single )mail box for different profiles? instead of creating different mail box on each server?

Or does it works like a mail realy?.

Please help?

Thanks,

Ven

|||

Ven,

I create a new email account for each Server so that any emails from a SQL Server are easily identified. For example, a server named "Boston" I would create an email account named "Boston Server". If SQL is only SENDING emails then you could use one email box for everything; however, I would not want to set up my environment that way...

p.s. I am glad that everything is working correctly!!!

DeWayne

Hello All,

I have an SQL 2000 sp4 default instance.
On windows server 2003 sp2 machine that is joined to a domain.
This windows is not the domain controller.

There is a domain account domain\user.
This domain account is a member of the Administrators group locally in the windows.
Also this domain account is a member of SysAdmin fixed server role of the SQL Server instance.
The MSSQLSERVER service is logged in by this domain account.
The SQLSERVERAGENT service is also logged in by this domain account.

Office 2007 (including outlook 2003) is installed on the same windows server machine that SQL resides in.

Lotus notes cloient 6.5 also installed on the same windows server machine that SQL resides in.

In Control Panel - Mail - Profiles: Outlook is the profile used.

In enterprise manager --> Support Services --> SQL Mail --> Properties --> I wrote Outlook in the profile name --> then click "Test" --> I encounter this error: "Error 18025: xp_test_mapi_profile: failed with mail error 0x80040111"

I looked at

http://support.microsoft.com/?id=263556

I could not figured it out

Any help please?

Thanks,

Ven

You need a mapi email client such as Outlook 2000.

I have around 17 SQL/Server 2000's using Domino 6.5 email accounts. Here is the scoop:

Log on to the server as the account that is used for the SQL Service account and install Outlook 2000 (with no service pack). Launch Outlook 2000 and create a mail profile that points to your Domino server. Call this email account SQLMail. Create another Outlook 2000 profile with the name SQLAgentMail and test it (this can be the same Domino account). Then log off the server and log back on using the login account that you normally run the server with. Restart SQL Server (and SQL Server Agent) and then the mapi email profiles created earlier will be available. Set SQLMail to use SQLMail profile and then set SQL Server Agent mail to use SQLAgentMail profile. That's it!

DeWayne

|||

-

|||

DeWayne,

Thanks for your help.

I have other question:

While am setting up SQLMail to use SQLMail profile and then set SQL Server Agent mail to use SQLAgentMail profile.

Receiving the following error.

Error 22022QLServerAgentError: Unable to get the default MAPI Address Book due to MAPI error 271: An error occurred while attempting to open the Window Address Book. Please specify a default mail delivery location in you profile.

If I try to create MAPI profile IBM Lotus Domino Access for Microsoft Outlook - create - new profile through getting the below error.

Failed to create new MAPI profile. Error creating personal Folders service

Note: This error can be caused by an incorrect configuration of out look 2000. If you are using outlook 2000, Please verify that is running in Corporate/Workgroup Mode.

Setup encountered an error and failed to create a MAPI profile.

You will need to reinstall IBM Lotus Domino Access for Microsoft Outlook

(Already we removed and reinstalled)

Any help please?

Ven

|||

DeWayne,

Sorry for the inconvenience,

Restarted SQL Server (and SQL Server Agent) ,the mapi email profiles created earlier still not available.

Can you please help me?

|||

Sure!

You don't need the Notes client installed on the Server at all as you will be using a POP3 email account to connect to the Domino Server (at least that is the way that I run it.)

Sign back on as the SQL Server service account then launch Outlook 2000. Click Tools, Options, click the Mail Services Tab, then click Reconfigure Mail Support and select the Corporate Workgroup option. You may have to setup the mail profile/accounts again if needed (choose POP3 when creating the mail accounts). Be sure to set Outlook to use each profile that you created and launch Outlook and click send/receive to test the email accounts.) Then logoff and sign back in as the normal Server user then restart SQL Server again...

|||

DeWayne,

Thanks you so much. It is working now.

I have other question.

we have five different sql servers.

Is it okif I use the same ( single )mail box for different profiles? instead of creating different mail box on each server?

Or does it works like a mail realy?.

Please help?

Thanks,

Ven

|||

Ven,

I create a new email account for each Server so that any emails from a SQL Server are easily identified. For example, a server named "Boston" I would create an email account named "Boston Server". If SQL is only SENDING emails then you could use one email box for everything; however, I would not want to set up my environment that way...

p.s. I am glad that everything is working correctly!!!

DeWayne