problem with ALTER TABLE syntax

I finally found a way to "deploy" my local SqlServerExpress (SSE) database to the remote Sql2K server... In VisualWebDeveloper (VWD) I can create the table definition and then save the creation sql script and use that in SSE Express Manager while connected to my remote DB. I am describing this because I'm so surprised no one has had problems with this as thousands of developers, some very unexperienced (as me maybe!), are trying the same situation now that some are offering 2.0 hosting... Well I thought this was a great idea until the Sql2K server is returning error messages on the script VWD created. So please could you help since I'm not that good at complex sql scripting. It seems the error comes from the ALTER TABLE syntax:
BEGIN TRANSACTION
SET QUOTED_IDENTIFIER ON
SET ARITHABORT ON
SET NUMERIC_ROUNDABORT OFF
SET CONCAT_NULL_YIELDS_NULL ON
SET ANSI_NULLS ON
SET ANSI_PADDING ON
SET ANSI_WARNINGS ON
COMMIT
BEGIN TRANSACTION
CREATE TABLE dbo.Table2
(
prID int NOT NULL IDENTITY (1, 1),
DateInserted datetime NOT NULL,
Title nvarchar(100) NOT NULL,
Description nvarchar(MAX) NULL,
CategoryID smallint NOT NULL,
DateLastUpdated datetime NULL,
Price int NOT NULL,
SpecialPrice int NULL,
ImgSuffix nvarchar(5) NULL,
ImgCustomWidth smallint NULL
) ON [PRIMARY]
TEXTIMAGE_ON [PRIMARY]
GO
ALTER TABLE dbo.Table2 ADD CONSTRAINT
PK_Table2 PRIMARY KEY CLUSTERED
(
prID
) WITH( STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

GO
COMMIT

Exactly what error message are you getting?
Tryst
|||

Msg 170... Incorrect syntax near '('.
I've found out if I remove "WITH( STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON)"
it works...

Problem when trying to deploy a web site built with asp.net 2.0 and using SQL EXPRESS

Hi,

Plz help!

I built a web site using IIS and ASP.NET 2.0.

My web site has a log on screen and I only configured it with one user without any roles. This web site uses the SQL EXPRESS.(I Have 2 databases: 1 for the security required by the application and the other for my application. for the connectionstring I used a windows authentication security with an instance = true.)

Everything went well on my PC.

When I tried to deploy the web site on another PC, there was a big problem.

When I tried to login with the same user I created, then I have a problem.

The password is incorrect(Why? I don't know).

Maybe there is a problem with the IIS or with the SQL SERVER.

pLZ HELP!!

You should take a look at the forum at http://forums.asp.net/54/ShowForum.aspx, which covers Visual Web Designer. They will have a better idea how to address this.

Mike

Problem when deploying a cube with new data in the datasource

Hello,

I've got a cube with a datasource. I deploy my cube a month ago for test.

Since, some data have been added in the datasource, and I want deploy the cube to add this data in my cube and use it in some web pages.

But I can't deploy it, it say me that it can't find the key attributes for a key value that corresponds to a new value in my datasource.

Can someone help me because I must present data to some person but I can't if my cube doesn't process anymore.

Thanks for your help

Run update Process on all the dimensions first and then run a FULL Process in the cube..This is how you will include all the new data into the cube .

Problem Viewing reports in Report Manager

I have successfully installed the sql server reporting services on a windows
2003 server. I have been able to deploy several reports to the report
server. I have even been able to schedule a report to execute and send out
via email every morning of the week.
Here's the problem. When I try to view a report using the report manager I
get a
The page cannot be found
HTTP 404 - File not found
Internet Explorer
error. I just don't get it. I can perform every other function using the
report manager except view the report online. Which of course is a problem
because I want to send my customers to the site to be able to view and run
reports.
Thanks for any help.
--
Jon Clayton
Regions Financial CorporationSounds like a security issue or a malformed URL. It's very difficult (from
here) to determine how you access report manager differently than the online
version, but could you post a URL that worked, and a URL that failed?
Dwayne|||Thanks for your help.
Here is a link that works
http://Servername/Reports/Pages/Folder.aspx
This link of course brings up the default folders page
Click on a folder and go to the following url, which work
http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
Click on a report in that folder to view the report using the following url
fail
http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
The failure only occurs within the frame below. The header frame is still
displayed, therefore I am able to:
Click on the properties tab with the failed page displayed is successful
using the following ur
http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
I have given full access permissions to the ASPNET account on the local
machine to the two RS folders.
I am convinced that it is a permissions issue. As a matter of fact I had an
instance installed in my test invironment which is Windows 2000 which worked
fine. But ever since the latest security updates that machine is having the
same issue.
Thanks again for your help.
--
Jon Clayton
Regions Financial Corporation
"Dwayne J. Baldwin" wrote:
> Sounds like a security issue or a malformed URL. It's very difficult (from
> here) to determine how you access report manager differently than the online
> version, but could you post a URL that worked, and a URL that failed?
> Dwayne
>
>|||"Jon" wrote:
> Thanks for your help.
> Here is a link that works
> http://Servername/Reports/Pages/Folder.aspx
> This link of course brings up the default folders page
> Click on a folder and go to the following url, which works
> http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
> Click on a report in that folder to view the report using the following url
> fails
> http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
> The failure only occurs within the frame below. The header frame is still
> displayed, therefore I am able to:
> Click on the properties tab with the failed page displayed is successful
> using the following url
> http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
> I have given full access permissions to the ASPNET account on the local
> machine to the two RS folders.
> I am convinced that it is a permissions issue. As a matter of fact I had an
> instance installed in my test invironment which is Windows 2000 which worked
> fine. But ever since the latest security updates that machine is having the
> same issue.
> Thanks again for your help.
> --
> Jon Clayton
> Regions Financial Corporation
>
> "Dwayne J. Baldwin" wrote:
> > Sounds like a security issue or a malformed URL. It's very difficult (from
> > here) to determine how you access report manager differently than the online
> > version, but could you post a URL that worked, and a URL that failed?
> >
> > Dwayne
> >
> >
> >
> > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.|||It appears that the entries in the config files are correct. Thanks for the
tip.
--
Jon Clayton
Regions Financial Corporation
"DLM" wrote:
>
> "Jon" wrote:
> > Thanks for your help.
> >
> > Here is a link that works
> > http://Servername/Reports/Pages/Folder.aspx
> > This link of course brings up the default folders page
> >
> > Click on a folder and go to the following url, which works
> > http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
> >
> > Click on a report in that folder to view the report using the following url
> > fails
> > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
> > The failure only occurs within the frame below. The header frame is still
> > displayed, therefore I am able to:
> >
> > Click on the properties tab with the failed page displayed is successful
> > using the following url
> > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
> >
> > I have given full access permissions to the ASPNET account on the local
> > machine to the two RS folders.
> >
> > I am convinced that it is a permissions issue. As a matter of fact I had an
> > instance installed in my test invironment which is Windows 2000 which worked
> > fine. But ever since the latest security updates that machine is having the
> > same issue.
> >
> > Thanks again for your help.
> >
> > --
> > Jon Clayton
> > Regions Financial Corporation
> >
> >
> > "Dwayne J. Baldwin" wrote:
> >
> > > Sounds like a security issue or a malformed URL. It's very difficult (from
> > > here) to determine how you access report manager differently than the online
> > > version, but could you post a URL that worked, and a URL that failed?
> > >
> > > Dwayne
> > >
> > >
> > >
> > > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.|||Hi Jon,
I have exactly the same problem. Please advise what I need to check/do?
Thanks very much
Khat.
"Jon" wrote:
> It appears that the entries in the config files are correct. Thanks for the
> tip.
> --
> Jon Clayton
> Regions Financial Corporation
>
> "DLM" wrote:
> >
> >
> > "Jon" wrote:
> >
> > > Thanks for your help.
> > >
> > > Here is a link that works
> > > http://Servername/Reports/Pages/Folder.aspx
> > > This link of course brings up the default folders page
> > >
> > > Click on a folder and go to the following url, which works
> > > http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
> > >
> > > Click on a report in that folder to view the report using the following url
> > > fails
> > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
> > > The failure only occurs within the frame below. The header frame is still
> > > displayed, therefore I am able to:
> > >
> > > Click on the properties tab with the failed page displayed is successful
> > > using the following url
> > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
> > >
> > > I have given full access permissions to the ASPNET account on the local
> > > machine to the two RS folders.
> > >
> > > I am convinced that it is a permissions issue. As a matter of fact I had an
> > > instance installed in my test invironment which is Windows 2000 which worked
> > > fine. But ever since the latest security updates that machine is having the
> > > same issue.
> > >
> > > Thanks again for your help.
> > >
> > > --
> > > Jon Clayton
> > > Regions Financial Corporation
> > >
> > >
> > > "Dwayne J. Baldwin" wrote:
> > >
> > > > Sounds like a security issue or a malformed URL. It's very difficult (from
> > > > here) to determine how you access report manager differently than the online
> > > > version, but could you post a URL that worked, and a URL that failed?
> > > >
> > > > Dwayne
> > > >
> > > >
> > > >
> > > > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.|||I am also having this same exact problem. I can run everything without issue
on our test server but production server is exhibiting this exact behavior?
I can do everything but view the report. I can even run the report on the
production server through code and through http://server/reportserver.
Navigate to the folder/report and viola. I can enter parameters and run it.
But not in the report manager gui' I get a 404 when I press the view
report button. If I press it a second time I then get an error in the lower
left hand corner of IE. If I open it up it states that on Line 50 permission
denied and url = http://server/reportserver...blah...blah...blah
Kevin
"Khat Liko" wrote:
> Hi Jon,
> I have exactly the same problem. Please advise what I need to check/do?
> Thanks very much
> Khat.
> "Jon" wrote:
> > It appears that the entries in the config files are correct. Thanks for the
> > tip.
> > --
> > Jon Clayton
> > Regions Financial Corporation
> >
> >
> > "DLM" wrote:
> >
> > >
> > >
> > > "Jon" wrote:
> > >
> > > > Thanks for your help.
> > > >
> > > > Here is a link that works
> > > > http://Servername/Reports/Pages/Folder.aspx
> > > > This link of course brings up the default folders page
> > > >
> > > > Click on a folder and go to the following url, which works
> > > > http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
> > > >
> > > > Click on a report in that folder to view the report using the following url
> > > > fails
> > > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
> > > > The failure only occurs within the frame below. The header frame is still
> > > > displayed, therefore I am able to:
> > > >
> > > > Click on the properties tab with the failed page displayed is successful
> > > > using the following url
> > > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
> > > >
> > > > I have given full access permissions to the ASPNET account on the local
> > > > machine to the two RS folders.
> > > >
> > > > I am convinced that it is a permissions issue. As a matter of fact I had an
> > > > instance installed in my test invironment which is Windows 2000 which worked
> > > > fine. But ever since the latest security updates that machine is having the
> > > > same issue.
> > > >
> > > > Thanks again for your help.
> > > >
> > > > --
> > > > Jon Clayton
> > > > Regions Financial Corporation
> > > >
> > > >
> > > > "Dwayne J. Baldwin" wrote:
> > > >
> > > > > Sounds like a security issue or a malformed URL. It's very difficult (from
> > > > > here) to determine how you access report manager differently than the online
> > > > > version, but could you post a URL that worked, and a URL that failed?
> > > > >
> > > > > Dwayne
> > > > >
> > > > >
> > > > >
> > > > > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.