Showing posts with label changing. Show all posts
Showing posts with label changing. Show all posts

Monday, March 12, 2012

Error when changing the length on DataReader Source

Hi,
I am trying to import data from Oracle RDB into SQL Server 2005 using SSIS. Created a ODBC data source to connect to Oracle and used DataReader Source component and ADO.net to connect to the ODBC data source.

Under the Component properties tab, the SQL Command looks something like this.

Select ID, ADDRESS, REVISED from ADDRESS

The data type for the source columns are Integer, Varchar(30) and DATE VMS.

Now when I look at the Input and Output properties window,

The External columns has the following data types.

ID - four-byte signed integer [DT_I4]
ADDRESS - Unicode string [DT_WSTR], length = 0
REVISED - database timestamp [DT_DBTIMESTAMP]

The Output columns has the following data types

ID - four-byte signed integer [DT_I4]
ADDRESS - Unicode string [DT_WSTR], length = 0
REVISED - database timestamp [DT_DBTIMESTAMP]

When I tried to change the length of the ADDRESS on the output column, I get the following error.

Error at Data Flow Task [DataReader Source [1]]: The data type of output columns on the component "DataReader Source" (1) cannot be changed.

Error at Data Flow Task [DataReader Source [1]]: System.Runtime.InteropServices.COMException (0xC020837D)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.SetOutputColumnDataTypeProperties(Int32 iOutputID, Int32 iOutputColumnID, DataType eDataType, Int32 iLength, Int32 iPrecision, Int32 iScale, Int32 iCodePage)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostSetOutputColumnDataTypeProperties(IDTSManagedComponentWrapper90 wrapper, Int32 iOutputID, Int32 iOutputColumnID, DataType eDataType, Int32 iLength, Int32 iPrecision, Int32 iScale, Int32 iCodePage)

Is this the default length for the Unicode string type. I was not able to load the ADDRESS column as it gets truncated before I load it into destination. Even if I use Derived or Data Conversion transformation, the ADDRESS is getting truncated before it reaches this transformation.

Any thoughts.

Thanks,
SK

Did you try using a Data Conversion transformation?

Rafael Salas

|||

Hi,
I did try to use the Data Conversion transformation. But when I execute the package, I get the truncation error at the Data Source Reader itself.

Error: 0xC020902A at Data Flow Task, DataReader Source [1736]: The "component "DataReader Source" (1736)" failed because truncation occurred, and the truncation row disposition on "output column "ADDRESS" (2469)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.

Error: 0xC02090F5 at Data Flow Task, DataReader Source [1736]: The component "DataReader Source" (1736) was unable to process the data.

Error: 0xC0047038 at Data Flow Task, DTS.Pipeline: The PrimeOutput method on component "DataReader Source" (1736) returned error code 0xC02090F5. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.

Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "SourceThread0" has exited with error code 0xC0047038.

Error: 0xC0047039 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown.

Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" has exited with error code 0xC0047039


Thanks,
SK

|||

Hi,
Does anybody have inputs on this issue?

SK

|||

It sounds like the provider you are using is reporting the length of the string incorrectly as 0. I've seen that before with a provider, but I don't recall what one... Is there a different provider you can try?

Otherwise, you might try changing the select statement to cast the value explicitly to a string of length 30 and see if the DataReaderSrc correctly creates the column then.

|||

Unfortunately I can't use any other providers other than ADO.net as I have to use Oracle RDB ODBC to connect to RDB database.

Strangely, now the column is showing as text instead of Unicode string and I was able to use the data conversion transformation to convert back to Unicode String. Not sure what changed on the server. The only thing that I think of is we updated SQL Server with some updated from MS website.

Thanks,
SK

|||

We had the exact same problem trying to pull data from Oracle Rdb. I went round & round but eventually found the solution.

Basically we had to install SQL*Net for Rdb (or OCI Services for Rdb) on our VMS server to make our Rdb database look like an Oracle database. Then we had to install Oracle client software on our client machine. I've used both Oracle 9.2 client and ODAC 10.2. You then set up your client connection using the Oracle Net Manager.

