Developer forum

Forum » Development » Error setting up DW on sql server 2008R2 and win7

Error setting up DW on sql server 2008R2 and win7

E-mail notifications
Finn Christensen
Reply
Posted on 24/06/2011 14:38:27
Hey All,

I have a problem setting up DW on win7 and sqlserver 2008R2.

I get yellow screen (see attachment) when I use sqlserver, it looks like it's an write-access problem to a log. I have set permissions on the folders (application/database/files) to network service, but not to machine\aspnet and machine\iusr_machine as network service covers these on IIS7.

But I cannot decifre the errormessage closer...

Any help is appriciated, thanks in advance.

Regards Finn.
Capture.PNG

Replies

 
Yury Zhukovskiy
Posted on 26/06/2011 23:48:29
Reply

Hi,

I’ve found two possible solutions, check them please.

 

Variant 1.

Add identify row to the web.config.

<identity impersonate="true" userName="userName" password="password"/>

Link to post:http://www.velocityreviews.com/forums/t94689-aspnet-cant-write-in-event-log-on-win-xp.html

 

Variant2

Change registry keys.

http://forums.asp.net/t/1131903.aspx

 

Kind Regards

Zhukovskiy Yury

 
Nicolai Høeg Pedersen
Posted on 27/06/2011 09:38:22
Reply
It is because Dynamicweb cannot access your database.

Check your database settings in /Files/Globalsettings.aspx in the database section.

 
Finn Christensen
Posted on 29/06/2011 11:11:27
Reply

Yes, of course. Thanks Nicolai!

Just using Integratedsecurity=false

I get an error though when logging in, System.IndexOutOfRangeException: AccessUserExternalID.

See attachment!
Capture2.PNG
 
Nicolai Høeg Pedersen
Posted on 29/06/2011 11:14:57
Reply
Go to files/update.xml and set it to 350, save, IISRESET, access the website and your are up and running.
 
Finn Christensen
Posted on 29/06/2011 12:53:06
Reply

Nope,

I'm sorry to say, but I get exactly the same error. And the system keeps changing the value back to 416!
 
Nicolai Høeg Pedersen
Posted on 29/06/2011 14:40:13
Reply
What does your /Files/updatelog.html say? My guess is that your DB user lacks the DDL permissions.
 
Finn Christensen
Posted on 29/06/2011 16:36:12
Reply

I think you are right!

It seems like no package sql succeeds, it gives error: 91 - Object reference not set to an instance of an object
which in turn comes from sqlserver error 229, which is an execute permission denial!

Though, I have never seen this kind of error before.
 
Pavel Volgarev
Posted on 29/06/2011 16:41:56
Reply
Hi Finn,

What version are you using? I think we fixed this issue in one of the recent releases...

Anyway, I guess switching from Integrated pipeline to Classic pipeline (app. pool settings in IIS) would eliminate the problem.

-- Pavel
 
Finn Christensen
Posted on 29/06/2011 17:06:48
Reply

Hi Pavel,

Thanks for your idea, but it doesn't work.

I'm a bit confused here. I have used the installation guide, part D upsizing access databases and completed the step "How to set up the sql server database" as the only step and modified the Globalsettings.aspx to use ms_sqlserver! Do I have to do the "how to upsize the access databases" as well, I didn't do that because I wanted a clean database to run on!

I just thought you could use a clean mssql database (doing the dedfaultemptydatasql)!

/Finn

Btw. I'm using the 19.2.2.3 version.
 
Nicolai Høeg Pedersen
Posted on 29/06/2011 17:27:34
Reply
You can use the defaultemptydatasql.

The problem is missing DDL permissions on the user you connect to the database with. Please check permissions.

The error is there because DW tries to create new fields in the database, and therefore the user needs the DDL permissions. This is also in the installation guide.

 

You must be logged in to post in the forum