Error publishing databases with not-server's default collation

Hello.
While trying to publish any database that uses a collation different from
server's default, I get this error in the step after selecting the articles
to be published:
Error 21423: You do not have sufficient privileges to view the publication
information. Your administrator may need to fix the PAL role on the publisher
for publication 'database_name'.
I've being trying to track down this error for a while now, and I've just
noticed it's related to the collation...
Any ideas about this?
Not sure if it's relevant here, but when I had a case-sensitive server
collation I noticed that passwords of logins became case sensitive on
authentication. I wonder if there is somehow a login/user case sensitivity
issue at work here also? Are the 2 collations the same in this regard or
different (a mixture of _CS and _CI)? Please can you post up the entire
collation names for the circumstance that doesn't work.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||The collations are:
Chinese_Taiwan_Stroke_BIN for the dbs that fails
and:
SQL_Latin1_General_CP1_CI_AS for the dbs that are sucessfuly published.
In any case, the passwords for the accounts are all lowercase...
Thanks for your support,
RODOLFO
"Paul Ibison" wrote:

> Not sure if it's relevant here, but when I had a case-sensitive server
> collation I noticed that passwords of logins became case sensitive on
> authentication. I wonder if there is somehow a login/user case sensitivity
> issue at work here also? Are the 2 collations the same in this regard or
> different (a mixture of _CS and _CI)? Please can you post up the entire
> collation names for the circumstance that doesn't work.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>

Error on creating cube file from Excel 2003, AS 2005

Hi,

I tried to create a cube file in Excel 2003. Data source is SSAS 2005.

On the last step of wizard I get the following error:
Microsoft OLE DB Provider for Analysis Services 2005:
Query (3,2) Parser: The syntax for 'DIMENSION' is incorrect.

Seems like a bug. Is there any fix?
Tried to search google, found nothing...

SQL Server 2005 Developer SP2
Excell 2003 SP2

Thx for any tip...

certainly sounds like a bug. Can you provide a repro' that the product team can look at?

thanks,

Bala.

Error on creating cube file from Excel 2003, AS 2005

Hi,

I tried to create a cube file in Excel 2003. Data source is SSAS 2005.

On the last step of wizard I get the following error:
Microsoft OLE DB Provider for Analysis Services 2005:
Query (3,2) Parser: The syntax for 'DIMENSION' is incorrect.

Seems like a bug. Is there any fix?
Tried to search google, found nothing...

SQL Server 2005 Developer SP2
Excell 2003 SP2

Thx for any tip...

certainly sounds like a bug. Can you provide a repro' that the product team can look at?

thanks,

Bala.

Error Message.....

I am using SQL 2K.
I am calling the below SQL statement as one of the SQL task in one of the
step.
EXEC SP_CYCLE_ERRORLOG
I am getting the attached message.
How to solve it?
Thanks,
Alok
Below is the error message.
"EXCUTE permission denied on object 'sp_cycle_errolog', database
'master',owner 'dbo'"Alok Choudhary wrote:
> I am using SQL 2K.
> I am calling the below SQL statement as one of the SQL task in one of
> the step.
> EXEC SP_CYCLE_ERRORLOG
> I am getting the attached message.
> How to solve it?
> Thanks,
> Alok
> Below is the error message.
> "EXCUTE permission denied on object 'sp_cycle_errolog', database
> 'master',owner 'dbo'"
Your user id does not have rights to execute that procedure because you
are probably not a system administrator. Admin rights are required.
--
David Gugick
Imceda Software
www.imceda.com|||What server roles are you a member of? sp_cycle_errorlog is sysadmin only.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Alok Choudhary" <AC_Ind@.hotmail.com> wrote in message
news:eCsUogNCFHA.1396@.TK2MSFTNGP14.phx.gbl...
> I am using SQL 2K.
> I am calling the below SQL statement as one of the SQL task in one of the
> step.
> EXEC SP_CYCLE_ERRORLOG
> I am getting the attached message.
> How to solve it?
> Thanks,
> Alok
> Below is the error message.
> "EXCUTE permission denied on object 'sp_cycle_errolog', database
> 'master',owner 'dbo'"
>
>

Error message question..

