Report Builder hangs

N

nevilleNeale

New Member
When connecting to Report Builder from a client (XP) PC, we getthe first screen and the a blank screen and the reportbulider task is flagged as 'not responding' however if we then remove 1 or 2 parameters in either the .pf file or the command line and try again it works. Add the parameters back and it hangs again. Are we missing some .ini setting or something?
 
What are the parameters you are saying you remove? What other parameters do you have in the pf file?
 
The .pf file is as follows

This is the working .pf file - between the -'s and the *'s.
------------------------------------------------------------------
-db CORE -N tcp -S 31010 -H node250 -trig trig
-db OPENREV -N tcp -S 31020 -H node250 -trig trig
-db OS -N tcp -S 31030 -H node250
-db SUNDEBT -N tcp -S 31040 -H node250 -trig trig
-db OPENWEB -N tcp -S 31050 -H node250
-db IH -N tcp -S 31060 -H node250 -trig trig
#-db oc -N tcp -S 31070 -H node250 -trig trig
#-db MIS -N tcp -S 31070 -H node250 -trig trig
-h 8
-Mm 4096 # network packet size
-T c:\temp # progress working temp dir
-q # quickstart
-D 200 # directory size
-TB 31 # speed sort parameter
-TM 32 # speed sort parameter
-Bt 20 # number of temp table buffers
-s 80

*******************************************************

If we remove the # sign on any of the -db lines above then report builder hangs.
 
Looks like you are using the same socket number for two different DBs.
-db oc -N tcp -S 31070 -H node250 -trig trig
-db MIS -N tcp -S 31070 -H node250 -trig trig
Click to expand...
One of the sockets used is bound to be wrong. So, check what sockets are used when starting the database servers for databases "oc" and "MIS" on server "node250" and put the correct sockets in your pf file with the correct database. That might solve your problem...
 
Thank's BUT...

The 2 DB's with the same socket numbers are a red herring as they are both commented out. However the MIS DB is correct and the OC db is currently being changed. The problem occurs when we 'uncomment' ,for example the MIS line, and does not occur with the .pf file as it is. Also we have 3 other identical 'test' environments (but without the MIS DB at all) in which the OC BD is currently being used but Report Builder hangs unless we comment out any of the DB lines in the relevant .pf file.
 
You must log in or register to reply here.
Back
Top