Showing posts with label servers. Show all posts
Showing posts with label servers. Show all posts

Thursday, March 22, 2012

Errors: SQL Reporting Services with CRM 3.0

Good Day All ...

I am currently trying to install CRM 3.0 onto one of our test servers.
I have managed with no problem to get everything ready for installation ... but having a problem with reporting services.

On the system requirements results page i have green for everything but reporting services.

ERROR;
Specified Reporting Services Reports Server http://XXXXXX/ReportsServer was not found.

I have reporting services installed, can someone please give me some direction on where to go from here to get this up and working.

Thanks

Do you habe any Sharepoint Server installed on the machine or any other program which tries to bind port 80 to itself ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||Yes i do have sharepoint installed.
Would you recommend removing that?|||

Hi,

no defintely not, but you should have a look on my site under the Screencast Section, this will whow you a way to solve your problem.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Thanks for all of your help.
Works fine.

Thanks Again ... Great Advice!!|||If this helped please mark post as answer and (for me) rate the screencast and give additional feedback if you want to :-)

HTH, Jens K. SUessmeyer.

http://www.sqlserver2005.de

Wednesday, March 21, 2012

Errors with SRS in Sharepoint Integration Mode

Hi Everyone,

Our project has two servers. One server is running WSS 3.0 and the SQL Reporting Services web front-end. We have a second server that operates all the databases involved (WSS Content, SRS, and our application specific DB).

We do not have a domain controller in our architecture. The WSS site is configured to use SQL authentication to connnect and modify the WSS Content database. We installed SRS, SRS service pack 2, and the Sharepoint add-in. We are using forms authentication for our WSS site. We would like to use SRS in Sharepoint Integration mode, but we are unable to create datasources, view reports, etc. SRS is configured to use the "Trusted Account" in WSS Central Admin.

When we attempt to create a new datasource, and we received an error stating the object moved and to check that SRS is in Sharepoint integration mode.

When we attempt to view a report, we get an error stating:

"An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode."

I have a feeling this has to do with the Windows Service Account and the Web Service Identity for SRS. What type of account should we use since we do not have a domain?

Thank you,

Michael milazzo

As explained here, in Trusted Account mode, WSS sends the requests to the Report Server under the identity of the SharePoint application. By default, the IIS 6.0 application pool runs under NT AUTHORITY\Network Service. Since you don't have a domain setup, try changing the application domain identity to a local Windows user account which has the same name and password as a privileged account on the Report Server that has access to the report catalog. If you had domain setup, the request could have gone under Domain\WSS machine name$ and you could have granted access to that account.

Errors when running DBCC CheckCatalog command

One of my users reported an error when testing against one of our Development
Servers, against a user databases. The error the application generated
contained the following:
Could not find row in sysindexes for database ID 9, object ID 1284406774,
index ID -1. Run DBCC CHECKTABLE on sysindexes.
I ran DBCC CHECKTABLE (sysindexes) and it came back clean.
I then ran DBCC CHECKDB, which came back clean.
Then, I ran DBCC CHECKALLOC, which came back clean.
Next, I ran DBCC CHECKCATALOG, which gave the following errors:
Server: Msg 2513, Level 16, State 2, Line 2
Table error: Object ID 823165107 (object '823165107') does not match between
'SYSCOLUMNS' and 'SYSOBJECTS'.
Server: Msg 2513, Level 16, State 1, Line 2
Table error: Object ID 823165107 (object '823165107') does not match between
'SYSCOLUMNS' and 'SYSOBJECTS'.
Server: Msg 2513, Level 16, State 1, Line 2
Table error: Object ID 823165107 (object '823165107') does not match between
'SYSCOLUMNS' and 'SYSOBJECTS'.
Server: Msg 2513, Level 16, State 1, Line 2
Table error: Object ID 823165107 (object '823165107') does not match between
'SYSCOLUMNS' and 'SYSOBJECTS'.
Server: Msg 2513, Level 16, State 1, Line 2
Table error: Object ID 823165107 (object '823165107') does not match between
'SYSCOLUMNS' and 'SYSOBJECTS'.
Server: Msg 2513, Level 16, State 1, Line 2
Table error: Object ID 823165107 (object '823165107') does not match between
'SYSCOMMENTS' and 'SYSOBJECTS'.
DBCC results for 'current database'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
I was not too worried, since this was a DEV server, but then I ran the DBCC
CHECKCATAOG command against our QA and then our Production server, and all
of them gave me the same error for the DBCC CHECKCATAOG command.
Any ideas on what I can try next? I don't think this is a corrupt index and
I can't run DBCC DBREINDEX against a system table.
Thank you in advance.
SamAre you on 7.0? If so, search KB for 2513, I found a few articles. If you are on 2000, I suggest you
open a case with MS Support for this.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:9FF30A6F-9DC1-4DE6-838E-8BA9D1FD15F4@.microsoft.com...
> One of my users reported an error when testing against one of our Development
> Servers, against a user databases. The error the application generated
> contained the following:
> Could not find row in sysindexes for database ID 9, object ID 1284406774,
> index ID -1. Run DBCC CHECKTABLE on sysindexes.
> I ran DBCC CHECKTABLE (sysindexes) and it came back clean.
> I then ran DBCC CHECKDB, which came back clean.
> Then, I ran DBCC CHECKALLOC, which came back clean.
> Next, I ran DBCC CHECKCATALOG, which gave the following errors:
> Server: Msg 2513, Level 16, State 2, Line 2
> Table error: Object ID 823165107 (object '823165107') does not match between
> 'SYSCOLUMNS' and 'SYSOBJECTS'.
> Server: Msg 2513, Level 16, State 1, Line 2
> Table error: Object ID 823165107 (object '823165107') does not match between
> 'SYSCOLUMNS' and 'SYSOBJECTS'.
> Server: Msg 2513, Level 16, State 1, Line 2
> Table error: Object ID 823165107 (object '823165107') does not match between
> 'SYSCOLUMNS' and 'SYSOBJECTS'.
> Server: Msg 2513, Level 16, State 1, Line 2
> Table error: Object ID 823165107 (object '823165107') does not match between
> 'SYSCOLUMNS' and 'SYSOBJECTS'.
> Server: Msg 2513, Level 16, State 1, Line 2
> Table error: Object ID 823165107 (object '823165107') does not match between
> 'SYSCOLUMNS' and 'SYSOBJECTS'.
> Server: Msg 2513, Level 16, State 1, Line 2
> Table error: Object ID 823165107 (object '823165107') does not match between
> 'SYSCOMMENTS' and 'SYSOBJECTS'.
> DBCC results for 'current database'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> I was not too worried, since this was a DEV server, but then I ran the DBCC
> CHECKCATAOG command against our QA and then our Production server, and all
> of them gave me the same error for the DBCC CHECKCATAOG command.
> Any ideas on what I can try next? I don't think this is a corrupt index and
> I can't run DBCC DBREINDEX against a system table.
> Thank you in advance.
> Sam
>
>