I am getting the error message
Procedure or function sp_MSaddinitialarticle has too many arguments specified. The step failed.
Please help me resolve this issue (The knowledge base did not have any relevent information).
Thank you for a quick response,
Carl
You are trying to put more arguments to a
procedure or funtion than it needs.
for example: (psuedo code)
sp_myproc @.A, @.B, @.C
and then you
EXEC sp_myproc 1, 2, 3, 4
would get you the error because you
have too many arguments (4) for the
procedure (3)
Bob M.
"Carl" <Carl@.discussions.microsoft.com> wrote in message
news:AB31BB38-3C7A-4772-93C4-6E453ACC3C63@.microsoft.com...
> I am getting the error message
> Procedure or function sp_MSaddinitialarticle has too many arguments
specified. The step failed.
> Please help me resolve this issue (The knowledge base did not have any
relevent information).
> Thank you for a quick response,
> Carl
|||Carl,
Whats the SQLServer edition and service pack?
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Carl" <Carl@.discussions.microsoft.com> wrote in message
news:AB31BB38-3C7A-4772-93C4-6E453ACC3C63@.microsoft.com...
> I am getting the error message
> Procedure or function sp_MSaddinitialarticle has too many arguments
specified. The step failed.
> Please help me resolve this issue (The knowledge base did not have any
relevent information).
> Thank you for a quick response,
> Carl

Error message question..

I am getting the error message
Procedure or function sp_MSaddinitialarticle has too many arguments specifie
d. The step failed.
Please help me resolve this issue (The knowledge base did not have any relev
ent information).
Thank you for a quick response,
CarlYou are trying to put more arguments to a
procedure or funtion than it needs.
for example: (psuedo code)
sp_myproc @.A, @.B, @.C
and then you
EXEC sp_myproc 1, 2, 3, 4
would get you the error because you
have too many arguments (4) for the
procedure (3)
Bob M.
"Carl" <Carl@.discussions.microsoft.com> wrote in message
news:AB31BB38-3C7A-4772-93C4-6E453ACC3C63@.microsoft.com...
> I am getting the error message
> Procedure or function sp_MSaddinitialarticle has too many arguments
specified. The step failed.
> Please help me resolve this issue (The knowledge base did not have any
relevent information).
> Thank you for a quick response,
> Carl|||Carl,
Whats the SQLServer edition and service pack?
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Carl" <Carl@.discussions.microsoft.com> wrote in message
news:AB31BB38-3C7A-4772-93C4-6E453ACC3C63@.microsoft.com...
> I am getting the error message
> Procedure or function sp_MSaddinitialarticle has too many arguments
specified. The step failed.
> Please help me resolve this issue (The knowledge base did not have any
relevent information).
> Thank you for a quick response,
> Carl

Error message question..

I am getting the error message
Procedure or function sp_MSaddinitialarticle has too many arguments specified. The step failed.
Please help me resolve this issue (The knowledge base did not have any relevent information).
Thank you for a quick response,
CarlYou are trying to put more arguments to a
procedure or funtion than it needs.
for example: (psuedo code)
sp_myproc @.A, @.B, @.C
and then you
EXEC sp_myproc 1, 2, 3, 4
would get you the error because you
have too many arguments (4) for the
procedure (3)
Bob M.
"Carl" <Carl@.discussions.microsoft.com> wrote in message
news:AB31BB38-3C7A-4772-93C4-6E453ACC3C63@.microsoft.com...
> I am getting the error message
> Procedure or function sp_MSaddinitialarticle has too many arguments
specified. The step failed.
> Please help me resolve this issue (The knowledge base did not have any
relevent information).
> Thank you for a quick response,
> Carl|||Carl,
Whats the SQLServer edition and service pack?
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Carl" <Carl@.discussions.microsoft.com> wrote in message
news:AB31BB38-3C7A-4772-93C4-6E453ACC3C63@.microsoft.com...
> I am getting the error message
> Procedure or function sp_MSaddinitialarticle has too many arguments
specified. The step failed.
> Please help me resolve this issue (The knowledge base did not have any
relevent information).
> Thank you for a quick response,
> Carl

Error message in a job, SQLSTATE 42S02 (Error 208)

