Good Day.
Why the following message may appear:
WCCOArdb (97), 2020.09.25 11:46:07.417, IMPL, SEVERE, 51, Parameter incorrect, DpType, setName, TypeId must not be 0!
RDB. TypeId must not be 0!
- mhargreaves
- Posts:84
- Joined: Thu Nov 11, 2010 12:31 pm
Re: RDB. TypeId must not be 0!
Did you resolve this issue? We are having the same message.
- dbindernagel
- Posts:161
- Joined: Mon Feb 23, 2015 1:34 pm
Re: RDB. TypeId must not be 0!
I did get this message now too, although for the NGA.
WinCC OA 3.18 P013
NGA with MS SQL; In-Proc (Backend as plugin); The SQL Server is on a different machine.
We switched from InfluxDB to MS SQL.
Steps:
1. Set the old InfluxDB backend offline
2. Create a new MS SQL backend
3. Switch the existing Groups to the new backend
4. Restart the project.
When I query archive data it seems to work (meaning I get archived data and the buffer count is 0) but I get the same error messages
I tried deleting these segments (only the ones with status "Current" remain; one segment for each group) but this did not fix the problem.
Archiving and querying historical data seems to be working just fine. I can see historical data and the buffer is 0 and "Not Changing".
Does anyone have any information about these messages?
Another problem is that one query is giving a warning that there are too many values (which is correct, there was a problem with the archiving in the old InfluxDB). But the new MS SQL database should be mostly empty.
Where is the system looking for this count and how can I reset it?
WinCC OA 3.18 P013
NGA with MS SQL; In-Proc (Backend as plugin); The SQL Server is on a different machine.
We switched from InfluxDB to MS SQL.
Steps:
1. Set the old InfluxDB backend offline
2. Create a new MS SQL backend
3. Switch the existing Groups to the new backend
4. Restart the project.
When I query archive data it seems to work (meaning I get archived data and the buffer count is 0) but I get the same error messages
Under segments I could see that I had many segments from before the switch. Not sure how these have been created as the MS SQL database was completely new.WCCOAnextgenarch(118), 2023.01.19 15:42:44.982, IMPL, SEVERE, 51, Parameter incorrect, DpType, setName, TypeId must not be 0!
I tried deleting these segments (only the ones with status "Current" remain; one segment for each group) but this did not fix the problem.
Archiving and querying historical data seems to be working just fine. I can see historical data and the buffer is 0 and "Not Changing".
Does anyone have any information about these messages?
Another problem is that one query is giving a warning that there are too many values (which is correct, there was a problem with the archiving in the old InfluxDB). But the new MS SQL database should be mostly empty.
Where is the system looking for this count and how can I reset it?
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: RDB. TypeId must not be 0!
According to the information in our internal database the cause for the NGA log message "TypeId must not be 0" was found. It is planned to fix it within the next patch.
When you have questions concerning log message we need to see the complete log message.
The most common log messages are explained in Support --> Knowledge Base --> Log-Messages.
Best Regards
Leopold Knipp
Senior Support Specialist
When you have questions concerning log message we need to see the complete log message.
The most common log messages are explained in Support --> Knowledge Base --> Log-Messages.
Best Regards
Leopold Knipp
Senior Support Specialist