After you've got client & server configured, set up an SSIS connection manager using .Net Providers for OleDb -> Oracle Provider for OLE DB.

It's kind of a hassle to set up but it seems to work just fine.

Regards, Pat

Error when changing the length on DataReader Source

Hi,
I am trying to import data from Oracle RDB into SQL Server 2005 using SSIS. Created a ODBC data source to connect to Oracle and used DataReader Source component and ADO.net to connect to the ODBC data source.

Under the Component properties tab, the SQL Command looks something like this.

Select ID, ADDRESS, REVISED from ADDRESS

The data type for the source columns are Integer, Varchar(30) and DATE VMS.

Now when I look at the Input and Output properties window,

The External columns has the following data types.

ID - four-byte signed integer [DT_I4]
ADDRESS - Unicode string [DT_WSTR], length = 0
REVISED - database timestamp [DT_DBTIMESTAMP]

The Output columns has the following data types

ID - four-byte signed integer [DT_I4]
ADDRESS - Unicode string [DT_WSTR], length = 0
REVISED - database timestamp [DT_DBTIMESTAMP]

When I tried to change the length of the ADDRESS on the output column, I get the following error.

Error at Data Flow Task [DataReader Source [1]]: The data type of output columns on the component "DataReader Source" (1) cannot be changed.

Error at Data Flow Task [DataReader Source [1]]: System.Runtime.InteropServices.COMException (0xC020837D)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.SetOutputColumnDataTypeProperties(Int32 iOutputID, Int32 iOutputColumnID, DataType eDataType, Int32 iLength, Int32 iPrecision, Int32 iScale, Int32 iCodePage)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostSetOutputColumnDataTypeProperties(IDTSManagedComponentWrapper90 wrapper, Int32 iOutputID, Int32 iOutputColumnID, DataType eDataType, Int32 iLength, Int32 iPrecision, Int32 iScale, Int32 iCodePage)

Is this the default length for the Unicode string type. I was not able to load the ADDRESS column as it gets truncated before I load it into destination. Even if I use Derived or Data Conversion transformation, the ADDRESS is getting truncated before it reaches this transformation.

Any thoughts.

Thanks,
SK

Did you try using a Data Conversion transformation?

Rafael Salas

|||

Hi,
I did try to use the Data Conversion transformation. But when I execute the package, I get the truncation error at the Data Source Reader itself.

Error: 0xC020902A at Data Flow Task, DataReader Source [1736]: The "component "DataReader Source" (1736)" failed because truncation occurred, and the truncation row disposition on "output column "ADDRESS" (2469)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.

Error: 0xC02090F5 at Data Flow Task, DataReader Source [1736]: The component "DataReader Source" (1736) was unable to process the data.

Error: 0xC0047038 at Data Flow Task, DTS.Pipeline: The PrimeOutput method on component "DataReader Source" (1736) returned error code 0xC02090F5. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.

Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "SourceThread0" has exited with error code 0xC0047038.

Error: 0xC0047039 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown.

Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" has exited with error code 0xC0047039


Thanks,
SK

|||

Hi,
Does anybody have inputs on this issue?

SK

|||

It sounds like the provider you are using is reporting the length of the string incorrectly as 0. I've seen that before with a provider, but I don't recall what one... Is there a different provider you can try?

Otherwise, you might try changing the select statement to cast the value explicitly to a string of length 30 and see if the DataReaderSrc correctly creates the column then.

|||

Unfortunately I can't use any other providers other than ADO.net as I have to use Oracle RDB ODBC to connect to RDB database.

Strangely, now the column is showing as text instead of Unicode string and I was able to use the data conversion transformation to convert back to Unicode String. Not sure what changed on the server. The only thing that I think of is we updated SQL Server with some updated from MS website.

Thanks,
SK

|||

We had the exact same problem trying to pull data from Oracle Rdb. I went round & round but eventually found the solution.

