Analysis Services

I have a MS SQL Server 2000 SP3 running under MS Server 2000 Standard Edit
SP4 (MDAC 2.8).
I just installed Analysis Services. How do I apply SP3 to this system?
Each time I try to reinstall SP3, I get the message:
"Setup was unable to validate the logged user. Press Retry to enter another
option, or Cancel to exit setup."
After I exit SP3, the SQLSERVER AGENT is stopped even though it was running
when I start the SP3.
Thank you...Ed> I have a MS SQL Server 2000 SP3 running under MS Server 2000 Standard Edit
> SP4 (MDAC 2.8).
What? Can you explain this again?
> I just installed Analysis Services. How do I apply SP3 to this system?
If you review http://www.microsoft.com/sql/downloads/2000/sp3.asp, you'll
see that you need to download sql2kasp3.exe.
--
http://www.aspfaq.com/
(Reverse address to reply.)

Analisys Services OLAP Error

running sql server 2000 w/ analisys serv sp4 on w2k3 sp1. Yes, also we are running sql 2000 sp4.

I keep getting an event id 6034.

The mssqlserverolapservice service terminated unexpectedly. It has done this 134 times.

Now, i went ahead and installed the suggested rollup hotfix already, which is a post AS SP4 rollup hotfix that fixes this.

It didn't.

What next?

Mike,

This is just one of the possible options:

I have seen this happening with corrupted database. To fix this, you have to find corrupted database and remove it from data folder. I was doing this:

1. Stop Analysis Services service.

2. Go to analysis services data folder and copy folder for one database to another outside folder. Also copy related file from root data folder (I think something like DBName.odb, forgot extension)?

3. Try to start analysis services, if same problem, choose another database and do step 2.

If you'll find corrupted databases, copy all other ones back. Restore corrupted database from backup.

Vidas Matelis

sql

An instance of the SQL Server Reconciler error object cannot be created

I've got the following server configuration.

Database Server

- Windows 2003 Standard

- MSSQL 2000 sp4

Web Server

- Windows 2003 Standard

- SQL 2000 sp4 replication components

- SQL Mobile 2005 Server tools

The database server published out the snapshot to a share on the web server. This bit is working file, I can see the snapshot contents etc. When I connect from my own pc using SQL Management Studio and attempt to set up a subscription to a Mobile database, I get the following error.

TITLE: Microsoft SQL Server Management Studio

An instance of the SQL Server Reconciler error object cannot be created. Try reinstalling the replication components.
HRESULT 0x8007007E (28010)

BUTTONS:

OK

I've also accessed the Url using diagnostics and get the following output:

 SQL Server Mobile Server Agent Diagnostics

 2006/01/13 10:09:10

*General Information*Item Value
Server Name bundy
URL /services/taskmobileserversync/sqlcesa30.dll
Authentication Type Anonymous
Server Port 80
HTTPS off
Server Software Microsoft-IIS/6.0
Replication Allowed
RDA Allowed
Logging Level 1

*Impersonation and Access Tests* Action Status ErrorCode
Impersonate User SUCCESS 0x0
ReadWriteDeleteMessageFile SUCCESS 0x0

*SQL Server Mobile Modules Test*Module Status ErrorCode Version
SQLCERP30.DLL SUCCESS 0x0 3.0.5206.0
SQLCESA30.DLL SUCCESS 0x0 3.0.5206.0

*Reconciler Test* Reconciler Status ErrorCode
9.0 Database Reconciler FAILURE 0x80040154
8.0 Database Reconciler FAILURE 0x8007007E

*SQL Server Module Versions* Module Version
sqloledb.dll 2000.85.1022.0
8.0 replrec.dll 2000.80.2038.0
8.0 replprov.dll 2000.80.2038.0
8.0 msgprox.dll 2000.80.2038.0

Any suggestions? I've reinstalled the various components on the Web Server quite a few times by now...

thanks

// charlie

Search for REPLERRX.DLL and register using regsvr32. And then try. If the registration fails for this DLL, just check whether you have all the dependant DLLs. There are tools to find out the dependant DLLs of a particular binary. Most probably you may need to have MSVCR71.DLL and MSVCP71.DLL. However these two DLLs are already packaged in the 'SQL Server 2000 SP4 Replication Components' setup package. There is some problem in the installation I believe. If you could register REPLERRX.DLL, then you should be able to sync.

