In proiv 5.5 is there a way that you can trap for deadlocks in sql server ?
In theory I suppose you can suppress errors, but would that then give you a bad write logic?
- ProIV Resource Centre
- → Viewing Profile: Topics: Sean Graves
Community Stats
- Group Members
- Active Posts 13
- Profile Views 5,520
- Member Title Member
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Male
-
Location
United Kingdom
Previous Fields
-
First Name
Sean
-
Surname
Graves
-
Year Started ProIV
1995
-
Highest ProIV Version Used
5.5
-
Company Working For
Pro Delta Systems Ltd
0
Neutral
User Tools
Friends
Sean Graves hasn't added any friends yet.
Latest Visitors
Topics I've Started
SQL Server Catch Deadlocks
20 May 2011 - 04:32 PM
Bus & Tasks / Service logon under diffent account
19 September 2006 - 11:02 AM
Hi guys,
I have a Windows 2000 machine where we have had to log the ProIV Service on as a different account due to there being more than one version of Oracle Client installed.
I created an Account called ServiceProIV and made it a member of "administrators".
I set the local policy to state it can logon locally and logon as a service.
This allowed me to set to the local environment for it to use the right Oracle Client.
This all works fine and connects to the environment all succesfully.
I now created a local user account eg BaTClient with a password and made it a member of "Users".
When I try and do a bus and task connection and found that the BaTClient System Username and System Password is being being told it is invalid.
Yet I can log onto the machine succesfully.
If I switch the service account back to use the LocalSystem and try the B&T again it now states it is valid.
So the question is what else is needed to allow the Service to authenticate the userid when the service is logged on as something other than LocalSystem?
Thanks for any help
Sean
I have a Windows 2000 machine where we have had to log the ProIV Service on as a different account due to there being more than one version of Oracle Client installed.
I created an Account called ServiceProIV and made it a member of "administrators".
I set the local policy to state it can logon locally and logon as a service.
This allowed me to set to the local environment for it to use the right Oracle Client.
This all works fine and connects to the environment all succesfully.
I now created a local user account eg BaTClient with a password and made it a member of "Users".
When I try and do a bus and task connection and found that the BaTClient System Username and System Password is being being told it is invalid.
Yet I can log onto the machine succesfully.
If I switch the service account back to use the LocalSystem and try the B&T again it now states it is valid.
So the question is what else is needed to allow the Service to authenticate the userid when the service is logged on as something other than LocalSystem?
Thanks for any help
Sean
ProIV & SQL Server 2005
12 July 2006 - 09:12 AM
Has anybody used SQL Server 2005 with ProIV Version 5.5 on Windows 2003 Server / Windows XP Professional ?
If so have you had any differculties using with ProIV or have you found it worked with no problems ?
If so have you had any differculties using with ProIV or have you found it worked with no problems ?
VIP Bulk Load
15 June 2006 - 04:48 PM
VIP Bulk Load - changes widths of ICONs in @FORMs
ProIV : 5.5r411
Mfc : 5.6.5.0
Vip : 5.5922 (005)
Platform: Windows NT Server
We have a function with a format that has an Icon defined with a WIDTH 42.
**** Extract from @DOCFN *****
03 6 : 3
TAG: WEB2
DISP: ALIGN: C TYPE: ICON SUPP.LAB: REP STR: VISITWEB FKEY:
HEIGHT: 1 WIDTH: 42 ICON NAME: PDSCLEAR.GIF VAR: Y
ICON LABEL:$$WEB1 VAR:
TOOL TIP: Some text here to act as the mouse tool tip help line
**** End of Extract *****
**** Logic In used to set the $$WEB1 **********
098 001 * Logic In
002 *
003 $$WEB1 = 'http://www.bbc.co.uk/news/'
004 WEB2.BACKCOLOR = 'WHITE'
005 WEB2.FORECOLOR = 'BLUE'
006 WEB2.FONTNAME = 'TAHOMA'
007 WEB2.UNDERLINE = 1
008 WEB2.ALIGNMENT = 'MID_CENTER'
009 WEB2.SCALE = 1
**** End of Logic *******
When you load this into VIP via the "Bulk Load" - VIP/Admin/Tools/Bulk Load
The code has now been changed and the new width of the Icon is 1.
Function in VIP (Statics) the $$WEB1 now has a width of 1.
Build it in VIP
Using the native @FORM look at what VIP has transferred back and you will see the width of 1.
This is a major bug as it will change the majority of our Application.
ProIV : 5.5r411
Mfc : 5.6.5.0
Vip : 5.5922 (005)
Platform: Windows NT Server
We have a function with a format that has an Icon defined with a WIDTH 42.
**** Extract from @DOCFN *****
03 6 : 3
TAG: WEB2
DISP: ALIGN: C TYPE: ICON SUPP.LAB: REP STR: VISITWEB FKEY:
HEIGHT: 1 WIDTH: 42 ICON NAME: PDSCLEAR.GIF VAR: Y
ICON LABEL:$$WEB1 VAR:
TOOL TIP: Some text here to act as the mouse tool tip help line
**** End of Extract *****
**** Logic In used to set the $$WEB1 **********
098 001 * Logic In
002 *
003 $$WEB1 = 'http://www.bbc.co.uk/news/'
004 WEB2.BACKCOLOR = 'WHITE'
005 WEB2.FORECOLOR = 'BLUE'
006 WEB2.FONTNAME = 'TAHOMA'
007 WEB2.UNDERLINE = 1
008 WEB2.ALIGNMENT = 'MID_CENTER'
009 WEB2.SCALE = 1
**** End of Logic *******
When you load this into VIP via the "Bulk Load" - VIP/Admin/Tools/Bulk Load
The code has now been changed and the new width of the Icon is 1.
Function in VIP (Statics) the $$WEB1 now has a width of 1.
Build it in VIP
Using the native @FORM look at what VIP has transferred back and you will see the width of 1.
This is a major bug as it will change the majority of our Application.
SYSTEM verb displays console box on Standalone
11 August 2005 - 08:27 AM
Platform: Windows XP
Mfc : 524
We have one set of BOOTS that runs on many different platforms, Windows NT,
Unix, Windows XP.
Part of our code requires us to run an application on the server where the
kernel lives. The application runs and after it has completed proiv then
reads a file that the application created.
We have used the SYSTEM verb and this works fine on Windows NT or UNIX
platforms.
However when you are a Standalone version using the pro32.exe eg Windows XP
then the system verb displays a console window ( DOS Black Box running CMD
shell ), then execute the application and finally disappears.
We are executing the following line:
"\myapp.exe parameter1 parameter2 parameter3"
I have also tried it with the word "WINDOWS " inserted at the front of the
above example :
"WINDOWS\myapp.exe parameter1 parameter2 parameter3"
Is there a way to execute the SYSTEM verb with out the console window
appearing ?
Otherwise is there a way of detecting when you are standalone ?
Any help will be appreciated.
Mfc : 524
We have one set of BOOTS that runs on many different platforms, Windows NT,
Unix, Windows XP.
Part of our code requires us to run an application on the server where the
kernel lives. The application runs and after it has completed proiv then
reads a file that the application created.
We have used the SYSTEM verb and this works fine on Windows NT or UNIX
platforms.
However when you are a Standalone version using the pro32.exe eg Windows XP
then the system verb displays a console window ( DOS Black Box running CMD
shell ), then execute the application and finally disappears.
We are executing the following line:
"
I have also tried it with the word "WINDOWS " inserted at the front of the
above example :
"WINDOWS
Is there a way to execute the SYSTEM verb with out the console window
appearing ?
Otherwise is there a way of detecting when you are standalone ?
Any help will be appreciated.
- ProIV Resource Centre
- → Viewing Profile: Topics: Sean Graves
- Privacy Policy