I have a scheduled job where it's failing intermittently every few days.
The job fails in one of two steps, but with the same error above.
Step 18 is where I do a drop of the table and a create of the table, and
its indexes. It doesn't fail here, but fails in one of the next two
steps.
Step 19 is an insert into the table created in step 18. It takes a
source table, and puts into it mostly the same information, except that
it sums stuff up by purcase order instead of by line item. It also does
some max(dates) to record the most recent activity on the items in this
summary table.
Step 20 is an insert into the same table from the same source table as
in step 19, except that it processes everything excluded from the first
pass.
It's failed on step 19 & step 20 over the last several days. The error
message itself displays like:
"Executed as user: Mydomain\Mysqlaccount. Invalid Object Name
'tablename'. [SQLSTATE 42S02] (Error 208). The step failed."
To fix the problem, we've simply re-started in the failed step (did not
re-create the table, only picked up with the insert into it), and the
job has run to completion.
One thing that has occurred to me is to have the table drop, create and
load all in stored procedures, instead of how it is now - in TSQL code
within the batch job. I don't know if this would fix the problem though.
Any ideas as to what's happening? The info I've found on the 42S02
error hasn't been much help yet.
SCBased on the fact that I can't see your DTS workflow diagram, I'd urge you t
o
check the workflow.
ML|||> Based on the fact that I can't see your DTS workflow diagram, I'd urge you toed">
> check the workflow.
There is no DTS Workflow diagram.
These are just steps in a job created under the Management folder in
Enterprise Manager, under the SQL Server Agent, under the Jobs link.
It's 3 steps inside 1 of those jobs that is dying on step 19 or 20 with
the 42S02 Error 208 message.
18 runs okay, 19 & 20 are the ones that have died intermittently.
The steps are:
-- Step 18
CREATE TABLE [dbo].[posummary] (
[sSalesOrganization] [varchar] (8) NULL ,
[sSalesGroup] [varchar] (3) NULL ,
[sSalesRepCode] [varchar] (10) NULL ,
[sDistributionChannel] [varchar] (2) NULL ,
[sSoldTo] [varchar] (10) NULL ,
[sShipTo] [varchar] (10) NULL ,
[sCustName1] [varchar] (45) NULL ,
[sCustName2] [varchar] (35) NULL ,
[PO_Num] [varchar] (20) NULL ,
[Order_date] [smalldatetime] NULL ,
[Req_Ship_Date] [smalldatetime] NULL ,
[Inv_Date] [smalldatetime] NULL ,
[Inv_Nr] [varchar] (10) NULL ,
[lOrderQuantity] [int] NULL ,
[lOrderValue] [money] NULL ,
[lShipValue] [money] NULL ,
[OpenVal] [money] NULL ,
[lShipQuantity] [int] NULL ,
[sAccountSoldTo] [varchar] (10) NULL ,
[sMasterSoldTo] [varchar] (10) NULL
) ON [PRIMARY]
GO
CREATE INDEX [posummary] ON [dbo].[posummary]([sSalesOrganization],
[sDistributionChannel], [sSalesGroup], [sSalesRepCode], [sSoldTo],
[sShipTo], [PO_Num], [Inv_Nr]) ON [PRIMARY]
GO
CREATE INDEX [sorg] ON [dbo].[posummary]([sSalesOrganization]) ON
[PRIMARY]
GO
CREATE INDEX [distchnl] ON [dbo].[posummary]([sDistributionChannel])
ON [PRIMARY]
GO
CREATE INDEX [sgroup] ON [dbo].[posummary]([sSalesGroup]) ON [PRIMARY]
GO
CREATE INDEX [sRep] ON [dbo].[posummary]([sSalesRepCode]) ON [PRIMARY]
GO
CREATE INDEX [SoldTo] ON [dbo].[posummary]([sSoldTo]) ON [PRIMARY]
GO
CREATE INDEX [ShipTo] ON [dbo].[posummary]([sShipTo]) ON [PRIMARY]
GO
CREATE INDEX [PO] ON [dbo].[posummary]([PO_Num]) ON [PRIMARY]
GO
CREATE INDEX [InvNr] ON [dbo].[posummary]([Inv_Nr]) ON [PRIMARY]
GO
CREATE INDEX [Ord Date] ON [dbo].[posummary]([Order_date]) ON [PRIMARY]
GO
CREATE INDEX [ACCTSOLDTO] ON [dbo].[posummary]([sAccountSoldTo]) ON
[PRIMARY]
GO
CREATE INDEX [MASTERSOLDTO] ON [dbo].[posummary]([sMasterSoldTo]) ON
[PRIMARY]
GO
-- Step 19
insert into posummary
select
podetail.ssalesorganization,
podetail.Ssalesgroup,
podetail.ssalesrepcode,
podetail.sDistributionChannel,
podetail.ssoldto,
podetail.sshipto,
max(tblmaster_shipto.scustname1) as Custname1,
max(tblmaster_shipto.scustname2) as Custname2,
PO_Num,
max(Order_Date) as Order_Date,
max(Req_Ship_Date) as Req_Ship_Date,
max(Inv_Date) as Inv_Date,
max(Inv_Nr) as Inv_Nr,
sum(lorderquantity) as lorderquantity,
sum(lordervalue) as lordervalue,
sum(lshipvalue) as lshipvalue,
sum(lordervalue) - sum(lshipvalue) as Openval,
sum(lshipquantity) as lshipquantity,
max(tblmaster_accountsoldto.saccountsoldto) as AccountSoldTo,
max(tblmaster_accountsoldto.smastersoldto) as MasterSoldTo
from podetail
left outer join tblmaster_shipto on
((tblmaster_shipto.ssoldto = podetail.ssoldto) and
(tblmaster_shipto.sshipto = podetail.sshipto) and
(tblmaster_shipto.ssalesgrp = podetail.ssalesgroup) and
(tblmaster_shipto.ssalesrep = podetail.ssalesrepcode) and
(tblmaster_shipto.sdistrchnl = podetail.sdistributionchannel))
left outer join tblmaster_accountsoldto on
(tblmaster_accountsoldto.ssoldto = podetail.ssoldto)
and (tblmaster_accountsoldto.ssalesgroup not in ('R1','R2','R3'))
where podetail.sdistributionchannel != 'WL'
group by
podetail.ssalesorganization,
podetail.Ssalesgroup,
podetail.ssalesrepcode,
podetail.sDistributionChannel,
podetail.ssoldto,
podetail.sshipto,
PO_Num
-- step 20
insert into posummary
select
podetail.ssalesorganization,
podetail.Ssalesgroup,
podetail.ssalesrepcode,
podetail.sDistributionChannel,
podetail.ssoldto,
podetail.sshipto,
max(tblmaster_shipto.scustname1) as Custname1,
max(tblmaster_shipto.scustname2) as Custname2,
PO_Num,
max(Order_Date) as Order_Date,
max(Req_Ship_Date) as Req_Ship_Date,
max(Inv_Date) as Inv_Date,
max(Inv_Nr) as Inv_Nr,
sum(lorderquantity) as lorderquantity,
sum(lordervalue) as lordervalue,
sum(lshipvalue) as lshipvalue,
sum(lordervalue) - sum(lshipvalue) as Openval,
sum(lshipquantity) as lshipquantity,
max(tblmaster_accountsoldto.saccountsoldto) as AccountSoldTo,
max(tblmaster_accountsoldto.smastersoldto) as MasterSoldTo
from podetail
left outer join tblmaster_shipto on
((tblmaster_shipto.ssoldto = podetail.ssoldto) and
(tblmaster_shipto.sshipto = podetail.sshipto) and
(tblmaster_shipto.ssalesgrp = podetail.ssalesgroup) and
(tblmaster_shipto.ssalesrep = podetail.ssalesrepcode) and
(tblmaster_shipto.sdistrchnl = podetail.sdistributionchannel))
left outer join tblmaster_accountsoldto on
(tblmaster_accountsoldto.ssoldto = podetail.ssoldto)
and (tblmaster_accountsoldto.ssalesgroup in ('R1','R2','R3'))
where podetail.sdistributionchannel = 'WL'
group by
podetail.ssalesorganization,
podetail.Ssalesgroup,
podetail.ssalesrepcode,
podetail.sDistributionChannel,
podetail.ssoldto,
podetail.sshipto,
PO_Num|||Your insert statement is not optimal - it's missing the column list for the
destination table. Maybe that's it.
ML|||> Your insert statement is not optimal - it's missing the column list for the
> destination table. Maybe that's it.
You mean where I have:
insert into posummary
select
podetail.ssalesorganization,
podetail.Ssalesgroup,
podetail.ssalesrepcode,
podetail.sDistributionChannel,
podetail.ssoldto,
podetail.sshipto......
it should now read:
insert into posummary
select
sSalesOrganization = podetail.ssalesorganization,
sSalesGroup = podetail.Ssalesgroup,
sSalesRepCode = podetail.ssalesrepcode,
sDistributionChannel = podetail.sDistributionChannel,
sSoldTo = podetail.ssoldto,
sShipTo = podetail.sshipto,
Is that correct?
I didn't think that made a lot of difference. The error message surely
doesn't lead you in that direction. The error message makes you think
it cannot find the table.
BC