View Complete Post
Hi friend,
I have a project develop with Visual Studio 2003, when i convert the project to Visual Studio 2005 is work well. But when i convert to Visual Studio 2008, the crystal report when have pass parameter will prompt the parameter field to re-type then show the report.
But in this converted project i create a new report and pass the parameter is ok. That means i wan re-do all report @.@??
Does someone can help me solve this problem??
Thank you
Hi!
I'm having problems converting a VS 2003 project to VS 2008 (tried 2005 as well, same problem). There are several problems;a) I don't have VS 2003 installed.b) The project is a web service, however I'm not sure what type of VS project it was created as.c) The general knowledge about the project setup is..slim.
I get a error message using the conversion wizard, however, I'm not familiar with the tool and I cannot quite find any good information on Google for it, so I am left with a error message I do not understand.
Conversion Issues - myProject.csproj:Unable to open the Web site 'C:\local\path\to\project\myProject.csproj'. The Web site 'C:\local\path\to\project\myProject.csproj' does not exist.
The web service is not intended to run on the dev machine, it is copied to a test or a prod server. However, I do not know how this was done previously. I'm thinking that in order to convert, it has to access the server on which it should run (which is set somehow in a config maybe). But that doesn't actually make any sence..
If anyone could shed light on this, I would really appreciate it.
Thank you.
I did an inplace upgrade of SSRS 2005 to 2008 and now the reports are throwing the following error. The reports were all working fine and there is a datasource with the name 'Data Source Name' without the '_'. Please help.
I hope someone may shed some light on a serious obstacle encountered on a client site:
We have implemented a SharePoint integrated report services solution for the client on a single server
Server = Windows 2003
SQL = 2008
MOSS 2007
Web application = servername:8888 (default) - windows auth
Web application extension 1 servername:8889 (extranet) forms auth
Web application extension 2 servername:8887 (intranet) forms auth
Reports are visible and can be run (renders) on internal sites
However, there is an external site which allows users to access the reports - the issue is, the reports then dont run and I get this:
"An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode."
Though I have not actually seen the firewall config of the AAM, the client assures me it has been setup properly.
If the AAM is setup correctly, what could be the problem? The server is clearly available and confgured in SharePoint integrated mode.
has anyone experienced the scenario where clients want to publish their reports on an external site? What can one do to see any errors other than the one line message (tried enabling custom errors, but no good)
SQLServer 2008 R2
Excel 2010 x64
Hi All,
I have a fairly complex Excel report where a raw data sheet is updated from 10 or so PivotTables pulling from an Analysis Services Cube, (2008 R2), with a VBA script that refreshes all pivottables, and then does some post-processing, formatting etc.
This was originally developed in Excel 2003, and the updating of all the pivot tables ran in under 10 seconds
I've now recreated in Excel 2010 and *each table* is taking up to a minute to refresh!
I've also observed that I can get the refresh time of a single table back down to 1sec, if I delete all other pivottables from the worksheet/book.
Its deeply frustrating, as I'm touting 2010 as being the way for our business to go...it won't help the cause if I deliver something with a x60 increase in runtime!
I've run traces of both the 2003 and 2010 versions executing against the SQL Server, the only thing I can see is that the 2003 version passes 1 single MDX query, whilst the 2010 version appears to be firing it in sections.
I've posted this in the Excel forum too.
Please can anyone help?
Many thanks,
Nikki
I'm trying to install SQL Server 2008 for Small Business, on a Windows Server 2003 SBS, which is a Domain Controller on a less than 50 users ' domain. I'm logged in with the Administrator account, wich belongs to the 'Doman admins' group also. Setup failed with this error:
Microsoft.SqlServer.Configuration.SetupExtension.EditionRequirementCheck 2010-09-25 11:55:34 Slp: EditionRequirementCheck Rule Check : The edition is not allowed on this OS. 2010-09-25 11:55:34 Slp: Evaluating rule : EditionRequirementCheck 2010-09-25 11:55:34 Slp: Rule running on machine: DELL1 2010-09-25 11:55:34 Slp: Rule evaluation done : Failed 2010-09-25 11:55:34 Slp: Rule evaluation message: This SQL Server edition is not supported on this operating system. See SQL Server Books Online for information about supported operating systems for SQL Small Business Server edition.
According to this link, this version is supported on Windows Server 2003 SBS: http://msdn.microsoft.com/en-us/library/ms143506%28SQL.100%29.aspx#SE32
I've tried to diagnose the error, after reading this link: http://blogs.technet.com/b/sbs/archive/2010/07/21/how-to-diagnose-quot-operating-system-supported-for-edition-quot-pre-requisite-errors-while-installing-sql-2008-standard-edition-for-small-business.aspx
After a new
Is there a way to take a SQL2008 database to SQL2003? I'm only interested in the basic schema of the database that is supported in SQL2003. I'm not interested in the data. I want a blank database at the end.
I tried the generate scripts but the resulting script has a plethoria of errors when I parsed it on SQL2003. I'm just looking for the basic database structure only. Tables, Views, basic interdependenices.
I am planning to move SharePoint 2007 from a Windows 2003 32-bit system to a new Windows 2008 R2 64-bit server tomorrow afternoon. I have done much research and found only one article that gives me enough information to go on for the migration. Others in technet have cited this article; so, I expect it is the one go use. However, before I begin, I wanted to see if anyone has anything else to add.
Here's the article I'm planning to use:
http://www.combined-knowledge.com/Downloads/2007/How%20to%20move%20MOSS2007%20from%20W2003_32bit%20to%20W2008_64bit.pdf
Our current environment consist of one front end server (Windows 2003 32-bit running MOSS 2007) and one SQL server (Windows 2008 Standard 64-bit with SQL 2008 640bit). So, we don't need to move the SQL databases - just the SharePoint front end. We are moving to Windows 2008 R2 with MOSS 2007 (same SP and patch levels are planned).
Our final goal is to move to SharePoint 2010 in the next week or two, but this seems to be the required first step.
Most of what I've read online contradicts other things. I've found no consistency between articles.
Thank you in advance for your assistance.
Hi, I have a weird problem.
I can start sql server just fine with services.
But i cannot start sql server with cluster admin utility, nor can i start sql server using command line.
ANd there is no errorlog produced when i tried.
What could be the problem? below is the cut from the cluster.log file
===========
I cannot get the SQL Server Agent to start. All the literature and blogs I have found to correct this, have led me to the following quick fix:
sp_configure 'show advanced options', 1; RECONFIGURE; GO sp_configure 'affinity mask', 32; RECONFIGURE; GO
However, when I try this, I get the following erros:
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install. Msg 5833, Level 16, State 1, Line 2 The affinity mask specified is greater than the number of CPUs supported or licensed on this edition of SQL Server. Msg 15123, Level 16, State 1, Procedure sp_configure, Line 51 The configuration option 'affinity mask' does not exist, or it may be an advanced option. Msg 5833, Level 16, State 1, Line 2 The affinity mask specified is greater than the number of CPUs supported or licensed on this edition of SQL Server.
Can anyone help?
Thanks.
Hall of Fame Twitter Terms of Service Privacy Policy Contact Us Archives Tell A Friend