Showing posts with label error. Show all posts

Thursday, March 29, 2012

Getting a syntax error involving Microsoft.SqlServer.SmoEnum

Last month we upgraded our SQL Server 2000 production database to SQL Server
2005. It also has SP1 applied to it. I was just checking the jobs, making
certain that everything was running OK. We have 7 jobs defined, when I
clicked on the View Job History link on each of the job's property page, I
got a syntax error involving Microsoft.SqlServer.SmoEnum, but really nothing
else mentioned. Here is the text of the error message:
syntax error (ackup_SystemDBs_Weekly'']) (Microsoft.SqlServer.SmoEnum)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
Going to the link didn't help me.
So, how do I find out what's wrong and fix it, please?
RodHi Rod
Does this happen on every job? If it does then how did you upgrade the jobs?
You may want to manually see what is in the sysjobhistory table for that job.
You may want to use SQL Profiler to see what SQL is being called and check
that there is no errors.
Try running DBCC CHECKDB on MSDB.
If that does not work try scripting the job and creating it as a different
one, then disable the original.
John
"Rod" wrote:
> Last month we upgraded our SQL Server 2000 production database to SQL Server
> 2005. It also has SP1 applied to it. I was just checking the jobs, making
> certain that everything was running OK. We have 7 jobs defined, when I
> clicked on the View Job History link on each of the job's property page, I
> got a syntax error involving Microsoft.SqlServer.SmoEnum, but really nothing
> else mentioned. Here is the text of the error message:
> syntax error (ackup_SystemDBs_Weekly'']) (Microsoft.SqlServer.SmoEnum)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
>
> Going to the link didn't help me.
> So, how do I find out what's wrong and fix it, please?
> Rod
>
>
>|||John,
Of the 7 jobs that were in SQL Server 2000 before the upgrade, 6 of them
cause this error to occur. The 7th does work.
Rod
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:4226D126-BA6B-4E45-A6ED-553F767C2E7A@.microsoft.com...
> Hi Rod
> Does this happen on every job? If it does then how did you upgrade the
> jobs?
> You may want to manually see what is in the sysjobhistory table for that
> job.
> You may want to use SQL Profiler to see what SQL is being called and check
> that there is no errors.
> Try running DBCC CHECKDB on MSDB.
> If that does not work try scripting the job and creating it as a different
> one, then disable the original.
> John
> "Rod" wrote:
>> Last month we upgraded our SQL Server 2000 production database to SQL
>> Server
>> 2005. It also has SP1 applied to it. I was just checking the jobs,
>> making
>> certain that everything was running OK. We have 7 jobs defined, when I
>> clicked on the View Job History link on each of the job's property page,
>> I
>> got a syntax error involving Microsoft.SqlServer.SmoEnum, but really
>> nothing
>> else mentioned. Here is the text of the error message:
>> syntax error (ackup_SystemDBs_Weekly'']) (Microsoft.SqlServer.SmoEnum)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
>>
>> Going to the link didn't help me.
>> So, how do I find out what's wrong and fix it, please?
>> Rod
>>
>>|||Hi Rod
How important is the history? If not then try to re-create the job.
John
"Rod" wrote:
> John,
> Of the 7 jobs that were in SQL Server 2000 before the upgrade, 6 of them
> cause this error to occur. The 7th does work.
> Rod
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:4226D126-BA6B-4E45-A6ED-553F767C2E7A@.microsoft.com...
> > Hi Rod
> >
> > Does this happen on every job? If it does then how did you upgrade the
> > jobs?
> >
> > You may want to manually see what is in the sysjobhistory table for that
> > job.
> >
> > You may want to use SQL Profiler to see what SQL is being called and check
> > that there is no errors.
> >
> > Try running DBCC CHECKDB on MSDB.
> >
> > If that does not work try scripting the job and creating it as a different
> > one, then disable the original.
> >
> > John
> >
> > "Rod" wrote:
> >
> >> Last month we upgraded our SQL Server 2000 production database to SQL
> >> Server
> >> 2005. It also has SP1 applied to it. I was just checking the jobs,
> >> making
> >> certain that everything was running OK. We have 7 jobs defined, when I
> >> clicked on the View Job History link on each of the job's property page,
> >> I
> >> got a syntax error involving Microsoft.SqlServer.SmoEnum, but really
> >> nothing
> >> else mentioned. Here is the text of the error message:
> >>
> >> syntax error (ackup_SystemDBs_Weekly'']) (Microsoft.SqlServer.SmoEnum)
> >>
> >> For help, click:
> >> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
> >>
> >>
> >> Going to the link didn't help me.
> >>
> >> So, how do I find out what's wrong and fix it, please?
> >>
> >> Rod
> >>
> >>
> >>
> >>
> >>
>
>

Getting a syntax error involving Microsoft.SqlServer.SmoEnum

Getting a pool timeout error

I have pages which are using a master page.

An example page on my site would be the homepage, it makes 3 connections to mssql.

1) Get the keywords of the page

2) Get a list of news articles

3) Get the content of the page.

When I visual web express to debug the site it's giving me a pool error message, neither can I get the site to load directly via IIS. It says theres been a pool timeout.

I've read on the internet about making sure connections are closed when you are finished and I've checked that all database connections are closed using

finally
{
conn.Close();
}

does anyone have any idea why I would be having this problem?

How can I see what connections the site is opening, or maybe theres a limit on my server?

I'm using my own test server running windows 2003 and IIS