Basically we had to install SQL*Net for Rdb (or OCI Services for Rdb) on our VMS server to make our Rdb database look like an Oracle database. Then we had to install Oracle client software on our client machine. I've used both Oracle 9.2 client and ODAC 10.2. You then set up your client connection using the Oracle Net Manager.

After you've got client & server configured, set up an SSIS connection manager using .Net Providers for OleDb -> Oracle Provider for OLE DB.

It's kind of a hassle to set up but it seems to work just fine.

Regards, Pat

Error when changing sa password or when trying to access DB via sa

Hi,
Two weird things with the sa account, and I found a solution on
Microsoft.com, but it's not working.
First, when I go to change the SA password in Enterprise Manager, I
get the following error:
Error 21776: [SQL-DMO] The name 'dbo' was not found in the Users
collection. If the name is a qualified name, use [] to separate
various parts of the name, and try again.
So, I checked the knowledgebase and found this:
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q218/1/72.ASP&NoWebContent=1#appliesto
This is the exact issue I'm having, but when I run: sp_changedbowner
sa
... I get the following message in Query Analyzer:
Server: Msg 15109, Level 16, State 1, Procedure sp_changedbowner, Line
22
Cannot change the owner of the master database.
So, I searched for this error and found this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;328173
Catch-22... I need to change the Master DB to be owned by 'sa', yet it
won't let me change it since it's not already owned. Am I missing
something? This did happen just after I restored a database, just as
discribed in the first support doc, but it gives no exact syntax on
what to plug into Query Analyzer to resolve the issue, other then
using the sp_changedbowner stored procedure. And I must be using it
incorrectly to get the error, or it's another bug in MS SQL.
Can someone point me to the right direction? What should be an easy
back-up and restore is turning into a multi-hour ordeal.
Thanks,
Alex.If your a local admin or domain admin connect to the SQL Server using Query
Analyser and ask for a 'WinNT Authentication' then issue the following
command
A. Change the password of a login without a former password
This example changes the password for the login Victoria from a NULL
password to "B3r12-36".
EXEC sp_password NULL, 'B3r12-36', 'Victoria'
In EnterPrise manager Delete and Re-Register the troublesome server, when
registering use the new password.
--
HTH
Ryan Waight, MCDBA, MCSE
"Alex" <alex@.totallynerd.com> wrote in message
news:2ba4b4eb.0310270835.36d6e245@.posting.google.com...
> Hi,
> Two weird things with the sa account, and I found a solution on
> Microsoft.com, but it's not working.
> First, when I go to change the SA password in Enterprise Manager, I
> get the following error:
> Error 21776: [SQL-DMO] The name 'dbo' was not found in the Users
> collection. If the name is a qualified name, use [] to separate
> various parts of the name, and try again.
> So, I checked the knowledgebase and found this:
>
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q218/1/72.ASP&NoWebContent=1#appliesto
> This is the exact issue I'm having, but when I run: sp_changedbowner
> sa
> ... I get the following message in Query Analyzer:
> Server: Msg 15109, Level 16, State 1, Procedure sp_changedbowner, Line
> 22
> Cannot change the owner of the master database.
> So, I searched for this error and found this:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;328173
> Catch-22... I need to change the Master DB to be owned by 'sa', yet it
> won't let me change it since it's not already owned. Am I missing
> something? This did happen just after I restored a database, just as
> discribed in the first support doc, but it gives no exact syntax on
> what to plug into Query Analyzer to resolve the issue, other then
> using the sp_changedbowner stored procedure. And I must be using it
> incorrectly to get the error, or it's another bug in MS SQL.
> Can someone point me to the right direction? What should be an easy
> back-up and restore is turning into a multi-hour ordeal.
> Thanks,
> Alex.|||Yes, you cannot change database owner to MASTER.
If you run sp_helpuser on your restored database, should
show the "LoginName" as NULL if 'sa' do not own it.
You only needed to run sp_changedbowner on your restored
database. -->
use <restored_db>
go
sp_changedbowner 'sa'
go