Thanks,

Laxmi NRO, MSFT, SQL Mobile, Microsoft Corporation

|||To fix this, I installed the SQL Server 2000 client tools. This resolved the problem.|||

Thanks for letting us know the information.

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

An explicit value for the identity column in table

for some unknow reasons.. my store proc stop working.. and i got an error..
i have installaed the latest SP4 for SQL server 2000 and still have the problem !
any ideas why ??
Message "An explicit value for the identity column in table 'LCMS_Modules' can only be specified when a column list is used and IDENTITY_INSERT is ON."
CREATE procedure LCMS_Modules_Add

@.PageID int,
@.ModuleDefID int,
@.Panename nvarchar(32),
@.Title nvarchar(128),
@.Admins nvarchar(256)

as

insert into LCMS_Modules
values(@.PageID, @.ModuleDefID, 99, @.Panename, @.Title, '0;', @.Admins, 0, '', 'Center', '', '', '', 1, 0)
GO

Have you reordered the columns in your LCMS_Modules table? I amguessing that you did, and that the identity column had previously beenat the end and is now in the beginning or somewhere in the middle.
Specify your column names in your INSERT statement. This is a best practice anyway and should take care of your problem.
insert into LCMS_Modules (column1, column2, column3, ...etc..., column15),
values(@.PageID, @.ModuleDefID, 99, @.Panename, @.Title, '0;', @.Admins, 0, '', 'Center', '', '', '', 1, 0)

Always write to Windows event log" doesn't work in MS SQL Server 2

Hi,
I have an MS SQL Server 2000 SP3, MS Windows 2000 SP4 machine. When I set
the "Always write to Windows event log" option for the 14150 (replication
agent success) error and start a snapshot agent, a message is logged in SQL
Server errorlog but not in Windows application log. Why?
-- Thanks, Oskar.
Sorry this wasn't a valid question. The error actually is logged, only it is
logged as an informational message, not error message. I was mislead by that.
--Thanks, Oskar.
"Oskar" wrote:

> Hi,
> I have an MS SQL Server 2000 SP3, MS Windows 2000 SP4 machine. When I set
> the "Always write to Windows event log" option for the 14150 (replication
> agent success) error and start a snapshot agent, a message is logged in SQL
> Server errorlog but not in Windows application log. Why?
> -- Thanks, Oskar.
>

Always write to Windows event log" doesn't work in MS SQL Server 2

Hi,
I have an MS SQL Server 2000 SP3, MS Windows 2000 SP4 machine. When I set
the "Always write to Windows event log" option for the 14150 (replication
agent success) error and start a snapshot agent, a message is logged in SQL
Server errorlog but not in Windows application log. Why?
-- Thanks, Oskar.Sorry this wasn't a valid question. The error actually is logged, only it is
logged as an informational message, not error message. I was mislead by that
.
--Thanks, Oskar.
"Oskar" wrote:

> Hi,
> I have an MS SQL Server 2000 SP3, MS Windows 2000 SP4 machine. When I set
> the "Always write to Windows event log" option for the 14150 (replication
> agent success) error and start a snapshot agent, a message is logged in SQ
L
> Server errorlog but not in Windows application log. Why?
> -- Thanks, Oskar.
>

Always write to Windows event log" doesn't work in MS SQL Server 2

Hi,
I have an MS SQL Server 2000 SP3, MS Windows 2000 SP4 machine. When I set
the "Always write to Windows event log" option for the 14150 (replication
agent success) error and start a snapshot agent, a message is logged in SQL
Server errorlog but not in Windows application log. Why?
-- Thanks, Oskar.Sorry this wasn't a valid question. The error actually is logged, only it is
logged as an informational message, not error message. I was mislead by that.
--Thanks, Oskar.
"Oskar" wrote:
> Hi,
> I have an MS SQL Server 2000 SP3, MS Windows 2000 SP4 machine. When I set
> the "Always write to Windows event log" option for the 14150 (replication
> agent success) error and start a snapshot agent, a message is logged in SQL
> Server errorlog but not in Windows application log. Why?
> -- Thanks, Oskar.
>

Alternatives to SQLMail

Hi,

We encountered a situation a few days where our SQLMail stopped working. We are using SQL Server 2000, SP4 and an Exchange Server. Prior to the SQLMail stopping we had experienced problems with our Exchange Server for a period of time.

