Page (1:368132)

Hi,
Can i know the DBID with this reference Page (1:368132)'
I'm getting this error
EventID: 0x4000429C (17052) - Error: 7105, Severity: 22,
State: 6
Page (1:370082), slot 5 for text, ntext, or image node
does not exist.
Can anyone help '
Thanks in advance
Celso CorreiaUnfortunately, no. Please look at the errorlog and see if there are any
other related error messages that may tell you which database has this
problem.
This error could be caused by a database page corruption. So please run dbcc
checktable after you have determined which database/table has the issue.
Based on the page id, the database file could be quite large: about 2.9GB.
This might help.
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Miguel" <anonymous@.discussions.microsoft.com> wrote in message
news:070a01c494ca$d8f165a0$a401280a@.phx.gbl...
> Hi,
> Can i know the DBID with this reference Page (1:368132)'
> I'm getting this error
> EventID: 0x4000429C (17052) - Error: 7105, Severity: 22,
> State: 6
> Page (1:370082), slot 5 for text, ntext, or image node
> does not exist.
> Can anyone help '
> Thanks in advance
> Celso Correia
>

Page (1:368132)

Hi,
Can i know the DBID with this reference Page (1:368132)?
I'm getting this error
EventID: 0x4000429C (17052) - Error: 7105, Severity: 22,
State: 6
Page (1:370082), slot 5 for text, ntext, or image node
does not exist.
Can anyone help ?
Thanks in advance
Celso Correia
Unfortunately, no. Please look at the errorlog and see if there are any
other related error messages that may tell you which database has this
problem.
This error could be caused by a database page corruption. So please run dbcc
checktable after you have determined which database/table has the issue.
Based on the page id, the database file could be quite large: about 2.9GB.
This might help.
Wei Xiao [MSFT]
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Miguel" <anonymous@.discussions.microsoft.com> wrote in message
news:070a01c494ca$d8f165a0$a401280a@.phx.gbl...
> Hi,
> Can i know the DBID with this reference Page (1:368132)?
> I'm getting this error
> EventID: 0x4000429C (17052) - Error: 7105, Severity: 22,
> State: 6
> Page (1:370082), slot 5 for text, ntext, or image node
> does not exist.
> Can anyone help ?
> Thanks in advance
> Celso Correia
>

Package loses configuration files!

I created a project with multiple packages. I created a global config file that all packages reference. I also created a config file for each package that contains the package specific settings. I checked it all into TFS. I went to a different machine and checked it all out. Upon loading a package into the IDE I got the following 3 warnings.

Warning loading MT_LSE_PROD_StageLoad.dtsx: The configuration file "MT_LSE_PROD_StageLoad.dtsConfig" cannot be found. Check the directory and file name. e:\contentloader\sprint1a\MT_LSE_PROD_StageLoad.dtsx

Warning loading MT_LSE_PROD_StageLoad.dtsx: The configuration file "Environment.dtsConfig" cannot be found. Check the directory and file name. e:\contentloader\sprint1a\MT_LSE_PROD_StageLoad.dtsx

Warning loading MT_LSE_PROD_StageLoad.dtsx: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to see descriptions of which configuration failed. e:\contentloader\sprint1a\MT_LSE_PROD_StageLoad.dtsx

Any ideas? And yes, the files *ARE* there! I tried building the project and it builds. I also tried doing a deployment build and that too built. I am so confused!!!

Are you using SQL2005/Express SP1? As I know there used to be a known issue with SP1: if you use configuration file to deploy SSIS package, the referenced file names in the configuraiton file will be change to lowercase. Since XML file is case-sensitive, the files can't be found if the name does not exactly match. Not sure whether there is any hotfix available now.|||We are using SQL 2005 Enterprise. I believe it is SP1 as well. Will see if naming everything in lower case only fixes it up. Thanks.sql