error when changing published article at the subscriber

Hi


Using merge replication - the stored procs are published articles.


When trying to change the article at the subscriber (sql express) I get the following errors:

Msg 21531, Level 16, State 1, Procedure sp_MSmerge_alterschemaonly, Line 45
The DDL statement cannot be performed at the Subscriber or Republisher.

Msg 21530, Level 16, State 1, Procedure sp_MSmerge_ddldispatcher, Line 181
The DDL operation failed inside merge DDL replication manipulation.

Msg 3609, Level 16, State 2, Procedure usp_Anniversary_upd, Line 21
The transaction ended in the trigger. The batch has been aborted.

Does this mean it can only be changed at the publisher ?

Bruce

correct. If you want to make schema changes at the subscriber, you need to set @.replicate_ddl to false in sp_addmergepublication.|||

Schema changes cannot be made at the subscriber. They have to come from the Publisher.

Message: correct. If you want to make schema changes at the subscriber, you need to set @.replicate_ddl to false in sp_addmergepublication.

I believe Greg meant "publisher only" instead of "subscriber" in the above statement.

|||

Hi

Just to clarify this.....

1. You cannot change it at the subscriber, irrespective of whether @.replicate_ddl is set to 0 or 1 ?

2. If @.replicate_ddl is set to 1, then changing the proc on the publisher will result in the proc being changed at the subscriber next time it is synchronised (if a published article)


Is this correct ?

I ask, because @.replicate_ddl is set to 1, but I get that error mentioned earlier if I try and change it at the subscriber.....


Thanks
Bruce

|||

1. you're correct, i was wrong in my earlier post.

2. correct.

Error when changing job owner