Don't increase the connection timeout unless there is a REAL need (15 sec by default).

Here are good links will help you hopfully:

http://blogs.msdn.com/angelsb/archive/2004/08/25/220333.aspx

http://www.15seconds.com/issue/040830.htm

http://kb.seekdotnet.com/ViewArticle.aspx?ID=35

Good luck.

|||

As far as I can see I have NO leaking connections.

And I'm sure this is relating to the bug in visual studio because this happens when I try to access the page directly via IIS.

Does anyone else have any ideas?

Is there some way I can view connections and their state when I'm debugging the site?

|||

Apply the latest service pack.

Yes, you can know the status by using one of the connection object proerity (con.status or something).

Good luck.

|||

Checkout this link:http://geekswithblogs.net/chrishan/archive/2007/07/18/114030.aspx

I hope it will help you.

Good luck.

|||

Thanks, I dont seem to be any further forward though.

One thing I have noticed is that in the Output window of Visual Studio I get the following error repeated constantly.

"A first chance exception of type 'System.Data.SqlClient.SqlException'' occurred in System.Data.Dll"

|||

Surely someone can help with this?

Like I say, I don't believe this problem is with Visual Studio, as it occurs when I run the site directly on the server.

Here is the procedure which seems to be causing the problem, when I dont include this function the site runs fine, however when I include it it wont run and I get the error in my above post in the output window.