Friday, March 9, 2012

Errors Copying Data Base

I'm trying to copy a data base from one server to another. Both servers are running 2005 MSDE, on Win 2k3, the target server is 64 bit.

I'm using the Copy Database function, and ultimately it fails with the error in the event viewer in the targe machine:

Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a, faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug? 0, fault address 0x0000000000027d0d.

I have tried both the Attach/Detach & the SMO method, and they both give me the same error. I have 'Repaired' the .NET framework on the target machine, with the same result.

Does anyone have any Suggestions? I really only need at this time to make one copy of the database.

Thanks

Phil

When you say "2005 MSDE", do you mean "2005 Express Edition"? You mentioned the target server is 64bit, is it IA64 or AMD64? My best guess is that you installed x86 version of SQL Server Express on AMD64 platform with WOW option.

Thanks,

Zhiqiang Feng

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

I have the x64 version of the Developer Edition of MS Sql Server 2005 installed on an AMD64 platform.

|||

More completely, the source server is a 32 bit machine, with MS Sql Server Developer Edition 2005, the target machine is the x64 configuration.

I have tried to initiate the transfer from both ends, i.e. the from the platform with the database pushing it to the platform without the DB, and from the platform without the DB, pulling it from the platform with the db

|||

Move the thread to the right alias. SSIS experts should be able to help out on your problem.

Thanks,

Zhiqiang Feng

This posting is provided "AS IS" with no warranties, and confers no rights.

|||the ssis transfer database task should help: http://msdn2.microsoft.com/en-us/library/ms141204.aspx

Friday, February 24, 2012

Error::"Server: Msg 7399, Level 16, State 1, Line 1"

Hi,
I am using link server btw. 2 SQL Servers.
From Server A to Server B it connected without any
problem.
But from Server B to Server A it is giving this error.
And idea'?Running out of choices..
Error msg :
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error. The provider
did not give any information about the error.
Thanks in advance,
SachiI did a very quick search on Google using your error message and there are
quite a few things that may cause this error. It may be worth your while
having a look through to see if any apply.
--
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Sachi" <sachiek_sachiek@.hotmail.com> wrote in message
news:0d6b01c372cf$4197f3e0$a101280a@.phx.gbl...
> Hi,
> Both as SQL 2k.
> Tks and Rgds,
> Sachi
> >--Original Message--
> >What versions of SQL Server are they ?
> >
> >--
> >
> >--
> >Allan Mitchell (Microsoft SQL Server MVP)
> >MCSE,MCDBA
> >www.SQLDTS.com
> >I support PASS - the definitive, global community
> >for SQL Server professionals - http://www.sqlpass.org
>

Friday, February 17, 2012

ERROR: table don't support this operation

hello all,

this query causes error on some servers (sql2000 sp3). on our development server is this ok. we have restore the database from customer server to the development server, this is ok too. we don't know which configuration on the server can change to solve the problem.
-
select distinct V.Vereinsname as Vereinsname, V.VNr as VerNr, V.PLZ as PLZ, V.Ort as Ort, V.Strasse1 as Stra?e1, V.Strasse2 as Stra?e2, '0' as Sel
, V.Statusfeld01, V.Statusfeld02, V.Statusfeld03, V.Statusfeld04, V.Statusfeld05, V.Statusfeld06, V.Statusfeld07, V.Statusfeld08, V.Statusfeld09
, V.Statusfeld10, V.Statusfeld11, V.Statusfeld12, V.Statusfeld13, V.Statusfeld14, V.Statusfeld15, V.Statusfeld16

from VRMWSTD V
where 0 < V.VKrNr
and V.VKrNr in (1)
order by Vereinsname

-
the message in german is: "Tabelle unterstützt diese Operation nicht."

many thanks in advance

duong

Have you checked the index?|||just a question but why do you do this -
where 0 < V.VKrNr
and V.VKrNr in (1)

and not simply

where V.VKrNr = 1

I don't know. . . sql might optimize it out, but seems like overkill.|||Could you please post a simple repro script? The error message looks like a client library message and not SQL Server. It could be that you are trying to add/update rows in the datatable or recordset for example and it is not supported. This can be due to the nature of the SELECT statement (use of DISTINCT and ORDER BY clauses) which will make the resultset read-only.