When I change one of my job owners on a job that does a simple select, from
sa to a domain account, the job fails giving me the following error:
Could not obtain information about Windows NT group/user 'MyDomain\ADUser'
Error 8198.
I verified this login was a part of the Pre-Windows 2000 Compatible Access
Group (kb 241643). Next I tried using xp_logininfo with this login, and I
got the same error. Then I took out the select from the xp and ran it
separately (select distinct domain+N'\'+name, sid, sidtype from
OpenRowset(NetUserGetGroups, 'mydomain\aduser') and got the same error.
When I ran the above select statement with unknow domain\login, I got the
same error.
Any help would be appreciated.
Paul
You might want to have a look at
How to troubleshoot a SQL Server 8198 error
http://support.microsoft.com/default...b;en-us;834124
and
FIX: You Receive an Error Message When the xp_logininfo Extended Stored
Procedure Runs
http://support.microsoft.com/default.aspx?kbid=830596
Also make sure you are on the latest windows service pack
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Paul Bergstedt" <Paul@.nospam.com> wrote in message
news:uLmmgm4XEHA.3664@.TK2MSFTNGP12.phx.gbl...
> When I change one of my job owners on a job that does a simple select,
from
> sa to a domain account, the job fails giving me the following error:
> Could not obtain information about Windows NT group/user 'MyDomain\ADUser'
> Error 8198.
> I verified this login was a part of the Pre-Windows 2000 Compatible Access
> Group (kb 241643). Next I tried using xp_logininfo with this login, and I
> got the same error. Then I took out the select from the xp and ran it
> separately (select distinct domain+N'\'+name, sid, sidtype from
> OpenRowset(NetUserGetGroups, 'mydomain\aduser') and got the same error.
> When I ran the above select statement with unknow domain\login, I got the
> same error.
> Any help would be appreciated.
> Paul
>
|||After trying everying under the sun, I tried putting the server name into
the Pre-Windows 2000 Access Group, and that fixed the problem. I got this
idea after noticing that the service account that the SQL Server services
ran under was the local System Account. I would imagine if I were running
the services under a domain account that it too would need to be added. I
have a case open with Microsoft on this, so I will ask them to suggest
putting this info into the KB article listed below.
Paul
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:eybsju6XEHA.1764@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> You might want to have a look at
> How to troubleshoot a SQL Server 8198 error
> http://support.microsoft.com/default...b;en-us;834124
> and
> FIX: You Receive an Error Message When the xp_logininfo Extended Stored
> Procedure Runs
> http://support.microsoft.com/default.aspx?kbid=830596
> Also make sure you are on the latest windows service pack
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Paul Bergstedt" <Paul@.nospam.com> wrote in message
> news:uLmmgm4XEHA.3664@.TK2MSFTNGP12.phx.gbl...
> from
'MyDomain\ADUser'[vbcol=seagreen]
Access[vbcol=seagreen]
I[vbcol=seagreen]
the
>

Error when changing job owner

When I change one of my job owners on a job that does a simple select, from
sa to a domain account, the job fails giving me the following error:
Could not obtain information about Windows NT group/user 'MyDomain\ADUser'
Error 8198.
I verified this login was a part of the Pre-Windows 2000 Compatible Access
Group (kb 241643). Next I tried using xp_logininfo with this login, and I
got the same error. Then I took out the select from the xp and ran it
separately (select distinct domain+N'\'+name, sid, sidtype from
OpenRowset(NetUserGetGroups, 'mydomain\aduser') and got the same error.
When I ran the above select statement with unknow domain\login, I got the
same error.
Any help would be appreciated.
PaulYou might want to have a look at
How to troubleshoot a SQL Server 8198 error
http://support.microsoft.com/default.aspx?scid=kb;en-us;834124
and
FIX: You Receive an Error Message When the xp_logininfo Extended Stored
Procedure Runs
http://support.microsoft.com/default.aspx?kbid=830596
Also make sure you are on the latest windows service pack
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Paul Bergstedt" <Paul@.nospam.com> wrote in message
news:uLmmgm4XEHA.3664@.TK2MSFTNGP12.phx.gbl...
> When I change one of my job owners on a job that does a simple select,
from
> sa to a domain account, the job fails giving me the following error:
> Could not obtain information about Windows NT group/user 'MyDomain\ADUser'
> Error 8198.
> I verified this login was a part of the Pre-Windows 2000 Compatible Access
> Group (kb 241643). Next I tried using xp_logininfo with this login, and I
> got the same error. Then I took out the select from the xp and ran it
> separately (select distinct domain+N'\'+name, sid, sidtype from
> OpenRowset(NetUserGetGroups, 'mydomain\aduser') and got the same error.
> When I ran the above select statement with unknow domain\login, I got the
> same error.
> Any help would be appreciated.
> Paul
>|||After trying everying under the sun, I tried putting the server name into
the Pre-Windows 2000 Access Group, and that fixed the problem. I got this
idea after noticing that the service account that the SQL Server services
ran under was the local System Account. I would imagine if I were running
the services under a domain account that it too would need to be added. I
have a case open with Microsoft on this, so I will ask them to suggest
putting this info into the KB article listed below.
Paul
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:eybsju6XEHA.1764@.TK2MSFTNGP10.phx.gbl...
> You might want to have a look at
> How to troubleshoot a SQL Server 8198 error
> http://support.microsoft.com/default.aspx?scid=kb;en-us;834124
> and
> FIX: You Receive an Error Message When the xp_logininfo Extended Stored
> Procedure Runs
> http://support.microsoft.com/default.aspx?kbid=830596
> Also make sure you are on the latest windows service pack
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Paul Bergstedt" <Paul@.nospam.com> wrote in message
> news:uLmmgm4XEHA.3664@.TK2MSFTNGP12.phx.gbl...
> > When I change one of my job owners on a job that does a simple select,
> from
> > sa to a domain account, the job fails giving me the following error:
> >
> > Could not obtain information about Windows NT group/user
'MyDomain\ADUser'
> > Error 8198.
> >
> > I verified this login was a part of the Pre-Windows 2000 Compatible
Access
> > Group (kb 241643). Next I tried using xp_logininfo with this login, and
I
> > got the same error. Then I took out the select from the xp and ran it
> > separately (select distinct domain+N'\'+name, sid, sidtype from
> > OpenRowset(NetUserGetGroups, 'mydomain\aduser') and got the same error.
> > When I ran the above select statement with unknow domain\login, I got
the
> > same error.
> >
> > Any help would be appreciated.
> >
> > Paul
> >
> >
>

Error when changing job owner

When I change one of my job owners on a job that does a simple select, from
sa to a domain account, the job fails giving me the following error:
Could not obtain information about Windows NT group/user 'MyDomain\ADUser'
Error 8198.
I verified this login was a part of the Pre-Windows 2000 Compatible Access
Group (kb 241643). Next I tried using xp_logininfo with this login, and I
got the same error. Then I took out the select from the xp and ran it
separately (select distinct domain+N'\'+name, sid, sidtype from
OpenRowset(NetUserGetGroups, 'mydomain\aduser') and got the same error.
When I ran the above select statement with unknow domain\login, I got the
same error.
Any help would be appreciated.
PaulYou might want to have a look at
How to troubleshoot a SQL Server 8198 error
http://support.microsoft.com/defaul...kb;en-us;834124
and
FIX: You Receive an Error Message When the xp_logininfo Extended Stored
Procedure Runs
http://support.microsoft.com/default.aspx?kbid=830596
Also make sure you are on the latest windows service pack
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Paul Bergstedt" <Paul@.nospam.com> wrote in message
news:uLmmgm4XEHA.3664@.TK2MSFTNGP12.phx.gbl...
> When I change one of my job owners on a job that does a simple select,
from
> sa to a domain account, the job fails giving me the following error:
> Could not obtain information about Windows NT group/user 'MyDomain\ADUser'
> Error 8198.
> I verified this login was a part of the Pre-Windows 2000 Compatible Access
> Group (kb 241643). Next I tried using xp_logininfo with this login, and I
> got the same error. Then I took out the select from the xp and ran it
> separately (select distinct domain+N''+name, sid, sidtype from
> OpenRowset(NetUserGetGroups, 'mydomain\aduser') and got the same error.
> When I ran the above select statement with unknow domain\login, I got the
> same error.
> Any help would be appreciated.
> Paul
>|||After trying everying under the sun, I tried putting the server name into
the Pre-Windows 2000 Access Group, and that fixed the problem. I got this
idea after noticing that the service account that the SQL Server services
ran under was the local System Account. I would imagine if I were running
the services under a domain account that it too would need to be added. I
have a case open with Microsoft on this, so I will ask them to suggest
putting this info into the KB article listed below.
Paul
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:eybsju6XEHA.1764@.TK2MSFTNGP10.phx.gbl...
> You might want to have a look at
> How to troubleshoot a SQL Server 8198 error
> http://support.microsoft.com/defaul...kb;en-us;834124
> and
> FIX: You Receive an Error Message When the xp_logininfo Extended Stored
> Procedure Runs
> http://support.microsoft.com/default.aspx?kbid=830596
> Also make sure you are on the latest windows service pack
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Paul Bergstedt" <Paul@.nospam.com> wrote in message
> news:uLmmgm4XEHA.3664@.TK2MSFTNGP12.phx.gbl...
> from
'MyDomain\ADUser'[vbcol=seagreen]
Access[vbcol=seagreen]
I[vbcol=seagreen]
the[vbcol=seagreen]
>

Error when changing a group in code

I am getting the following error message when i attempt to set a date field as the group by condition in code.



"The group options for a date, time or date-time condition field must be a date group options object."



Does anyone know what this means or how it can be corrected? Im using VS2005 and ASP.NET

ThanksWell, I'm guessing that you need to provide a valid group option :)
i.e. do you want the dates grouped by day, week, month etc.|||Thanks for your reply. Yes it would seem i would need to set a valid group option but i think firstly for a group field that is using a date/time field the groupOptions property needs to be of type DateTimeGroupOptions. If originally the grouped field was a not date field you can't then change it to a date/time field because the GroupOptions property is Read-Only and can't be changed to the DateTimeGroupOptions object.