1protected void setConfigKeywords()2 {3// Define data objects4 SqlConnection conn;5 SqlCommand comm;6 SqlDataReader reader;78// Read the connection string from web.config9string connectionString = ConfigurationManager.ConnectionStrings["AWT"].ConnectionString;1011// Initialise the connection12 conn =new SqlConnection(connectionString);1314// Create command15 comm =new SqlCommand("SELECT * FROM Config WHERE ConfigID = 1", conn);1617try18 {19// Open the connection20 //conn.Open();2122 // Execute the command23 reader = comm.ExecuteReader();2425while (reader.Read())26 {27string title = reader["ConfigMetaTitle"].ToString();28string keywords = reader["ConfigMetaKeywords"].ToString();29string description = reader["ConfigMetaDesc"].ToString();30 }3132//Page.Title = title;33 //HtmlHead head = (HtmlHead)Page.Header;34 //Cls_Meta.setHeaderInfo(head, description, keywords);3536 // Close the reader37 reader.Close();3839 }40catch (Exception ex)41 {42string errorPage = ConfigurationManager.AppSettings["errorPage"];43string errorMsg ="Problem getting general keywords from database : " + ex;44 Server.Transfer(errorPage +"?errormsg=" + errorMsg);45 }46finally47 {48// Close the connection49 conn.Close();50 }51 }

Getting a Major error.....

When i try to launch SQL 2005, I'm all of a sudden getting the following error:
"SqlWb.exe - Application Error
The application failed to initialize properly (0xc0000034). Click on OK to
terminate the application."
Any suggestions or recommendations? Tried to search the knowledgebase, but,
couldn't find anything.
Thanks.
JJ
Maybe I am wrong but looks like SqlWb is Management Studio so perhaps SQL
Server is really running. Try connecting from another client like Query
Analyzer to see if the instance is running.
With no additional information perhaps what I would try is rebooting the
computer and, if the problem is still there, reinstalling the client tools.
Regards,
Ben Nevarez
"Jeff" <Jeff@.discussions.microsoft.com> wrote in message
news:658463FC-52F7-493E-9FF7-7DA363D12681@.microsoft.com...
> When i try to launch SQL 2005, I'm all of a sudden getting the following
> error:
> "SqlWb.exe - Application Error
> The application failed to initialize properly (0xc0000034). Click on OK to
> terminate the application."
> Any suggestions or recommendations? Tried to search the knowledgebase,
> but,
> couldn't find anything.
> Thanks.
> --
> JJ

Getting a Major error.....

When i try to launch SQL 2005, I'm all of a sudden getting the following error:
"SqlWb.exe - Application Error
The application failed to initialize properly (0xc0000034). Click on OK to
terminate the application."
Any suggestions or recommendations? Tried to search the knowledgebase, but,
couldn't find anything.
Thanks.
--
JJMaybe I am wrong but looks like SqlWb is Management Studio so perhaps SQL
Server is really running. Try connecting from another client like Query
Analyzer to see if the instance is running.
With no additional information perhaps what I would try is rebooting the
computer and, if the problem is still there, reinstalling the client tools.
Regards,
Ben Nevarez
"Jeff" <Jeff@.discussions.microsoft.com> wrote in message
news:658463FC-52F7-493E-9FF7-7DA363D12681@.microsoft.com...
> When i try to launch SQL 2005, I'm all of a sudden getting the following
> error:
> "SqlWb.exe - Application Error
> The application failed to initialize properly (0xc0000034). Click on OK to
> terminate the application."
> Any suggestions or recommendations? Tried to search the knowledgebase,
> but,
> couldn't find anything.
> Thanks.
> --
> JJ

Getting a Major error.....

When i try to launch SQL 2005, I'm all of a sudden getting the following err
or:
"SqlWb.exe - Application Error
The application failed to initialize properly (0xc0000034). Click on OK to
terminate the application."
Any suggestions or recommendations? Tried to search the knowledgebase, but,
couldn't find anything.
Thanks.
JJMaybe I am wrong but looks like SqlWb is Management Studio so perhaps SQL
Server is really running. Try connecting from another client like Query
Analyzer to see if the instance is running.
With no additional information perhaps what I would try is rebooting the
computer and, if the problem is still there, reinstalling the client tools.
Regards,
Ben Nevarez
"Jeff" <Jeff@.discussions.microsoft.com> wrote in message
news:658463FC-52F7-493E-9FF7-7DA363D12681@.microsoft.com...
> When i try to launch SQL 2005, I'm all of a sudden getting the following
> error:
> "SqlWb.exe - Application Error
> The application failed to initialize properly (0xc0000034). Click on OK to
> terminate the application."
> Any suggestions or recommendations? Tried to search the knowledgebase,
> but,
> couldn't find anything.
> Thanks.
> --
> JJsql

Getting a error in DTS Active x script

Can anybody help me with this?

I'm trying to update three fields in one table from an import table. Is the anything you see missing in my code:

Dim rs1, strSQL

strSQL = "Select safety_valve_cap, hydro_date, hydro_psi, state_No From HBC_ZImport"
set rs1 = objConn.Execute(strSQL)

Do While NOT rs1.EOF

strSQL = "Update HBC_Boiler_Inspection set Safety_Valve_Cap = '" & rs1 ("Safety_Valve_Cap") & "', "
strSQL = strSQL & " Hydro_PSI = '" & rs1 ("Hydro_PSI") & "', "
strSQL = strSQL & " Hydro_Date = '" & rs1 ("Hydro_Date") & "' "
strSQL = strSQL & " where Boiler_ID = (Select ID from HBC_Boiler where State_No = ' " & rs1 ( "State_No") & " ') & " ' "
objConn.Execute(strSQL)

rs1.MoveNext()
Loop

Function Main()
Main = DTSTaskExecResult_Success
End FunctionLook at http://dbforums.com/t673820.html

Hugh Scott

Originally posted by Bigced_21
Can anybody help me with this?

I'm trying to update three fields in one table from an import table. Is the anything you see missing in my code:

Dim rs1, strSQL

strSQL = "Select safety_valve_cap, hydro_date, hydro_psi, state_No From HBC_ZImport"
set rs1 = objConn.Execute(strSQL)

Do While NOT rs1.EOF

strSQL = "Update HBC_Boiler_Inspection set Safety_Valve_Cap = '" & rs1 ("Safety_Valve_Cap") & "', "
strSQL = strSQL & " Hydro_PSI = '" & rs1 ("Hydro_PSI") & "', "
strSQL = strSQL & " Hydro_Date = '" & rs1 ("Hydro_Date") & "' "
strSQL = strSQL & " where Boiler_ID = (Select ID from HBC_Boiler where State_No = ' " & rs1 ( "State_No") & " ') & " ' "
objConn.Execute(strSQL)

rs1.MoveNext()
Loop

Function Main()
Main = DTSTaskExecResult_Success
End Function

Tuesday, March 27, 2012

Getting 644 Error in log

I am getting a pair of errors in the SQL Server log:
**
Could not find the index entry for
RID '367007017019022035037037038030303130313
030303037353836
353030323431324d415220202020202020' in index page
(1:126931), index ID 2, database 'ee8idbbd'..
**
AND
**
Error: 644, Severity: 21, State: 5
**
I looked in KB article 834290 and tried Method 2 on the
affected table. There were no columns that exhibited the
given symptoms, so either I did it wrong or this does not
apply.
Can someone help me diagnose this problem before it
happens again?1. Is that the build you are on at the moment (build 904 sqlservr.exe)? If
so, you might want to call into PSS to get that hotfix.
2. Do you get this error, as the KB article claims when you run an update
on READ UNCOMMITTED?
3. You might want to run a checkdb on the database and make sure that there
are no allocation or consistency errors.
Cheers.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Getting 644 Error in log

I am getting a pair of errors in the SQL Server log:
**
Could not find the index entry for
RID '3670070170190220350370370380303031303130303030373 53836
353030323431324d415220202020202020' in index page
(1:126931), index ID 2, database 'ee8idbbd'..
**
AND
**
Error: 644, Severity: 21, State: 5
**
I looked in KB article 834290 and tried Method 2 on the
affected table. There were no columns that exhibited the
given symptoms, so either I did it wrong or this does not
apply.
Can someone help me diagnose this problem before it
happens again?
1. Is that the build you are on at the moment (build 904 sqlservr.exe)? If
so, you might want to call into PSS to get that hotfix.
2. Do you get this error, as the KB article claims when you run an update
on READ UNCOMMITTED?
3. You might want to run a checkdb on the database and make sure that there
are no allocation or consistency errors.
Cheers.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Getting 644 Error in log

I am getting a pair of errors in the SQL Server log:
**
Could not find the index entry for
RID '367007017019022035037037038030303130313030303037353836
353030323431324d415220202020202020' in index page
(1:126931), index ID 2, database 'ee8idbbd'..
**
AND
**
Error: 644, Severity: 21, State: 5
**
I looked in KB article 834290 and tried Method 2 on the
affected table. There were no columns that exhibited the
given symptoms, so either I did it wrong or this does not
apply.
Can someone help me diagnose this problem before it
happens again?1. Is that the build you are on at the moment (build 904 sqlservr.exe)? If
so, you might want to call into PSS to get that hotfix.
2. Do you get this error, as the KB article claims when you run an update
on READ UNCOMMITTED?
3. You might want to run a checkdb on the database and make sure that there
are no allocation or consistency errors.
Cheers.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Getting 5105 error when I try to attach database

Forgive me for not making this clearer. I
sometimes forget I'm not always talking to other developers.
"jrpm" wrote:
[vbcol=seagreen]
> When you did the backup, did you specify a device or a file? If a device and
> you are restoring from the file, you may be seeing a header conflict.
> "Mark Miller" wrote:
|||I suggest to first try doing this from Query Analyzer using sp_attach_db and make sure you get the
parameters correct. Possibly, you need to specify correct path for the ldf file if not in same path
as on original SQL Server. If that doesn't work (and you feel that you got the parameters correct),
I'd try to attach the original files (before the file copy) on the originating server. If that work,
I'd copy the files over the network back onto the originating server and try to attach those
files...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Mark Miller" <MarkMiller@.discussions.microsoft.com> wrote in message
news:6637F49E-D3B5-4C20-800B-45CB72EE5F78@.microsoft.com...[vbcol=seagreen]
>I wasn't trying to back up data. I wanted to transfer data from one database
> to another, because I'm working on a software development project. The
> source database is behind a firewall, and I can't access it from my
> application on my development system. All I need is a subset of the data on
> the source database. So I decided to create a new database on the source
> instance, export the data I needed into it, detach it, and then copy it to my
> machine, where I have my own SQL Server 2000 instance, and where I was
> planning on accessing it from my application. I transferred it using a
> straight network file copy process (ie. copy from source file system and
> paste to destination file system). No tape backup was involved. Is the
> picture getting clearer now?

Forgive me for not making this clearer. I
> sometimes forget I'm not always talking to other developers.
> "jrpm" wrote:

Getting 5105 error when I try to attach database

Here's what I did. I created a new database on SQL Server 2000, on a remote
server, using Enterprise Manager. I then exported some data from another
database (same instance) into my new database. I then detached the database
I created, and copied the .MDF and .LDF files to my machine.
I've been trying to attach the .MDF and .LDF files, again using Enterprise
Manager (I'm also running SQL Server 2000). In EM, I tell it to Attach
Database... I give it the path to my .MDF and .LDF files, hit Verify, and
they verify (both the .MDF and .LDF file paths show up in the window,
checked). The problem comes when I hit OK. It gives me error 5105 (device
activation error), it gives the same path that I gave it, and says that the
filename may be wrong.
I don't think this is a permissions problem, and I've checked whether any
other process has grabbed ahold of it, and there isn't any. So I'm not sure
what's wrong. Please help.
Thanks.Miller -
Please go through the following link :-
http://support.microsoft.com/default.aspx?scid=kb;en-us;304261
Let me know if you where able to get the help for your problem.
Regards
"Mark Miller" wrote:
> Here's what I did. I created a new database on SQL Server 2000, on a remote
> server, using Enterprise Manager. I then exported some data from another
> database (same instance) into my new database. I then detached the database
> I created, and copied the .MDF and .LDF files to my machine.
> I've been trying to attach the .MDF and .LDF files, again using Enterprise
> Manager (I'm also running SQL Server 2000). In EM, I tell it to Attach
> Database... I give it the path to my .MDF and .LDF files, hit Verify, and
> they verify (both the .MDF and .LDF file paths show up in the window,
> checked). The problem comes when I hit OK. It gives me error 5105 (device
> activation error), it gives the same path that I gave it, and says that the
> filename may be wrong.
> I don't think this is a permissions problem, and I've checked whether any
> other process has grabbed ahold of it, and there isn't any. So I'm not sure
> what's wrong. Please help.
> Thanks.
>|||I tried turning on trace flag 1807, like the article says, to turn off the
check SQL Server does to detect if I'm accessing a database file through a
network share, and I get the same error. I gave this a try because it seemed
to be in the ballpark of my problem, but I'm not trying to access the
database file over a network share anyway. It's on my computer's hard drive.
Other than this bit of information in the article, nothing else in it seemed
relevant.
"surajits" wrote:
> Miller -
> Please go through the following link :-
> http://support.microsoft.com/default.aspx?scid=kb;en-us;304261
> Let me know if you where able to get the help for your problem.
> Regards
>
> "Mark Miller" wrote:
> > Here's what I did. I created a new database on SQL Server 2000, on a remote
> > server, using Enterprise Manager. I then exported some data from another
> > database (same instance) into my new database. I then detached the database
> > I created, and copied the .MDF and .LDF files to my machine.
> >
> > I've been trying to attach the .MDF and .LDF files, again using Enterprise
> > Manager (I'm also running SQL Server 2000). In EM, I tell it to Attach
> > Database... I give it the path to my .MDF and .LDF files, hit Verify, and
> > they verify (both the .MDF and .LDF file paths show up in the window,
> > checked). The problem comes when I hit OK. It gives me error 5105 (device
> > activation error), it gives the same path that I gave it, and says that the
> > filename may be wrong.
> >
> > I don't think this is a permissions problem, and I've checked whether any
> > other process has grabbed ahold of it, and there isn't any. So I'm not sure
> > what's wrong. Please help.
> >
> > Thanks.
> >|||When you did the backup, did you specify a device or a file? If a device and
you are restoring from the file, you may be seeing a header conflict.
"Mark Miller" wrote:
> I tried turning on trace flag 1807, like the article says, to turn off the
> check SQL Server does to detect if I'm accessing a database file through a
> network share, and I get the same error. I gave this a try because it seemed
> to be in the ballpark of my problem, but I'm not trying to access the
> database file over a network share anyway. It's on my computer's hard drive.
> Other than this bit of information in the article, nothing else in it seemed
> relevant.
> "surajits" wrote:
> > Miller -
> > Please go through the following link :-
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;304261
> >
> > Let me know if you where able to get the help for your problem.
> >
> > Regards
> >
> >
> > "Mark Miller" wrote:
> >
> > > Here's what I did. I created a new database on SQL Server 2000, on a remote
> > > server, using Enterprise Manager. I then exported some data from another
> > > database (same instance) into my new database. I then detached the database
> > > I created, and copied the .MDF and .LDF files to my machine.
> > >
> > > I've been trying to attach the .MDF and .LDF files, again using Enterprise
> > > Manager (I'm also running SQL Server 2000). In EM, I tell it to Attach
> > > Database... I give it the path to my .MDF and .LDF files, hit Verify, and
> > > they verify (both the .MDF and .LDF file paths show up in the window,
> > > checked). The problem comes when I hit OK. It gives me error 5105 (device
> > > activation error), it gives the same path that I gave it, and says that the
> > > filename may be wrong.
> > >
> > > I don't think this is a permissions problem, and I've checked whether any
> > > other process has grabbed ahold of it, and there isn't any. So I'm not sure
> > > what's wrong. Please help.
> > >
> > > Thanks.
> > >|||I wasn't trying to back up data. I wanted to transfer data from one database
to another, because I'm working on a software development project. The
source database is behind a firewall, and I can't access it from my
application on my development system. All I need is a subset of the data on
the source database. So I decided to create a new database on the source
instance, export the data I needed into it, detach it, and then copy it to my
machine, where I have my own SQL Server 2000 instance, and where I was
planning on accessing it from my application. I transferred it using a
straight network file copy process (ie. copy from source file system and
paste to destination file system). No tape backup was involved. Is the
picture getting clearer now? :) Forgive me for not making this clearer. I
sometimes forget I'm not always talking to other developers.
"jrpm" wrote:
> When you did the backup, did you specify a device or a file? If a device and
> you are restoring from the file, you may be seeing a header conflict.
> "Mark Miller" wrote:
> > I tried turning on trace flag 1807, like the article says, to turn off the
> > check SQL Server does to detect if I'm accessing a database file through a
> > network share, and I get the same error. I gave this a try because it seemed
> > to be in the ballpark of my problem, but I'm not trying to access the
> > database file over a network share anyway. It's on my computer's hard drive.
> > Other than this bit of information in the article, nothing else in it seemed
> > relevant.
> >
> > "surajits" wrote:
> >
> > > Miller -
> > > Please go through the following link :-
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;304261
> > >
> > > Let me know if you where able to get the help for your problem.
> > >
> > > Regards
> > >
> > >
> > > "Mark Miller" wrote:
> > >
> > > > Here's what I did. I created a new database on SQL Server 2000, on a remote
> > > > server, using Enterprise Manager. I then exported some data from another
> > > > database (same instance) into my new database. I then detached the database
> > > > I created, and copied the .MDF and .LDF files to my machine.
> > > >
> > > > I've been trying to attach the .MDF and .LDF files, again using Enterprise
> > > > Manager (I'm also running SQL Server 2000). In EM, I tell it to Attach
> > > > Database... I give it the path to my .MDF and .LDF files, hit Verify, and
> > > > they verify (both the .MDF and .LDF file paths show up in the window,
> > > > checked). The problem comes when I hit OK. It gives me error 5105 (device
> > > > activation error), it gives the same path that I gave it, and says that the
> > > > filename may be wrong.
> > > >
> > > > I don't think this is a permissions problem, and I've checked whether any
> > > > other process has grabbed ahold of it, and there isn't any. So I'm not sure
> > > > what's wrong. Please help.
> > > >
> > > > Thanks.
> > > >|||I suggest to first try doing this from Query Analyzer using sp_attach_db and make sure you get the
parameters correct. Possibly, you need to specify correct path for the ldf file if not in same path
as on original SQL Server. If that doesn't work (and you feel that you got the parameters correct),
I'd try to attach the original files (before the file copy) on the originating server. If that work,
I'd copy the files over the network back onto the originating server and try to attach those
files...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Mark Miller" <MarkMiller@.discussions.microsoft.com> wrote in message
news:6637F49E-D3B5-4C20-800B-45CB72EE5F78@.microsoft.com...
>I wasn't trying to back up data. I wanted to transfer data from one database
> to another, because I'm working on a software development project. The
> source database is behind a firewall, and I can't access it from my
> application on my development system. All I need is a subset of the data on
> the source database. So I decided to create a new database on the source
> instance, export the data I needed into it, detach it, and then copy it to my
> machine, where I have my own SQL Server 2000 instance, and where I was
> planning on accessing it from my application. I transferred it using a
> straight network file copy process (ie. copy from source file system and
> paste to destination file system). No tape backup was involved. Is the
> picture getting clearer now? :) Forgive me for not making this clearer. I
> sometimes forget I'm not always talking to other developers.
> "jrpm" wrote:
>> When you did the backup, did you specify a device or a file? If a device and
>> you are restoring from the file, you may be seeing a header conflict.
>> "Mark Miller" wrote:
>> > I tried turning on trace flag 1807, like the article says, to turn off the
>> > check SQL Server does to detect if I'm accessing a database file through a
>> > network share, and I get the same error. I gave this a try because it seemed
>> > to be in the ballpark of my problem, but I'm not trying to access the
>> > database file over a network share anyway. It's on my computer's hard drive.
>> > Other than this bit of information in the article, nothing else in it seemed
>> > relevant.
>> >
>> > "surajits" wrote:
>> >
>> > > Miller -
>> > > Please go through the following link :-
>> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;304261
>> > >
>> > > Let me know if you where able to get the help for your problem.
>> > >
>> > > Regards
>> > >
>> > >
>> > > "Mark Miller" wrote:
>> > >
>> > > > Here's what I did. I created a new database on SQL Server 2000, on a remote
>> > > > server, using Enterprise Manager. I then exported some data from another
>> > > > database (same instance) into my new database. I then detached the database
>> > > > I created, and copied the .MDF and .LDF files to my machine.
>> > > >
>> > > > I've been trying to attach the .MDF and .LDF files, again using Enterprise
>> > > > Manager (I'm also running SQL Server 2000). In EM, I tell it to Attach
>> > > > Database... I give it the path to my .MDF and .LDF files, hit Verify, and
>> > > > they verify (both the .MDF and .LDF file paths show up in the window,
>> > > > checked). The problem comes when I hit OK. It gives me error 5105 (device
>> > > > activation error), it gives the same path that I gave it, and says that the
>> > > > filename may be wrong.
>> > > >
>> > > > I don't think this is a permissions problem, and I've checked whether any
>> > > > other process has grabbed ahold of it, and there isn't any. So I'm not sure
>> > > > what's wrong. Please help.
>> > > >
>> > > > Thanks.
>> > > >sql

Getting 20533 Error as a result of subreports.

I am using VB6 with crystal reports version 8.5 (the OCX) and Access (Jet) database.

I have created a report which works fine on my dev machine and am trying to deploy to another machine.
When the report is run on the other machine an error 20533 Unable to open database error is received.
The report has an embedded subreport, which if I remove the subreport, works fine.
I have validated the database for both the main report and the subreport.

Here is the code I am using to run the report.

With MDIMain.CrystalReport
.ReportFileName = App.Path & "\reports\Summary.rpt"

.RetrieveDataFiles
Do Until .DataFiles(xCntr) = ""
.DataFiles(xCntr) = gSystem.DB_Path
xCntr = xCntr + 1
Loop
.SelectionFormula = "{OrderHeader.OrderID} =" & rsOrder("OrderID") '{?OrderID}
.ReportTitle = gSystem.Company_Name
.Action = 1
End With

I'm at a loss... any help would be apprieciated. Thanks.Hi all... I figured out what the issue was. It was fixed with the following code that sets the database location for the subreport.
I have posted the code fix for anyone else that may run into this issue.

Thanks to all that took a look at this for me.

With MDIMain.CrystalReport
.ReportFileName = App.Path & "\reports\Summary.rpt"
.RetrieveDataFiles
Do Until .DataFiles(xCntr) = ""
.DataFiles(xCntr) = gSystem.DB_Path
xCntr = xCntr + 1
Loop
.SelectionFormula = "{OrderHeader.OrderID} =" & rsOrder("OrderID")
.ReportTitle = gSystem.Company_Name

.SubreportToChange = "Selected Options"
.DataFiles(0) = gSystem.DB_Path

.SubreportToChange = ""
.Action = 1
End With

Getting "Report Server WMI Provider error: Not Found" while configuring Reporting Sevi

I'm Getting "Report Server WMI Provider error: Not Found" when trying to Grant Database Access while configuring the Reporting Sevices Integration. Logging in fine to the DB. Tried all the WMI troublshooting and can't find any issues there. Any tips?

Many Thanks!!

I’m experiencing the same problem. Windows 2003 Server Standard, MSSQL 2005, SharePoint Services 3.0.

I hope someone is going to find a solution soon.

Thanks.

|||So sounds like a bug; I'll look into reporting it as such and maybe it'll get addressed in the next release. Guess that's what CTP's all about. Oh well, at least it seems it wasn't my screw-up for a change :)|||

Do you see the same error when connecting to the Report Server using the RS Config tool?

thanx,
Prash

|||

No, I'm able to connect and config the RS with that tool; also I can access and use report manager; here's something that I don't know whether is correct or not: when I browse to my reportserver virtual directory, I see a directory browsing type view een though directory browsing's not selected in IIS:

wctestserv/ReportServer - /

Thursday, February 01, 2007 10:07 AM <dir> Users Folders

Microsoft SQL Server Reporting Services Version 9.00.2047.00

</page text>

Granted there are no reports on this site yet, but it's interesting (irritating) that I can't get the sharepoint report explorer web part to work with my report server either; same cause/issue?

Thanks!

|||

Looks like you have Report Server running in Native mode.

You need to switch it to SharePoint integrated mode before using "Grant Database Access" and other RS pages in the Central Admin. Refer to the following in SQL SP2 CTP BOL for more details: "How to: Create a Report Server Database for SharePoint Integrated Mode (Reporting Services Configuration) "

In any case, if you simply need to run the Report Explorer web part that worked in WSS 2.0 then should not have to switch the Report Server to SharePoint Integrated mode. Refer to section 4.1.1 in the SP2 readme @.http://download.microsoft.com/download/5/1/3/513534ae-a0e7-44e6-9a04-ba3c549a5f5f/sp2Readme_EN.htm
Note: you may want to use the -globalinstall switch with stsadm.exe in order to successfully connect the Report Explorer to the Report Viewer web part.

HTH
Prash

|||

I'm using SharePoint Services 3.0, so I don't have to mention Service Pack 2 I guess.

I still get the same problem: Report Server WMI Provider error: Not found while doing grand database access.

Thx.

|||Thanks, I figured out the report explorer; I was pointing at ReportServer VD when I shoulda been pointing at ReportManager VD (/reports); works well now (except getting it to connect with the reportviewer webpart, but that's for another forum) :). So somwhere I assume there's a config to switch my report server to integrated mode(?); I'll review those references you cite. Thanks for your help!!|||

Hi Prash,

I'm using WSS3.0 + MOSS 2007, so switch RS to "SharePoint Integrated Mode" would be best fit and thus can use the RS wbe part to render the reports in an easy way.

However, I can still not pass the "Grant Database Access" page, it pop-up:

The group name could not be found

Any advice?

Paul

|||I'm getting the same error message.|||

Refer to the following thread for the latest status on this:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1126475&SiteID=1

thanx,
Prash

Getting "Report Server WMI Provider error: Not Found" while configuring Reporting Sevi

Many Thanks!!

I’m experiencing the same problem. Windows 2003 Server Standard, MSSQL 2005, SharePoint Services 3.0.

I hope someone is going to find a solution soon.

Thanks.

Do you see the same error when connecting to the Report Server using the RS Config tool?

thanx,
Prash

|||

wctestserv/ReportServer - /

Thursday, February 01, 2007 10:07 AM <dir> Users Folders

Microsoft SQL Server Reporting Services Version 9.00.2047.00

</page text>

Granted there are no reports on this site yet, but it's interesting (irritating) that I can't get the sharepoint report explorer web part to work with my report server either; same cause/issue?

Thanks!

|||

Looks like you have Report Server running in Native mode.

HTH
Prash

|||

I'm using SharePoint Services 3.0, so I don't have to mention Service Pack 2 I guess.

I still get the same problem: Report Server WMI Provider error: Not found while doing grand database access.

Thx.

Hi Prash,

I'm using WSS3.0 + MOSS 2007, so switch RS to "SharePoint Integrated Mode" would be best fit and thus can use the RS wbe part to render the reports in an easy way.

However, I can still not pass the "Grant Database Access" page, it pop-up:

The group name could not be found

Any advice?

Paul

|||I'm getting the same error message.|||

Refer to the following thread for the latest status on this:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1126475&SiteID=1

thanx,
Prash

Getting "Report Server WMI Provider error: Not Found" while configuring Reporting

Many Thanks!!

I’m experiencing the same problem. Windows 2003 Server Standard, MSSQL 2005, SharePoint Services 3.0.

I hope someone is going to find a solution soon.

Thanks.

Do you see the same error when connecting to the Report Server using the RS Config tool?

thanx,
Prash

|||

wctestserv/ReportServer - /

Thursday, February 01, 2007 10:07 AM <dir> Users Folders

Microsoft SQL Server Reporting Services Version 9.00.2047.00

</page text>

Granted there are no reports on this site yet, but it's interesting (irritating) that I can't get the sharepoint report explorer web part to work with my report server either; same cause/issue?

Thanks!

|||

Looks like you have Report Server running in Native mode.

HTH
Prash

|||

I'm using SharePoint Services 3.0, so I don't have to mention Service Pack 2 I guess.

I still get the same problem: Report Server WMI Provider error: Not found while doing grand database access.

Thx.

Hi Prash,

I'm using WSS3.0 + MOSS 2007, so switch RS to "SharePoint Integrated Mode" would be best fit and thus can use the RS wbe part to render the reports in an easy way.

However, I can still not pass the "Grant Database Access" page, it pop-up:

The group name could not be found

Any advice?

Paul

|||I'm getting the same error message.|||

Refer to the following thread for the latest status on this:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1126475&SiteID=1

thanx,
Prash

Getting "extremely complex query" error when using xml data type parameters

Good morning, I am trying to figure out, and understand, why I am receiving the error that I am when I use xml data type parameters. If you look at the proc below, I have a proc with 8 xml data type parameters. When i call this proc adn pass in the values for the parameters, I recieve is the following:

The query processor ran out of internal resources and could not produce a query plan.

This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions.

Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information.

In debugging, I found that I DON'T get this error if i have only 3 or 4 xml data type parameters, but if I add more than 4, I get the above error.

The proc looks like the following:

CREATE PROCEDURE dbo.dosomething

@.BegDate DateTime,

@.EndDate DateTime,

@.InClass xml,

@.InDept xml,

@.InCat xml,

@.InPayPer xml,

@.InEmp xml,

@.InLoc xml,

@.InLeave xml,

@.InSalClass xml

SELECT blah, blah

FROM blah

WHERE table.column IN (select [JoinValues].[ref].value('@.id', 'int') from @.InEmp.nodes('ids/values') JoinValues([ref])

AND...join other xml datatypes just like the one above

I call the stored proc by the following...and notice that i am not passing anything very large for each value...

exec dosomething

'20060101','20060101',

N'<ids>

</ids>'

,N'<ids>

</ids>',

N'<ids>

</ids>',

N'<ids>

</ids>',

N'<ids>

</ids>',

N'<ids>

</ids>',

N'<ids>

</ids>',

N'<ids>

</ids>'

Does anyone have any suggestions as to what might be causing this? Am i doign my compare in my proc incorrectly? Any insight would be greatly appreciated...

Scott

Hi Scott

This error message normally means that you should rewrite your query. Could you please post a complete repro to either my work address (mrys at the microsoft.com address) or post it here and we will take a look.

Thanks

Michael

PS: Sorry I thought I posted this reply yesterday but my travel connectivity at the moment seems to be shakey.

|||

I guess the problem is not you have lots xml data type parameters. It's caused by the WHERE clause in your query :

"WHERE table.column IN (select [JoinValues].[ref].value('@.id', 'int') from @.InEmp.nodes('ids/values') JoinValues([ref])

AND...join other xml datatypes just like the one above"

You can try to define some temp tables and shred the ID values in the xml into those tables. Jojn those temp tables in your query.

Getting "An existing connection was forcibly closed by the remote host (System)" error

I cannot connect to Analysis Services through SSMS. Receiving a "An existing connection was forcibly closed by the remote host (System) error." I changed my password this morning due to our company security policies and now I can't do squat. This is definitely a bug in the service as something is cached and not clearing out. I've rebooted both the server and client a couple of times. Running AS 2005 SP1 on Windows Server 2003. I can connect through another machine. Here's the message I'm getting. Don't know where to look to fix the problem.

===================================

Cannot connect to hctx-idwdev.

===================================

A connection cannot be made. Ensure that the server is running. (Microsoft.AnalysisServices.AdomdClient)

Program Location:

at Microsoft.AnalysisServices.AdomdClient.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.AdomdConnection.IXmlaClientProviderEx.ConnectXmla()
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

===================================

Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. (System)

Program Location:

at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count)
at Microsoft.AnalysisServices.AdomdClient.DimeRecord.ForceRead(Stream stream, Byte[] buffer, Int32 length)
at Microsoft.AnalysisServices.AdomdClient.DimeRecord.ReadHeader()
at Microsoft.AnalysisServices.AdomdClient.DimeRecord..ctor(Stream stream)
at Microsoft.AnalysisServices.AdomdClient.DimeReader.ReadRecord()
at Microsoft.AnalysisServices.AdomdClient.TcpStream.GetResponseDataType()

===================================

An existing connection was forcibly closed by the remote host (System)

Program Location:

at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)

I've uninstalled the client tools and reinstalled. After rebooting, I STILL CANNOT CONNECT TO ANALYSIS SERVICES FROM THIS MACHINE.

Major issue addressed in next service pack? Is there a local cache I need to clear? Any help would be greatly appreciated.

|||Fixed the problem even though the solution is less than ideal. To resolve, we had to delete my user profile on the machine. Apparently, something used by the drivers is being stored in the Document and Settings for the current user. What exactly we weren't able to identify.

Monday, March 26, 2012

Getting #Error with aggregate function

Why doesn't this return a value?
=Sum(IIf(Fields!GroupCode.Value = 10, Fields!Rating.Value, 0))
I am getting #Error as the value. This however gives me a value:
=Sum(IIf(Fields!GroupCode.Value = 10, 1, 0))
However, I need the above to work...I need it to sum the rating if it's
part of a particular group.Here are some additional findings...
The following code works:
=Sum(IIf(Fields!GroupCode.Value = 10, CInt(Fields!Rating.Value), 0))
The following code fails:
=Sum(IIf(Fields!GroupCode.Value = 10, 1.20, 0))
=Sum(IIf(Fields!GroupCode.Value = 10, CDbl(Fields!Rating.Value), 0))
Why is it that it can only sum up intergers?|||I figured it out!!
The following code works:
=Sum(IIf(Fields!GroupCode.Value = 10, 1.20, 0.0))
Both the true and false values need to be of the same type. By return
0 as my false condition value, and 1.2 as my true condition, it caused
it to fail because it's returning different data types base on the
different condition.
This is bad, MS needs to fix this.

Getting #Error details from deployed report

I have a report that displays #Error for some field values when deployed on the server. Is there any way to get details on the error?

Thanks.

Most likely the #Error comes from making a call into a custom assembly and insufficient security permissions for that custom assembly to be invoked.

You can partially simulate the server environment, if you run the report in the stand-alone preview of report designer. I.e. instead of clicking on the Preview tab, hit F5 which should open a new window for the stand-alone preview. For the #Error you should get warning messages with more details in the output window.

-- Robert

Thursday, March 29, 2012

Getting a syntax error involving Microsoft.SqlServer.SmoEnum

Getting a syntax error involving Microsoft.SqlServer.SmoEnum

Getting a pool timeout error

Getting a Major error.....

Getting a Major error.....

Getting a Major error.....

Getting a error in DTS Active x script

Tuesday, March 27, 2012

Getting 644 Error in log

Getting 644 Error in log

Getting 644 Error in log

Getting 5105 error when I try to attach database

Getting 5105 error when I try to attach database

Getting 20533 Error as a result of subreports.

Getting "Report Server WMI Provider error: Not Found" while configuring Reporting Sevi

wctestserv/ReportServer - /

Getting "Report Server WMI Provider error: Not Found" while configuring Reporting Sevi

wctestserv/ReportServer - /

Getting "Report Server WMI Provider error: Not Found" while configuring Reporting

wctestserv/ReportServer - /

Getting "extremely complex query" error when using xml data type parameters

Getting "An existing connection was forcibly closed by the remote host (System)" error

Monday, March 26, 2012

Getting #Error with aggregate function

Getting #Error details from deployed report

Failure Details

Blog Archive

About Me