Researching on the Internet, I've found several explanations that all read:

"The most common cause of this problem is a temporary loss of the network connection to the e-mail server. This problem most often occurs when SQL Mail is configured to use Internet protocols for message delivery, although it can also occur when communicating with a Microsoft Exchange host.

When SQL Mail loses a connection to the e-mail server, the Extended MAPI components display a message that requests user action as to whether or not to continue. This message does not appear on the server because SQL Mail is run from the SQL Server service. Because the message does not appear, there is no way to respond to the message to allow SQL Mail to continue. Even if the network connection becomes available, SQL Mail does not retry the connection.

To work around the problem, you must stop and restart SQL Server."

I believe this is the situation that we encountered. However stopping and restarting SQL Server did not solve the problem. We had to reboot the machine before the SQL Mail started working again. This is a production machine that we don't just want to "reboot at will", so I'm a little concerned about this issue.

My question is - are there any alternatives to using SQLMail? I have stored procedures that call xp_sendmail (and then xp_stopmail) to send email notifications in certain instances. Is there something else that I can/should use in its place? I found a reference that stated "To resolve the problem, update your applications to use Database Mail.", but this was on a SQL Server 2005 page, and apparently Database Mail is not part of SQL Server 2000.

Thanks,
Beth

YES!

The preferred alternative is xp_smtpmail. You 'should' NOT be using MAPI mail with SQL 2000 -for several reasons

Read about it and download from:

Email for SQL Server 2000
http://www.sqldev.net/xp/xpsmtp.htm

|||Is there any article/link that explains why "You 'should' NOT be using MAPI mail with SQL 2000"?

Thanks for the info on xp_smtpmail - I'll take a look at it.
Beth

|||

This first link is from one of the SQL Dev Team members.

http://sqljunkies.com/WebLog/euang/archive/2004/03/16/1617.aspx

http://www.windowsitpro.com/Articles/ArticleID/14116/14116.html?Ad=1

http://www.developersdex.com/sql/message.asp?p=1925&ID=%3C943EC1D1-1E2A-413A-8DF5-A5F919125DD9%40microsoft.com%3E

Top Causes of SQL Server Downtime (Item #2)
http://www.sqlmag.com/Article/ArticleID/40011/sql_server_40011.html

http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3bQ315886

Google? for: sql and server and mapi and problems. You'll probably notice a couple hundred thousand hits...

'nuf said.

Alternative to OSQL?

SQL2K SP4
Howdy all. I have a daily process that gets a .txt file full of Inserts/
Updates/ Deletes and imports them into a SQL DB every day. I have a Stored
Proc that calls a .bat which contains OSQL and runs the .txt file. Are there
any alternatives to this from within SQL Server?
TIA, ChrisRHi Chris
You could write your own application to parse the file and run each command,
a different alternative would be to load the data into a table and use the
EXEC command to run them. As your statements are in a file, there is a
security risk. If you just provided a data file and loaded it into a staging
table you could then insert/update existing data quite easily on-mass without
having to insert/update each row individually. You could use DTS, BULK INSERT
or BCP to quickly load the data into a staging table.
John
"ChrisR" wrote:
> SQL2K SP4
> Howdy all. I have a daily process that gets a .txt file full of Inserts/
> Updates/ Deletes and imports them into a SQL DB every day. I have a Stored
> Proc that calls a .bat which contains OSQL and runs the .txt file. Are there
> any alternatives to this from within SQL Server?
> TIA, ChrisR
>
>|||I appreciare your ideas, but Im confused.
> You could write your own application to parse the file and run each
command
I really need to do this from within SQL Server.
> If you just provided a data file and loaded it into a staging
> table you could then insert/update existing data quite easily on-mass
without
> having to insert/update each row individually. You could use DTS, BULK
INSERT
> or BCP to quickly load the data into a staging table.
How would this be any better than what I have? I still need to get it from
the file into a table. The way Im reading this, I need to go from file to
table, then from table to table?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:C37FBE46-03DF-4FF8-9F53-35532DECCE64@.microsoft.com...
> Hi Chris
> You could write your own application to parse the file and run each
command,
> a different alternative would be to load the data into a table and use the
> EXEC command to run them. As your statements are in a file, there is a
> security risk. If you just provided a data file and loaded it into a
staging
> table you could then insert/update existing data quite easily on-mass
without
> having to insert/update each row individually. You could use DTS, BULK
INSERT
> or BCP to quickly load the data into a staging table.
> John
> "ChrisR" wrote:
> > SQL2K SP4
> >
> > Howdy all. I have a daily process that gets a .txt file full of Inserts/
> > Updates/ Deletes and imports them into a SQL DB every day. I have a
Stored
> > Proc that calls a .bat which contains OSQL and runs the .txt file. Are
there
> > any alternatives to this from within SQL Server?
> >
> > TIA, ChrisR
> >
> >
> >|||Hi Chris
How do you create the file that makes up these SQL Statements?
John
"ChrisR" wrote:
> I appreciare your ideas, but Im confused.
> > You could write your own application to parse the file and run each
> command
> I really need to do this from within SQL Server.
> > If you just provided a data file and loaded it into a staging
> > table you could then insert/update existing data quite easily on-mass
> without
> > having to insert/update each row individually. You could use DTS, BULK
> INSERT
> > or BCP to quickly load the data into a staging table.
> How would this be any better than what I have? I still need to get it from
> the file into a table. The way Im reading this, I need to go from file to
> table, then from table to table?
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:C37FBE46-03DF-4FF8-9F53-35532DECCE64@.microsoft.com...
> > Hi Chris
> >
> > You could write your own application to parse the file and run each
> command,
> > a different alternative would be to load the data into a table and use the
> > EXEC command to run them. As your statements are in a file, there is a
> > security risk. If you just provided a data file and loaded it into a
> staging
> > table you could then insert/update existing data quite easily on-mass
> without
> > having to insert/update each row individually. You could use DTS, BULK
> INSERT
> > or BCP to quickly load the data into a staging table.
> >
> > John
> >
> > "ChrisR" wrote:
> >
> > > SQL2K SP4
> > >
> > > Howdy all. I have a daily process that gets a .txt file full of Inserts/
> > > Updates/ Deletes and imports them into a SQL DB every day. I have a
> Stored
> > > Proc that calls a .bat which contains OSQL and runs the .txt file. Are
> there
> > > any alternatives to this from within SQL Server?
> > >
> > > TIA, ChrisR
> > >
> > >
> > >
>
>|||It is made up for me. A mainframe does some stuff, an ETL tool called Tree
House does some stuff, etc.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:FFCD1719-BA31-49DE-BD31-BC52EF3AD898@.microsoft.com...
> Hi Chris
> How do you create the file that makes up these SQL Statements?
> John
> "ChrisR" wrote:
> > I appreciare your ideas, but Im confused.
> >
> > > You could write your own application to parse the file and run each
> > command
> >
> > I really need to do this from within SQL Server.
> >
> > > If you just provided a data file and loaded it into a staging
> > > table you could then insert/update existing data quite easily on-mass
> > without
> > > having to insert/update each row individually. You could use DTS, BULK
> > INSERT
> > > or BCP to quickly load the data into a staging table.
> >
> > How would this be any better than what I have? I still need to get it
from
> > the file into a table. The way Im reading this, I need to go from file
to
> > table, then from table to table?
> >
> >
> > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > news:C37FBE46-03DF-4FF8-9F53-35532DECCE64@.microsoft.com...
> > > Hi Chris
> > >
> > > You could write your own application to parse the file and run each
> > command,
> > > a different alternative would be to load the data into a table and use
the
> > > EXEC command to run them. As your statements are in a file, there is a
> > > security risk. If you just provided a data file and loaded it into a
> > staging
> > > table you could then insert/update existing data quite easily on-mass
> > without
> > > having to insert/update each row individually. You could use DTS, BULK
> > INSERT
> > > or BCP to quickly load the data into a staging table.
> > >
> > > John
> > >
> > > "ChrisR" wrote:
> > >
> > > > SQL2K SP4
> > > >
> > > > Howdy all. I have a daily process that gets a .txt file full of
Inserts/
> > > > Updates/ Deletes and imports them into a SQL DB every day. I have a
> > Stored
> > > > Proc that calls a .bat which contains OSQL and runs the .txt file.
Are
> > there
> > > > any alternatives to this from within SQL Server?
> > > >
> > > > TIA, ChrisR
> > > >
> > > >
> > > >
> >
> >
> >|||Hi
I guess you could get it changed to produce updategrams and use SQLXML, but
it would be far easier and quicker just to dump a datafile and load it
en-mass.
If you want to still with the SQL statements then you could look at loading
this into a table and then using a cursor and execute statement to run them
(see books online for both), this would rely that each statement was less
than 8000 characters and contained no carriage return or line feeds.
John
"ChrisR" wrote:
> It is made up for me. A mainframe does some stuff, an ETL tool called Tree
> House does some stuff, etc.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:FFCD1719-BA31-49DE-BD31-BC52EF3AD898@.microsoft.com...
> > Hi Chris
> >
> > How do you create the file that makes up these SQL Statements?
> >
> > John
> >
> > "ChrisR" wrote:
> >
> > > I appreciare your ideas, but Im confused.
> > >
> > > > You could write your own application to parse the file and run each
> > > command
> > >
> > > I really need to do this from within SQL Server.
> > >
> > > > If you just provided a data file and loaded it into a staging
> > > > table you could then insert/update existing data quite easily on-mass
> > > without
> > > > having to insert/update each row individually. You could use DTS, BULK
> > > INSERT
> > > > or BCP to quickly load the data into a staging table.
> > >
> > > How would this be any better than what I have? I still need to get it
> from
> > > the file into a table. The way Im reading this, I need to go from file
> to
> > > table, then from table to table?
> > >
> > >
> > > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > > news:C37FBE46-03DF-4FF8-9F53-35532DECCE64@.microsoft.com...
> > > > Hi Chris
> > > >
> > > > You could write your own application to parse the file and run each
> > > command,
> > > > a different alternative would be to load the data into a table and use
> the
> > > > EXEC command to run them. As your statements are in a file, there is a
> > > > security risk. If you just provided a data file and loaded it into a
> > > staging
> > > > table you could then insert/update existing data quite easily on-mass
> > > without
> > > > having to insert/update each row individually. You could use DTS, BULK
> > > INSERT
> > > > or BCP to quickly load the data into a staging table.
> > > >
> > > > John
> > > >
> > > > "ChrisR" wrote:
> > > >
> > > > > SQL2K SP4
> > > > >
> > > > > Howdy all. I have a daily process that gets a .txt file full of
> Inserts/
> > > > > Updates/ Deletes and imports them into a SQL DB every day. I have a
> > > Stored
> > > > > Proc that calls a .bat which contains OSQL and runs the .txt file.
> Are
> > > there
> > > > > any alternatives to this from within SQL Server?
> > > > >
> > > > > TIA, ChrisR
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%230AAwWdoGHA.4776@.TK2MSFTNGP03.phx.gbl...
> I appreciare your ideas, but Im confused.
> > You could write your own application to parse the file and run each
> command
> I really need to do this from within SQL Server.
Why?
In any case, your best bet is probably BULK INSERT.
> > If you just provided a data file and loaded it into a staging
> > table you could then insert/update existing data quite easily on-mass
> without
> > having to insert/update each row individually. You could use DTS, BULK
> INSERT
> > or BCP to quickly load the data into a staging table.
> How would this be any better than what I have? I still need to get it from
> the file into a table. The way Im reading this, I need to go from file to
> table, then from table to table?
Yes and no. You can go from file->table.
What Chris is suggesting is a staging table (presumably w/o indexes) because
this will make the actual load from the file faster.
It's not necessary, but sometimes can improve performance and overall
maintenance.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:C37FBE46-03DF-4FF8-9F53-35532DECCE64@.microsoft.com...
> > Hi Chris
> >
> > You could write your own application to parse the file and run each
> command,
> > a different alternative would be to load the data into a table and use
the
> > EXEC command to run them. As your statements are in a file, there is a
> > security risk. If you just provided a data file and loaded it into a
> staging
> > table you could then insert/update existing data quite easily on-mass
> without
> > having to insert/update each row individually. You could use DTS, BULK
> INSERT
> > or BCP to quickly load the data into a staging table.
> >
> > John
> >
> > "ChrisR" wrote:
> >
> > > SQL2K SP4
> > >
> > > Howdy all. I have a daily process that gets a .txt file full of
Inserts/
> > > Updates/ Deletes and imports them into a SQL DB every day. I have a
> Stored
> > > Proc that calls a .bat which contains OSQL and runs the .txt file. Are
> there
> > > any alternatives to this from within SQL Server?
> > >
> > > TIA, ChrisR
> > >
> > >
> > >
>